Skip to content
Founders’ price Launch pricing for your first twelve months. 40 Playbooks, 40% discount for Founders. View the playbooks →

We keep building things people don't use.

By , Editor · · Playbooks for Leaders

Concept and planning by Will Rowan. Researched and drafted with AI. Edited and checked by Will Rowan.

01Position

“We keep building things people don't use.”

The feelingIgnored.

We keep building things people don't use. A leadership Playbook film: where you stand, the Play to choose, the tools in sequence, and the leaders who made the same call. Captions available.

If that’s where you are right now, this is the Playbook built for exactly that moment.

“Built, not used” is one of 40+ Playbooks for Leaders Playbooks, for leaders facing a specific, real situation. In under fifteen minutes it helps you recognise what’s actually going on, then gives you a clear way through: the Play to choose, the Plan in concrete moves, the Precedents of people who faced it before, and your next move.

Frameworks you’ll see put to work on this exact decision, applied, not taught in the abstract:

  • Opportunity Solution Tree
  • Dual-Track Agile
  • Solution Interviews

You’ll also see how it played out in the real world, Erika Cardona at Colombian Red Cross, Bogotá, and Melissa Hanna at Mahmee, Los Angeles (2014). Real precedents, not platitudes.

It leaves you with one question to carry into your next conversation: “How many alternative solutions have you actually considered for the opportunity you’re about to commit”

Part of the Discovery & Understanding collection, Playbooks for when you don’t yet understand the problem, the customer, or what to build. See them all ›

Transcript: read it in full

What to do when you keep building things people don't use

Cundinamarca and Bogotá, Colombia. The Colombian Red Cross runs shelters for women and girls, including women displaced by violence. Erika Cardona is its Director of Humanitarian Affairs there. The shelters run courses that help people find work, and workshops in social and life skills, so they can start over.

A parent with young children cannot sit through a course with nobody to look after them.

So beside the training there is a safe space for children. In Cardona's words: we have a safe space for children, where they feel free to have fun and play while their mothers and fathers attend training courses.

When you keep building things people don't use, ask what people would need before they could use it at all, and whether you built that too. The Red Cross put the childcare beside the training.

So let's go to the office and work through it.

First read why the work is being ignored

"We keep building things people don't use."

The feeling is ignored.

The product ships. The features are intelligent. The team is talented. And the engagement numbers say what they say. Every release is greeted with the same polite indifference, and the indifference has stopped being a surprise.

Two choices. They look like the same engagement problem. The first move is different.

When the team is in love with its own ideas

Choice one: the team has fallen in love with their own ideas. The work is emotionally invested in the elegance of what's being built. The feedback loop from users has been politely ignored because it contradicts the investment.

If that's the read, make them watch. Sit the developers and designers in a room with a screen recording of a real user failing to navigate their most recent feature. No commentary. No defending the design. Just watching.

Jakob Nielsen has been clear about this for thirty years. The feedback users give you in interviews is polite. The feedback they give you by struggling in silence is not. And the silence is much harder to argue with. The goal isn't to humiliate the team. It's to break the emotional attachment long enough for the evidence to land.

When the pain simply isn't acute enough

Choice two: the problem isn't painful enough. The team has been solving real problems, just not problems users are prepared to change their workflow for. The work is well-aimed in principle and not well-aimed at anything the user is currently spending time being frustrated by.

If that's the read, ask the user what they currently do about it. If the answer is nothing, we just deal with it — kill the feature.

Teresa Torres, formalising what she calls continuous discovery, has named the test plainly. The absence of a current workaround is the clearest possible signal that the pain isn't acute. People build their own workarounds, however ugly, when the pain is real. If there is no workaround, there is no pain — and no amount of better product is going to create the pain to justify itself.

How to stop jumping to solutions too early

In-love-with-the-idea, or not-painful-enough. Same engagement problem. Two different first moves.

Three tools. The discipline is to stop the team from jumping to solutions before the problem has earned it.

Make every alternative solution visible

The first is

the Opportunity Solution Tree.

The Opportunity Solution Tree was developed by Teresa Torres and codified through her Product Talk writing and the two thousand and twenty-one book Continuous Discovery Habits. The framework draws on the deeper jobs-to-be-done tradition we covered in scenario twenty-one and the opportunity-discovery lineage that runs through the design-thinking literature. The tree is structural rather than novel — its value is forcing the team to make the discovery hierarchy visible.

