Design thinking that survives the board pack

Design thinking for enterprises is a decision system. Sticky-note tourism is a party. I can tell which one you bought by what is still on the wall in week three. If it is a mural, you bought the party. If it is a one-page problem frame with an owner, you bought the system.

Enterprise design thinking has to survive risk, procurement and a board pack. That is not a betrayal of the method. That is the habitat. Pretending you are in a Stanford d.school studio is how you get a great workshop and a dead idea.

I have run enough of these rooms to be blunt. The five stages are not the product. The prototype and the kill test are the product. If your training never leaves a prototype, you taught vocabulary.

Training that leaves residue

Design thinking training is worth it when the team brings a live problem. Empathise, define, ideate, prototype, test: fine. Now do it on the thing that is actually stuck. Glen Eira, legal practices, agencies: the sessions that worked used a real constraint. The sessions that failed were icebreakers with post-its.

Public-sector tenders still ask for this on purpose. Agencies need a way to frame messy problems without waiting for a three-year programme. When a UK agency tenders for design thinking, that is an opportunity. We wrote it that way. Public sector design thinking without the theatre is the longer argument: permission, a metric, a 90-day window. Not a lab.

CX sits next door. Design thinking decides what to change. Customer experience is the seam the customer feels. One without the other is either a mural or a complaint log. AI design sprints are the same method with a model in the room. Faster options. Same kill.

The board pack test

If you cannot explain the problem, the test and the decision in a pack a director will read, you are not ready to spend. That is the enterprise version. It is not anti-creative. It is anti-waste.

I would rather see a ugly prototype and a clear no than a beautiful journey map and an open question. The map feels like progress. The no is progress.

Collective Campus still trains design thinking for teams who have to take it back to a building with security guards and a steering committee. One link. Steal the method from the pieces below. Buy the room if you need a facilitator who will not let you hide in the stages.

Geos stay named. AU, NZ, HK, SG, the UK, the US and Canada. A tender in the UK is not "government innovation is hard." A council in Victoria is not a Silicon Valley case study. Write the brief you actually have.

What we publish here

Design thinking that survives the board pack. The UK tender piece. The public-sector essay. The design thinking field guide for enterprise teams. Inkeros as a two-day sprint.

If your last workshop did not produce a prototype, do not book another one until you have a problem owner in the invite.

A note on facilitators. The best ones are rude about the stages. They will not let you spend 90 minutes on icebreakers. They will not let "ideation" become a pile of ideas with no test. They will force a prototype out of cheap materials or a clickable fake before lunch on day two. If your facilitator is protecting the vibe, fire the vibe. Keep the prototype.

Procurement will ask for learning outcomes. Give them: a framed problem, a tested prototype, a decision log. If the RFT only asks for "an overview of the five stages," rewrite the RFT or you will get a lecture. The UK tender we wrote about is interesting because it asked for thinking that survives a board. That is the brief you want, even if you are not in government.