4 Reasons to Build (Only One Is Your Portfolio)
A sanity framework for makers
Most creative frustration comes from a mismatch between what you’re building and why you’re building it.
You sit down to make something fun, then halfway through start worrying about whether it’s portfolio-worthy. You begin a strategic project, then resent it for not feeling meaningful. You want to build something important, but you’re too tired to think that big.
The problem isn’t the project. It’s that you’re running the wrong program.
Paul Klee, Insula Dulcamara, 1938. Oil on newsprint on burlap. Zentrum Paul Klee, Bern, Switzerland. Via Wikimedia Commons.
Mode 1: Recovery
Sometimes you build because you need to remember you can build.
This isn’t about output. It’s about proving to yourself that your hands still work, that your taste still exists, that the creative part of you didn’t die during that last brutal sprint or rejection or life implosion.
Recovery projects are small, private, and low-stakes. Redesign an app you’ll never ship. Make a playlist. Reorganize your notes. The point is motion, not achievement.
Mode 2: Play
Play is how you stay interesting.
It’s the 2am idea, the “what if I tried…”, the thing you’d be embarrassed to pitch in a meeting. Play has no ROI and that’s precisely why it matters — it’s where your actual voice develops, away from the pressure to perform.
The warning sign that you need more play: when everything you make starts to feel like everything else you’ve made.
Mode 3: Proof
Let’s be honest — some projects exist to get you hired, funded, or taken seriously. That’s not selling out; it’s surviving.
Proof projects are strategic. They demonstrate capability to people who don’t know you yet. They’re the highlight reel, not the behind-the-scenes.
The trap is living here permanently. Proof projects show what you can do, but they rarely show who you are. Build them when you need them, but don’t mistake them for the whole picture.
Mode 4: The Long Game
Some projects just won’t leave you alone.
They’re not necessarily grand or important-sounding. They might be a weird obsession, a question you keep returning to, a thing you’ve been circling for years without finishing.
I’d resist calling this “legacy” — that word implies you know what matters, and usually you don’t until much later. But there’s something to the projects that persist across different phases of your life, the ones that keep pulling you back.
You can’t force these. You can only notice them.
The real insight isn’t the categories — it’s permission.
Permission to build something that isn’t strategic. Permission to be strategic without guilt. Permission to not know which kind of project you’re working on until you’re deep in it.
Your creative life isn’t a portfolio. It’s an ecosystem. Different things feed different needs at different times.
The goal isn’t to perfectly sort your projects into boxes. It’s to stop expecting one project to be everything — and to forgive yourself when a recovery project doesn’t become a legacy, or when a proof project doesn’t feel meaningful.
Sometimes you’re just making something. That’s allowed too.