Market Space in Design Thinking: Beyond Build

Most design thinking diagrams end when the solution ships. The team celebrates release. Leadership moves on. Three months later, adoption is flat, support tickets spike, and someone asks whether you built the right thing after all.

That question belongs in Market space - not as a post-mortem, but as a designed phase of work.

In the Growth Diamond Model™, PSM maps three spaces: Problem (Empathize, Define), Solution (Ideate, Develop), and Market (Implement). Market space is where you validate that the solution actually lands with users, stakeholders, and the business - and where you learn what to improve next.

Build is not market validation

Teams often confuse these milestones:

Milestone	What it proves	What it does not prove
Prototype tested	Usability in a lab or pilot	Sustained behavior change at scale
Feature released	Engineering delivery	Adoption, retention, or ROI
Positive feedback from early users	Affinity with a segment	Mainstream readiness
Sales deck approved	Internal alignment	Customer willingness to change workflow

Test in the Stanford model and Deliver in Double Diamond are valuable - but they sit at the boundary of Solution space, not Market space. Market space asks: Now that it exists, does it win?

If your roadmap treats launch as the finish line, you are optimizing for output, not outcome. Read Why 80-95% of Products Fail for how that shows up upstream and downstream.

What Market space includes

In the Growth Diamond Model, Implement is the EDIDI phase for Market space. It is not "hand off to marketing." It includes:

• Prepare to launch - readiness, rollout sequencing, support model, risk plan
• Influencing the decision - executive and buyer alignment so the solution survives internal politics
• Crossing the chasm - moving from early adopters to the pragmatic majority
• Solution enhancement - structured feedback and iteration after go-live

Each activity stays user-centered. The user in Market space may be the same frontline worker from Empathize - or the budget holder who must approve rollout. Both matter.

For a focused take on why teams skip this work, see The Implement Phase Most Teams Skip.

Market validation vs product validation

Product validation asks: Does the solution work? Does it meet acceptance criteria? Can we ship it?

Market validation asks: Will the intended users adopt it? Will the organization sustain it? Does it create measurable value in the real environment?

Examples of market validation signals:

• Adoption rate in the first 90 days vs target segment
• Workflow completion without workarounds or manual overrides
• Support ticket themes - are users struggling with the same friction Empathize surfaced?
• Churn or reversion - do users go back to the old process?
• Stakeholder renewal - does the sponsor fund phase two?

None of these are vanity metrics. Pick the ones tied to the problem statement you wrote in Define.

Three Market space mistakes

1. Launch without a first segment

"Everyone" is not a go-to-market strategy. Crossing the chasm requires a beachhead: one user group, one use case, one success story you can repeat.

2. Confusing communication with adoption

Announcements, training slides, and email blasts are not Implement by themselves. Adoption needs incentives, support, and workflow fit - especially in operations environments. See Design Thinking for Operational Excellence.

3. Treating feedback as a backlog dump

Post-launch enhancement without synthesis sends you back to random feature requests. Structure feedback against the original problem statement and success criteria. If pain shifted, loop to Empathize or Define - that is the iterative power of PSM.

How Market space loops back

Market space is not a one-way exit. Poor adoption may mean:

• Wrong problem statement → back to Define
• Wrong solution shape → back to Ideate or Develop
• New user segments emerged → back to Empathize

The diagram shows iteration arrows for a reason. Market learning is input to the next cycle, not a complaint queue.

A practical Market space starter kit

Before your next launch, document:

1. Beachhead segment - who adopts first, and why them
2. Adoption metric - one primary measure for 90 days post-launch
3. Launch owner - named role for rollout, training, and escalation
4. Feedback channel - how user pain after launch reaches the product team
5. Enhancement trigger - when you formally review Define success criteria again

If item three is blank, you are not in Market space yet - you are hoping.

Where this fits in the full framework

The Growth Diamond Model overview and Methodology guide explain how PSM and EDIDI connect. Solution space gets most workshop airtime; Market space is where practitioners separate themselves from poster sessions.

Double Diamond and Honeycomb models are strong through build. The Growth Diamond Model extends into market impact - because design thinking that stops at build does not change organizations.

Bottom line

Beyond build means beyond release. Market space is where you earn the right to say the user's problem improved - with evidence, adoption, and iteration.

Explore Implement in depth in the Academy. Applying this with a product or operations team? Book a 15-minute call.