The concept one-pager: everything a decision needs on one page

The 30-slide deck went to the sponsor on Friday. On Monday she asked what the team actually wanted from her; nobody had read past slide six. The concept one-pager is the opposite document: nine fields, one page, read twice, decided in the room. Here is the template, a running example and the rules that keep it to one page.
When to use it
After a workshop you have clusters, not concepts. A cluster is a cloud of sticky notes with a label; a concept is something a person can test, fund or reject. The one-pager folds the cluster into one proposal and asks the sponsor for a specific decision. Write it when the decision is due and the person deciding was not in the room. With several clusters, write one page per concept and bring them to a decision workshop.
The template
Nine fields, in this order. One line of guidance each; the italic text is a running example, a refill station in stores.
- The problem. One sentence, including who has it. Customers who want less packaging leave our stores with as much plastic as everyone else, because there is nothing else on the shelf.
- The concept. Two sentences: what, for whom, how it is different. A refill station for our five best-selling cleaning products in three city-centre stores, for customers who bring their own containers. Unlike the bulk corners of organic shops, it sits on the main aisle at the same price per litre as the bottle.
- What we know. Three facts, each with a source. Reusable packaging was the most frequent request in last year's customer survey (customer service). Two competitors run refill pilots (store managers' quarterly report). Cleaning products carry the highest packaging weight per euro of sales (sustainability team).
- What we assume. The three riskiest assumptions. Customers bring a container rather than buy an empty one. The station stays clean with two checks a day. Staff take on the task without extra hours.
- The first test. What, with whom, how long, what it costs. One station in one store for six weeks, run by the store manager and two staff, with a rented dispenser. Cost 8.000 euros including staff time (estimate).
- Kill criterion and date. The number below which you stop, and the day you look. Fewer than 150 refills by 15 March. Below that we stop and write down why.
- What success looks like. The result that earns the next step. At least 300 refills, no hygiene complaint, staff time under one hour a day. Then we propose five stores.
- At full scale. Rough, one line each for people, money, time. People: one project lead, half a day a week per store manager. Money: around 15.000 euros per station (estimate). Time: one region within eighteen months.
- The ask. The decision wanted today: go for the test, no, or more information, and which. Yes to the six-week test in the pilot store, starting next month. If no, which of the three assumptions needs more evidence first?
The rules
- One page. If it does not fit, cut the concept description, never the assumptions.
- No pictures of the product unless it exists. A rendering turns an assumption into a promise.
- Every number has a source or says "estimate".
- Written by the owner, not the facilitator. The owner will run the test and defend the page.
- Sent two days before the decision. Long enough to read, too short to lobby.
- Read in the room for five minutes before anyone speaks. Say it out loud: "Five minutes of silence, then questions." It feels odd once and works every time.
Filling it from workshop results
- Pull the ideas of the cluster. Collect every idea with its context: who proposed it, what was said for and against, which questions stayed open. Tools like IdeaHone keep ideas and context together and record the decision afterwards; the who said what notes work too.
- Write the problem first. One sentence, with the person who has it. Leave the other fields until this one is sharp.
- List the assumptions from the open questions. What the workshop could not answer is what you assume. Keep the three that hurt most if the answer is no.
- Pick the test with the people who would run it. A test designed by the owner alone is twice as big as it needs to be.
- Write the concept last. With problem, assumptions and test on the page, the two sentences almost write themselves. Written first, they turn into a sales text.
- Get one sceptic to read it before the sponsor. Someone who voted against the cluster. If they find nothing missing, send it, and record the outcome in your decision log.
If field 1 takes more than one sentence, there are two concepts. Split them into two pages before you argue about wording.
A one-pager without field 9 is a report, not a request. The sponsor will nod, say "interesting", and nothing happens.
How a one-pager loses the sponsor's trust
- Selling instead of informing. Innovative, seamless, unique. The sponsor reads adjectives as a sign the facts were thin.
- Hiding the assumptions. A page with no risks is read as a page that has not looked for them.
- Estimates presented as facts. "8.000 euros" and "8.000 euros (estimate)" are different sentences. Only the second survives "where does that come from?"
- The page that grows to three. A market section here, a competitor table there. Put them in an appendix nobody has to read.
To draft a one-pager faster, use prompts that sharpen an idea into a concept.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
What is a concept one-pager?
A single page that turns a cluster of workshop ideas into one proposal a sponsor can decide on: problem, concept, facts, assumptions, a first test with a kill criterion, and the decision wanted today.
What should a concept one-pager include?
Nine fields: problem, concept, what you know (with sources), what you assume, the first test, kill criterion and date, what success looks like, rough full-scale effort, and the ask.
Who writes the concept one-pager?
The owner who would run the first test, not the facilitator. One sceptic reads the draft before the sponsor does.