The reason the Opportunity Solution Tree matters when you keep building things people don't use is that most we-keep-building-things-people-don't-use problems are we-kept-building-the-first-thing-we-thought-of problems in disguise. The team commits to the first solution that surfaces and never seriously considers alternatives. The tree forces the alternatives onto the page where they can be compared.

The unique insight is the branching structure. From a top-line outcome, the tree branches into customer opportunities (the pains and gains we have learned about). From each opportunity, it branches into possible solutions. Most teams discover, when they fill in the second branching honestly, that they considered exactly one solution per opportunity — the first one that came up — before committing.

What you get is a structural test for solution-space coverage. If a node has only one child solution, the team has not actually considered alternatives. The tree makes the lack of consideration visible without anyone having to accuse anyone of being unimaginative.

So. How to draw it.

Outcome. One sentence at the top. Increase weekly active users by twenty per cent.

Opportunities. Three to five pains or gains beneath, drawn from real customer evidence. Onboarding feels overwhelming. Hard to find the right feature. No reason to return next week.

Solutions. Per opportunity, three to five candidate solutions. Guided tour. Empty-state CTAs. Cmd-K search. Personalised home. Weekly digest. Streak. The structural value is the comparison — anywhere the tree has only one solution branch is where the team has been committing to the first idea.

Experiments. Per solution, what would you build and what would you measure to find out which actually moves the opportunity?

Depth before width — choose one opportunity, explore many solutions, test cheaply.

The tree is the working artefact, not the deliverable. It lives on the wall, gets updated as the team learns, and is the place the but we already considered that conversation gets settled by reference rather than from memory.

Test the solution before engineering starts

The second is

Solution Interviews.

Solution Interviews complement Problem Interviews (which we covered in scenario twenty-eight) and were formalised through the same lean-startup and customer-development tradition. Where Problem Interviews probe the customer's current pain and workflow, Solution Interviews probe whether the team's proposed solution actually addresses the pain in a way the customer would change their behaviour for. The deeper lineage runs through the concierge MVP tradition and the broader user-research practice formalised in tools like Maze, dscout, and UserTesting.

The reason Solution Interviews matter when you keep building things people don't use is that they put the candidate solution in front of users before engineering starts, not after. The disappointment surfaces while it is cheap rather than after the team has shipped.

The unique insight is the positioning between problem-validation and build. Most teams interview customers about their pain (problem validation) and then go straight to building. The middle step — testing the candidate solution — is the cheap one that gets skipped. The cost of skipping it is, typically, a feature that ships and doesn't get used.

What you get is a structural defence against shipping the wrong solution. The interview is short, cheap, and concrete. Here is what we are considering building. If we built it, would you use it? Show me when in your day you would use it. Show me what you currently do instead.

So. How to run it.

Pick. Same target segment as the eventual product. Compensate them. Schedule them inside a week.

Show. Low-fidelity sketch, wireframe, click-through prototype — whatever lets the user understand what is being proposed without the team committing to execution.

Ask. Not whether they like the solution. Walk me through what you currently do when you have this problem. The current workflow is the diagnostic; the candidate solution either fits into it or doesn't.

Watch. Where, in the user's existing workflow, would the candidate solution sit? If they can't tell you — or if it would require them to change their habits before they would use it — the candidate solution is unlikely to land.

Aggregate. Across five interviews, the candidate solution either survives or doesn't. The team that built it gets to learn this before the engineers commit a sprint to it.

Validate before you build, not after you ship

The third is

Dual-Track Agile.

Dual-Track Agile was popularised by Jeff Patton in his writing through the late two-thousands and twenty-tens — User Story Mapping (two thousand and fourteen) is the canonical reference — and traces back to the discovery and delivery split that Marty Cagan and the Silicon Valley Product Group have written about extensively. The framework runs two tracks simultaneously: a discovery track (validating problems and solutions) and a delivery track (building validated work).

The reason Dual-Track Agile matters when you keep building things people don't use is that the workflow makes it impossible to validate while the team is building. Most teams default to a single-track workflow — the engineers build whatever the product team has next, and validation happens (when it happens) after the build has shipped. The structural problem is that the workflow doesn't have a place for test the solution before commitment.

