Interactive Whiteboarding: How SEs Co-Design Solutions With Buyers

A slide shows the prospect what you think. A whiteboard shows them what you both think. Interactive whiteboarding, whether on a physical board or a shared digital canvas, turns a solution presentation into a joint design session in which the customer draws their own current state and helps sketch the future one. Ideas the customer helped build are ideas they defend later, often in meetings you will never attend.

Why whiteboarding works

• It surfaces reality. When the customer draws their environment, details appear that never come up in a questionnaire: the manual workaround between two systems, the integration nobody owns, the database everyone is afraid to touch.
• It creates shared ownership. The future-state diagram becomes “our design”, not “the vendor’s proposal”.
• It demonstrates expertise without a pitch. Drawing a clear architecture under live questioning builds more credibility than a polished slide.
• It slows the conversation down in a good way. People think more carefully when they are drawing than when they are watching.

Preparation: what to bring into the room

Good whiteboarding looks spontaneous but is rarely improvised. Before the session:

• Sketch your own hypothesis of the current state from discovery notes, so you know which questions to ask while the customer draws.
• Prepare two or three reusable building blocks you are comfortable drawing quickly: users, core systems, integration layer, data stores, security boundary.
• Agree the goal of the session with your champion: understand the current state, agree a target design, or test a specific integration approach.
• For virtual sessions, test the digital canvas beforehand and share edit access so the customer can draw too.

A five-step whiteboarding flow

1. Frame the outcome

Start by writing the business goal at the top of the board in the customer’s words. Every box drawn afterwards should connect back to it.

2. Hand over the pen for the current state

Ask the customer to draw how things work today. Your job is to ask questions: “Where does this data come from?” “What happens when this step fails?” “Who maintains this connection?” Mark pain points directly on the diagram as they are mentioned.

3. Confirm the pain picture

Summarise what is on the board: “So the main friction sits here, here and here. Did I miss anything?” This is the moment to validate your discovery findings in front of everyone.

4. Co-design the future state

Now take the pen, but keep asking. Draw the target architecture beside the current one, and invite the customer to adjust it: “Would your team be comfortable owning this component?” “Is this where security would want the boundary?” Resist drawing your entire product. Draw only what solves the pains on the board.

5. Capture and confirm next steps

Photograph or export the board, send it with a short written summary, and list the open questions with owners. The diagram becomes a shared artefact for the rest of the evaluation.

Techniques that keep the room engaged

• Use two colours. One for today, one for the future. The contrast makes the transformation visible.
• Number the flows. Numbered arrows make it easy for people to reference a step: “Can we go back to step four?”
• Leave white space. A crowded board shuts down contributions. Space invites people to add to it.
• Talk to the room, not the board. Turn around after each element and check understanding.

Common mistakes

• Drawing a product diagram. If every box carries your product name, it is a slide drawn by hand.
• Owning the pen all session. The customer’s hand on the board is the point of the exercise.
• Going too deep too early. Start at the level of systems and flows; zoom in only where the customer wants detail.
• Losing the board. An undocumented whiteboard session is a memory, not an asset.

How to practise

Ask a colleague to describe a system they know well while you draw it in a fixed time, then swap roles. Next, practise drawing your standard reference architecture from memory in a few minutes, talking as you draw. Fluency with the pen frees your attention for the customer.

Interactive whiteboarding belongs to the solution architecture and collaborative design skills in the SE Ignite curriculum: a tech-agnostic way to secure conceptual buy-in, whatever platform you sell. The curriculum is free for any SE who wants to build these skills.