teams without shared understanding

what happened

having people on the team that don't know what's going on isn't a good feeling. don't trust each other, create issues, need to redo things. one person builds feature A while another person is also building feature A differently. nobody knows the plan because there was no plan.

why it's a gotcha

you assume everyone's on the same page because you had a 5-minute conversation at the start. they're not. different mental models of the project lead to incompatible code, duplicated work, and arguments at 3am when you realize nothing fits together.

the fix

before anyone writes a line of code, spend 15-30 minutes aligning on: what are we building, what's the MVP, who owns what, what's the tech stack. write it down — even a shared note works. revisit it when things change. role clarity is the most concrete part of shared understanding, and alignment starts before the team forms — figure out what you want first. when misalignment is bad enough, solo is better. and shared understanding breaks down even harder across handoffs, which is why the relay-build-fallacy fails so spectacularly.