The unique insight is the parallel-track structure. Discovery and delivery don't take turns; they happen simultaneously. The discovery track is one or two weeks ahead of the delivery track. By the time engineering starts on a feature, that feature has been through Solution Interviews and validated against the Opportunity Solution Tree. The team isn't validating after they ship; they're validating before they build.

What you get when the workflow is dual-track is a structural mechanism for keeping the team out of building things people don't use. The discovery track does the testing; the delivery track only gets work that has already been tested.

So. How to organise it.

Discovery. Interview customers. Frame opportunities. Prototype solutions. Test assumptions. The track for figuring out what to build — product, design, research — running Concept Testing and Solution Interviews on candidate features.

Delivery. Plan sprint. Build. Ship. Measure in production. The track for actually building it — engineering — taking on features that have passed discovery.

Handoffs. A feature only crosses from discovery to delivery when discovery has produced sufficient evidence that the feature will be used. The team agrees what sufficient evidence means in advance — usage signal from prototype, qualitative interview saturation, quantitative test result.

Discovery always runs one cycle ahead of delivery. The temptation under deadline pressure is to skip discovery on the easy features — that's exactly how teams accumulate the unused-features problem the workflow is supposed to prevent.

The framework is the structural solution to the build-things-people-don't-use problem. Every feature has a discovery record before it has a delivery commitment.

A precedent: the tool was fine, the theory of uptake was not

That's the toolkit. One more story before we close.

The Red Cross story we opened with put the childcare beside the training. The story we close with is a founder who started with a tool, and grew a care team of her own.

Two thousand and fourteen. Melissa Hanna, who trained in law and business, founds Mahmee with her mother, Linda Hanna, a nurse and lactation consultant. Mahmee sets out to close the gaps in American care for mothers and babies.

Hanna first builds it as software that the healthcare industry would pay to use.

Mahmee grows instead into a company with its own care team of nurses, doulas and lactation consultants, who work directly with new and expecting parents. In two thousand and nineteen parents pay twenty to two hundred dollars a month. In May two thousand and twenty-two Hanna tells MedCity News: closing gaps in care and eliminating systemic racism requires more than just apps. By November two thousand and twenty-five over sixty million people have Mahmee covered by their insurance.

So.

The Colombian Red Cross built the childcare its training depended on. Hanna at Mahmee started with a tool, and grew a team to do the job. Two different cuts at the same question: what would people need before they could use what you built?

When you keep building things people don't use, there is a version of the problem where the product is right and the sales process is wrong. There is another version, less comfortable, where the honest question is whether the job needs a tool at all, or people to do it.

The Red Cross built the childcare. Hanna built a care team.

So. Your Next Move from this playbook.

How many alternative solutions have you actually considered for the opportunity you're about to commit to — or have you been defending the first idea since the start?

What’s inside All 40 Playbooks

Two behavioural Plays. Each positions you differently for the next conversation. You choose.

Play A

A named stance, with the outcome it sets up.

Play B

The counter-stance for the same moment.

  1. A Plan of tools

    Tools from the Toolbox, in order, each ending in Your Next Move: one concrete instruction.

  2. Precedents

    Leaders who stood here. We show whose play worked, half-worked, and shouldn’t have been attempted.

The full Playbook includes the video walkthrough, both Plays in full, the Plan tool by tool, how each precedent played out, and your next move.

“The list was never the hard part. Standing behind the cut, in the next three conversations, is.”

The close

Sources & further reading 3 Positions, 4 Plays, 3 Plans, and 2 Precedents.

Your Next Move

Questions, answered

How does a Playbook work?

A Playbook names your Position, hands you two Plays to choose between, then turns your choice into a Plan: a sequence of tools, each ending with a single concrete move. It closes on Your Next Move: the one thing to do before the day ends.

How long is a Playbook?

Around fifteen minutes. Short enough to watch in the gap before the meeting it’s made for.

What’s the difference between this and asking AI?

A chatbot gives you an answer. A Playbook gives you a Position, a chosen Play, a Plan, and Precedent: the structure of a decision, not a paragraph of advice. You open the situation you’re in rather than describing it from scratch.

Do I need to watch them in order?

No. Each Playbook stands alone. You open the one that matches the situation in front of you, and there’s no sequence to follow and nothing to complete first.

What is Your Next Move?

The single concrete move you leave with: a question to take back into the room and answer there. Every tool in a Plan ends with one. It’s the answer to the question the brand name asks.

Next on the shelf

Your next playbook
Share this Playbook ->