What to Put on the Wall During a Design Sprint

Key Takeaways

• Four zones: the question, the constraints, today's work, decisions made. Anything else goes to archive.
• The sprint question stays visible for all five days. It is the thing that drifts fastest and costs the most when it does.
• Decisions get written when made, in a permanent zone. Otherwise Thursday reopens Tuesday.
• Archive rather than delete. Yesterday's divergence is context, and it should not be in the working field of view.
• Constraints belong on the wall from Monday. A sprint that discovers a constraint on Thursday has wasted two days.
• One person owns the wall. Shared editing with nobody responsible produces a wall nobody trusts.

Why Walls Fail by Wednesday

A design sprint generates a large amount of material fast, and a wall is the only artifact everyone shares. The default behaviour is additive: everything produced gets put up and nothing comes down.

By Wednesday the wall holds Monday's map, Monday's expert notes, Tuesday's lightning demos, Tuesday's sketches, Wednesday's storyboard in progress, and a scattering of parked ideas. It is a complete record and a useless working surface.

What breaks first is the question. It went up on Monday, at the top, and by Wednesday it is buried under three days of output or scrolled off screen. The team is now solving whatever the current activity is about, which correlates only loosely with what the week was for.

What breaks second is decisions. A sprint makes dozens of small decisions, and unless they are written somewhere permanent they exist only in the memory of whoever was in the room at the time. Thursday's prototyping then reopens a Tuesday decision, not out of stubbornness but because nobody can point to it.

What breaks third is attention. A wall with two hundred elements gets skimmed rather than read. The team defaults to looking only at whatever was made in the last hour, which is exactly the material that needs the least reference.

A useful diagnostic: on Wednesday afternoon, ask someone to point at the sprint question without scrolling. If they cannot, the wall has stopped working.

The Four Zones

Zone 1: The question

One sentence. Top of the wall. It does not move for five days.

A good sprint question is specific enough to be answerable in a week and big enough to matter. "How might we make onboarding better" fails both tests. "Can a new user get to their first published page without talking to us?" passes.

Next to it, the success criterion: what Friday's test would have to show for the answer to be yes. Written Monday, before anyone has an opinion about the solution.

This zone is roughly two elements and it earns more wall space per element than anything else on the board.

Zone 2: The constraints

Three to six lines, also permanent, also from Monday.

What cannot change: the platforms you must support, the brand rules, the technical realities, the launch date, the thing legal has already said no to.

Constraints on the wall from day one prevent the most demoralising sprint failure, which is a team spending Tuesday and Wednesday on a direction that Thursday reveals to be impossible. Someone in the room usually knew on Monday and did not think to say, because nobody asked.

Add to this zone during the week when a new constraint surfaces, and mark it with the day, so it is obvious that work before that point did not know about it.

Zone 3: Today's work

The largest zone and the only one that changes shape daily.

Monday it holds the map and the expert notes. Tuesday the demos and sketches. Wednesday the storyboard. Thursday the prototype plan. Friday the test observations.

At the end of each day this zone is cleared into archive, except for anything that feeds directly into tomorrow. That clearing is the discipline that keeps the wall usable, and it takes about five minutes.

Zone 4: Decisions made

A running list, permanent, added to as decisions happen.

Each entry is one line: what was decided, and what it rules out. "We are testing the no-account flow. This rules out the social-login variant and the email-first variant."

Write it in the moment. A decision recorded at the end of the day is recorded from memory and loses the ruling-out clause, which is the half that stops it being reopened.

This zone is what makes the sprint's output survive the week. Everything else on the wall is working material; this is the record.

Keeping four zones stable while one of them churns daily is where the tool matters. On a Storyflow canvas the permanent zones stay pinned in their region while the working zone fills and empties, and because its AI reads the whole board you can ask it at the end of a day what decisions were made that are not yet in zone four, which reliably catches two or three.

FigJam and Miro both run sprints well and are the conventional choice; the discipline described here works on either, it just has to be maintained by hand.

Day by Day

Monday. Question and success criterion go up first, before the map. Constraints next, gathered by asking every person in the room what they know that would make a direction impossible. Then the map and expert interviews in zone three.

Monday's specific risk is that the map expands to fill the wall. It is a means, not an output. Clear it into archive on Monday evening and keep only the target area chosen at the end of the day.

Tuesday. Lightning demos and sketching. High volume, and almost all of it is intermediate. Keep the sketches, archive the demos.

Wednesday. Decisions day, and the day zone four earns its existence. Every choice that narrows the prototype goes in as it happens. By Wednesday evening the storyboard is the only thing in zone three.

Thursday. Prototype build. The wall gets quiet because people are working in other tools. What belongs on it is the build plan and the list of what is being faked, since the test on Friday will produce confusing results if nobody remembers which parts were not real.

Friday. Test observations in zone three, grouped by participant. Patterns pulled out into zone four as findings.

Friday evening. The wall is converted: question, constraints, decisions and findings become the record. Zone three archives entirely. This takes half an hour and it is the difference between a sprint that produced a decision and a sprint that produced a nice week.

Remote Walls

Remote sprints make the accumulation problem worse, because infinite canvas removes the natural limit a physical wall imposes. A physical wall runs out of space and forces a decision about what stays; a digital one never does.

The compensation is to define the zones spatially and hold them. Draw the regions on Monday, label them, and do not let zone three spill into the others. It sounds pedantic and it is what keeps a remote wall readable on Thursday.

Name one wall owner. On a physical wall, whoever is standing at it does the tidying and everyone sees it happen. Remotely, nobody owns it and it degrades invisibly. One person clears zone three each evening and keeps zone four current.

Zoom level is a real constraint. If the team has to zoom out past readability to see the whole wall, it is too big, regardless of how well organised it is. That is the signal to archive.

What Goes Wrong

The question scrolls out of view. The single most common failure. Pin it and check on Wednesday that someone can find it in two seconds.

Nothing is ever archived. By Thursday the wall is a museum. Clear zone three nightly.

Decisions are not written down. Thursday reopens Tuesday, and the team loses half a day relitigating something it already settled.

Constraints arrive on Thursday. Somebody knew on Monday. Ask explicitly on Monday and keep asking.

The wall has no owner. It degrades and nobody notices because degradation is gradual.

Everything is kept for the record. Confuses the working surface with the archive. Both are needed and they are not the same surface.

The Bottom Line

Four zones: the question, the constraints, today's work, and the decisions made. Everything else archives.

Pin the question for five days, put the constraints up on Monday by asking the room directly, clear the working zone every evening, and write each decision with what it rules out at the moment it is made. Give one person the job of maintaining it. That is what separates a wall the team uses on Thursday from a wall they stopped reading on Tuesday.