Twelve forced choices, about ten minutes, for you alone. There are no good or bad answers — but there is no way to pick all three, which is the whole point of it.
"Is this even possible?"
Builds the crude thing that proves an idea can exist at all. Most attempts fail — that is the price of the ones that don't.
"Who actually needs this, and why?"
Takes the rough prototype and turns it into something people can rely on without asking whoever built it.
"How do we make this cheap and boring?"
Turns a working product into a utility: measured, automated, predictable, dull by design.
| side by side | Pioneer | Settler | Town Planner |
|---|---|---|---|
| Produces | A crude prototype that proves a thing can exist | A product people trust, with users, docs and an ecosystem | A utility: SLAs, automation, volume, low unit cost |
| Wins by | Exploring fast, failing often | Listening, refactoring, productising | Measuring, optimising, removing variance |
| Failure rate | High, and expected | Moderate | Low, and unacceptable |
| Allergic to | Requirements, process, "what's the return on this" | Half-finished toys, and scaling before anyone has adopted it | Snowflakes, undocumented magic, surprises |
| Horizon | Weeks | Quarters | Years |
| Sounds like | "Let's just build it and see." | "Have you watched anyone actually try to use this?" | "What happens when this fails at three in the morning?" |
For each set, mark the one statement that is most like you and the one that is least like you. Answer for how you actually work, not how you think you should.
Now forget preference. Split ten points across the three to describe what the last three months of your work really looked like or future work will requiere of you.
The label is the least interesting part. These three questions are the reason to have done it.