Draw the important boundaries
Map the components and the data that passes between them. Name external dependencies and ownership boundaries.
Work through the architecture together.
Map components, boundaries and trade-offs on a shared canvas. Make room for the questions that need answering before implementation.
Hosts sign up. Guests join with a name.
Expose the assumptions before the build.
Add the uncomfortable questions
Note failure cases, access assumptions and operational constraints beside the affected parts of the design.
Record the trade-off
Compare the options in the same board and write down why the team chose one. Keep unresolved questions explicit.
An example session
Review an import workflow
Trace a file from upload through validation, processing and the result shown to the user. Add branches for partial failure and a repeated submission. Invite engineering and operations to challenge the recovery path.
Take a clearer set of design decisions and open questions into implementation.
Technical designExample board ClientCollect the user’s request
ApplicationCheck access and apply rules
Data serviceRead the required records
ResponseReturn a useful result
Does Boards validate the architecture?
No. The board helps the team model and review a design. Technical correctness, performance and security still need appropriate engineering validation.
Can an assistant edit a technical diagram?
Compatible assistants can work with real board objects through MCP. Review their changes as you would any other contribution to the design.
Bring the next conversation
onto a board.
Start with 3 free live boards. Invite your participants through a link.
Start free