Founder pricing available until . Lock founder rate 10% discount Use code FOUNDER2025.

Ends inUse FOUNDER2025

Get OnePlan
Clarity.

One page to a single, confident decision

See OnePlan

Clarity. Value Map Framework

A value-based system to make confident choices simple.

What the Value Map does

It turns a messy question into a decision-ready brief: one recommendation, explicit trade-offs, and a single owned next step.

Why it works

  • Focus on outcome and stakes.
  • Trade-offs made visible: Risk · Speed · Cost.
  • One clear recommendation, no drift.

When to use it

  • High-stakes or ambiguous priorities.
  • Competing options causing delay.
  • Cross-team alignment needed fast.

Format

Default to one page for simplicity, speed and clarity. The more simple the information, the easier it is to understand and act on.

If required, keep page 1 as the decision summary (WHY · WHAT · HOW · NOW). Move detail, assumptions, and evidence to an appendix or linked artefacts. The output is valid if it follows the framework and keeps the summary tight.

Why it's repeatable

  • Same four blocks every time: WHY · WHAT · HOW · NOW.
  • Checklist-driven intake; consistent share-and-capture loop.
  • Page-1 summary preserves speed even when depth grows.

How we gather input: the ACA stance

ACA guides discovery so the Value Map has honest, decision-ready inputs. It is a stance, not a script.

Acknowledge

  • Reflect their words to confirm understanding.
  • State the challenge and outcome in their language.
  • Reduce defensiveness and surface candid context.

Compliment

  • Recognise clarity, foresight, or useful constraints.
  • Reinforce good framing and evidence-based thinking.
  • Increase openness to trade-offs and focus.

Ask

  • Probe urgency, stakes, constraints, and prior attempts.
  • Target gaps that affect Risk · Speed · Cost.
  • End with a single owned next step to keep momentum.

Use and scope

  • Apply primarily in Phase 1: Gather; echo in Map and Deliver.
  • Keep it natural. Guide the conversation, do not interrogate.
  • Supports our gates: enables confident action and makes choices simple.

Value Map Framework at a glance

PHASE 1: Gather

Understand context and constraints.

  • Identify priority question.
  • Clarify desired outcome and why it matters now.
  • State stakes if wrong or delayed.
  • Note constraints (time, capacity, budget, urgency).
  • Review signals and prior attempts.

PHASE 2: Map

Translate insight into value structure.

  • WHY: Outcome, urgency, stakes.
  • WHAT: One recommendation or decision.
  • HOW: Risk, Speed, Cost, tools/principles.
  • NOW: Next step with deadline/owner.
  • Sanity-check: Value is visible and ownable.

PHASE 3: Deliver

Create and deploy the summary, then attach depth if needed.

  • Lead with the "so what”.
  • Default to one page; see Format guidance.
  • Share in deliverables, onboarding, follow-ups.
  • Capture reactions and blockers surfaced.

Why it works

  • Predictable and repeatable: the same structure every time prevents drift.
  • Cuts complexity: keeps only what matters so teams can act.
  • Keeps momentum: turns uncertainty into the next clear step.

Execution checklist

Use this before sharing: complete, owned, and decision-ready.

Identify the priority question or challenge.
Clarify desired outcome and why it matters now.
Make stakes explicit if wrong or delayed.
Capture constraints: time, team capacity, budget, urgency.
Review signals: past insights, deliverables, external factors.
Write the single recommended course of action.
Explain the mechanism via Risk / Speed / Cost.
Specify the next step with a deadline and owner.
Default to one page. Lead with the 'so what'. See Format guidance
Share, capture reactions, note blockers surfaced.

Clarity. Value Map Framework - Cheat Sheet

Applied detail so you can use the framework without guesswork.

PHASE 1: Gather - Do

  • Ask: "If we solve this, what changes?”
  • Push for measurable outcomes.
  • Surface hard limits early.

PHASE 1: Gather - Avoid

  • Vague goals with no clear impact.
  • Skipping prior attempts or data.
  • Ignoring constraints until late.

PHASE 2: Map - Do

  • WHY in client language.
  • WHAT as one clear recommendation.
  • HOW via Risk, Speed, Cost trade-offs.
  • NOW as a specific, owned step.

PHASE 2: Map - Avoid

  • Overloading with options.
  • Using jargon that obscures urgency.
  • Hiding trade-offs or assumptions.

PHASE 2: Map - Why

  • Frames decisions in the client's language.
  • Presents one clear path.
  • Makes trade-offs visible.
  • Assigns clear ownership.

Why value-based measurements?

We use Risk, Speed, and Cost because these are the trade-offs leaders weigh in almost every significant decision:

  • Risk: Decide which risks to avoid or accept.
  • Speed: Determine how quickly value will be realised.
  • Cost: Understand investment across Time, Effort, Money.

Together, they make trade-offs explicit and ownable.

FAQs

Why one page?
It forces clarity and speeds agreement without slide bloat.
What if it won't fit?
Use two pages. Keep the same sections and lead with the “so what”.
Where should it live?
In your normal doc or ticket tool so owners and deadlines are visible.
See OnePlan

We use cookies to analyze traffic. See our  Privacy Policy.