First Principles

Make sure you’re solving the right problem.

First Principles

What this fixes

You’re stuck on a difficult problem, and every new idea sounds like a variation of an old one. The team keeps discussing, planning and trying things, but nothing seems to move forward.

This activity helps the team separate facts from assumptions, rebuild the problem from what is actually true, and find new ways forward.

How this works

A team says, “We need a better dashboard.” First Principles asks: What do we know is true?

Managers can’t see project status quickly. Teams use different reporting formats. Decisions are delayed because information arrives late. None of those facts mentions a dashboard. The dashboard was an answer; it wasn’t the problem.

Bring one real problem. Break it into pieces, separate facts from assumptions and pre-chosen answers, then rebuild the problem from what is actually true.

Team: one person runs the activity using the Facilitator Guide. Everyone else takes part.

Time required

Solo ✓   Team ✓

Solo: 15–25 minutes.   Team: 45–60 minutes, with a facilitator.

 

The time required is indicative and will depend on the nature of the problem and the size of the team.

The facilitator must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Bring a real problem the team is stuck on - one you’ve worked at for a while without a breakthrough.

Use it whenever:

  • every new idea sounds like a version of the last one
  • the team has “tried everything” and nothing has worked
  • you’re about to commit to a big solution and want to be sure it’s the right problem first
  • a problem has been around for months and won’t shift
  • the problem statement already names a solution (“we need a [tool/team/process]”)

What you get

A clearer problem.

  • Your problem stripped to what’s actually true - assumptions, legacy limits and hidden solutions removed
  • A rebuilt problem statement, often visibly different from the one you started with
  • A fresh set of options that the old problem statement was hiding

You’ve done it well when: the problem on the board at the end is not the problem you walked in with - and the team can see options it couldn’t see before.

What you’ll notice

  • Most of what you called “the problem” turned out not to be the problem
  • A solution had been hiding inside the problem all along
  • “What’s actually true here?” becomes a question you can ask out loud

Why this works

The way you define a problem decides which solutions you can even see. A problem statement carrying hidden assumptions and half-chosen answers quietly blocks the best options. Stripping it back to what’s actually true and then rebuilding opens up new options.

What you need

Everything comes in one kit. Here is each part, and when you use it:

Claim cards - blank (core). Give one small stack to each participant. During Step 2, everyone writes one statement per card. Each card should contain only one claim, assumption, legacy rule or proposed solution that appears inside the problem.

Four tag markers (Truth · Assumption · Legacy · Solution). Used in Step 3. After all Claim cards are on the board, the team tags each card with exactly one marker.

Test-prompt cards. Keep this deck face down beside the facilitator. Used in Step 3 when the team cannot agree on how to tag a card: the facilitator draws a card and reads the prompt aloud. The prompt helps the team decide whether the claim is really true, a legacy rule, assumed or a solution.

Starter-problem cards (optional). Short examples of stuck problems. Use one only if the team does not have a real problem of its own to work on. Otherwise, set them aside.

The board. Divide it into six areas before you begin:

  • Original Problem (top)
  • Truth
  • Assumption
  • Legacy
  • Solution
  • Rebuilt Problem (bottom)

By the end, the team can see what survived and what was removed.

Roles

  • Facilitator - runs the activity, manages time, draws Test-prompt cards when needed, resolves ties, and writes the rebuilt problem.
  • Participants - break the problem into claims, tag the cards, discuss disagreements, and help rebuild the problem.
  • Solo - you perform all roles yourself.

Steps

  1. Set up (2 min)

Team: Appoint a facilitator. Write the real problem you are stuck on at the top of the board, using the team’s own words.

Solo: Write your problem at the top of the board and begin.

  1. Break the problem into claims (8–10 min)

Working on your own, break the problem into smaller statements. Write one statement per Claim card.

Look for:

  • facts
  • assumptions
  • rules everyone accepts
  • proposed solutions already hiding inside the problem

Example: “We need a better dashboard.”

might become:

  • ✓ Managers cannot see project status quickly.
  • ✓ Teams use different reporting formats.
  • ✓ Information arrives too late.
  • ✓ We need a dashboard.

Don’t discuss yet. Just capture every statement you can see.

When everyone is finished, the facilitator places all Claim cards on the board.

Keep moving. Your first version is usually enough.

 

  1. Tag every claim (12–15 min)

Work through one card at a time. The facilitator reads it aloud and asks the team to tag it as:

  • Truth - we can show this is true.
  • Assumption - we believe it, but have not tested it.
  • Legacy - this comes from a past decision, rule or convention.
  • Solution - this is an answer, not part of the problem.

Use a quick show of hands if needed. If the team cannot agree, the facilitator draws a Test-prompt card and reads it aloud. After the discussion, the facilitator makes the final call.

  1. Keep only the truths (4–6 min)

Move all Truth cards into the Truth area of the board. Remove all other cards. The facilitator reads the surviving Truth cards aloud. Most teams discover that only a small number of claims remain.

  1. Rebuild the problem (8–10 min)

Using only the surviving Truth cards, the facilitator writes a new version of the problem at the bottom of the board. As a team, compare the rebuilt problem with the original problem at the top.

Ask:

  • Which words disappeared?
  • Are we solving the same problem we started with?
  • Does this version open up new options?
  1. Commit (4–6 min)

As a team, decide which new problem statement - or which new option it revealed - you will act on first. Assign an owner and a date. Before ending, write down the question to reuse:

What’s actually true here?

Output / Takeaways

  • A version of the problem built only from what is true
  • A rebuilt problem statement, compared against the original
  • One new option or next step to act on this week - with an owner

Important rules

  • If you can’t show it’s true, it comes off the board
  • One claim per card - break compound statements apart
  • Every claim gets exactly one tag
  • Rebuild the problem using only the Truth cards
  • Compare the rebuilt problem with the original before deciding
  • Leave with a next step, not just an insight

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.