Why design and development need the same conversation
Bring designers and developers into the decisions that shape the project, from the first brief to the last interaction.
Maya Ellis · Co-founder & Design Director
· 4 min read

The gaps between a design and its implementation often begin long before handover. A team can agree on a screen while holding different assumptions about the content, interaction, or data behind it.
Discuss those assumptions while choices are still easy to change. A short working session early in the project can prevent a week of revisions later.
Use real constraints to guide the design.
Share the shape of the data, the systems involved, and any accessibility requirements early. These details can help the team choose a stronger direction.
If a constraint is uncertain, build a small experiment. The result gives the team something concrete to discuss before the layout is locked.
Work through what happens between screens.
Review loading, empty, error, and success states alongside the main view. Identify what a visitor can do when something takes longer or fails.
Document keyboard behavior and focus changes while the interaction is fresh. Test those decisions against a working prototype.
Use a browser to settle the details.
Build a representative section with real content and review it on a few screen sizes. Look at wrapping, reading order, and the way interactions feel.
Keep the review focused on the intent of the design. When the browser reveals a better solution, capture the change in both the design and the code.

Leave enough context for the next person.
Record why a component behaves a certain way or why a feature was deferred. A few sentences next to the relevant design or pull request are often enough.
When a decision changes, update the place the team actually reads. That makes the new direction easy to find during implementation.
Check the experience as a team.
Walk through the key tasks together before launch. Verify that the copy, layout, and behavior support the same goal.
Leave the next team a short guide to the decisions that are likely to come up again, along with examples they can build on.
Questions for the next project review
- Do we agree on the outcome?
- What assumptions need testing?
- Have we reviewed the less common states?
- What changed in the browser?
- Where did we record the decisions?
Start with one shared review early in the project and keep the conversation going as the work moves into the browser.


