Product Thinking
Measure outcomes, not outputs, and decide what not to build.
What you will learn in this lesson
You will learn to think like a product person. You will measure whether your design helped and choose what to leave out.
Outputs vs. outcomes
An output is something you made. A screen. A form. A feature.
An outcome is a change in people's lives. Fewer families turned away. More customers who come back. Less time on hold.
Teams often ship lots of outputs and change nothing. Product thinking keeps the focus on outcomes.
| Output | Outcome |
|---|---|
| A "What to bring" page | Fewer families turned away for missing papers |
| A wait-time text alert | Fewer customers who drive away |
| A one-page league sign-up | More parents who finish sign-up on the first try |
How will you know it worked?
Pick one or two simple measures your partner can track. Keep them easy. A tally sheet at the front desk counts.
- Pantry: "How many people were turned away this month?" Compare before and after.
- Barbershop: "How many customers say they checked the wait first?"
Decide what not to build
Every partner has more ideas than time. Product thinking means saying no, kindly and on purpose. One simple way to sort ideas:
| Low effort | High effort | |
|---|---|---|
| High impact | Do first | Plan carefully |
| Low impact | Maybe later | Skip |
Start with the smallest version that solves the main problem. People call this a minimum viable product, or MVP. For the pantry, the MVP might be a printed checklist and a text message. A full app can wait until the simple version proves the need.
Judgment check: who carries the burden of a bad build?
Small businesses and nonprofits have few staff. A tool they can't maintain becomes a burden. Ask your partner: who will update this? What if that person leaves? A simple tool that lasts beats a complex one that breaks.
Reflection
Quiz: Outputs or outcomes?
Go deeper: Product Management: Building the Right Thing, a Temerarii Media playbook.