Design Your Life Like a Side Project

You’re stuck because you’re trying to figure out the answer before you take the action. You’ve read the books. You’ve made the spreadsheet. You’ve done the values audit. You’re still in the same job.

Bill Burnett’s Designing Your Life makes the case that career planning, the way most people do it, is structurally broken. You’re trying to write a story you haven’t lived yet. That’s not planning - that’s fiction.

The shift Burnett offers is borrowed from product design: stop planning, start prototyping. Test cheap. Fail small. Learn fast. Treat your life like a side project.

Let me show you what that actually means in practice.

Stop trying to find your passion

The passion search is a trap. It assumes there’s a hidden right answer inside you, and if you just think hard enough, journal long enough, or do enough personality tests, you’ll find it.

You won’t. Not because you’re broken. Because that’s not how preferences work. You don’t find passion by introspecting. You build it by doing things and noticing what energizes you.

This is the first hard pivot Burnett asks for. Drop the “what’s my one true calling” question. Replace it with: “what’s a small thing I can test this month?”

Your first move

Pick three career directions you’ve quietly fantasized about. Not the “realistic” version. The actual ones. Maybe it’s writing. Maybe it’s consulting. Maybe it’s a totally different field.

Now, for each one, design a 30-day prototype. Not a career change. A test.

The test should be small enough that you can do it without quitting anything, cheap enough that failure costs you almost nothing, and real enough that you’ll learn something you didn’t know before.

A prototype is not:

• Buying a domain name
• Reading three more books
• Taking another course

A prototype is:

• Doing the actual work for one real client (paid or free)
• Spending five hours building the thing you’d build if you were doing it for a living
• Having three conversations with people who actually do the job

Notice the difference? Prototypes produce contact with reality. Research produces more research.

The 5-hour test

Here’s the simplest prototype you can run this week. Pick one of your three directions. Block five hours of focused time. Do the work of that direction, as if you were already in it.

If it’s writing - write a real piece, polish it, ship it somewhere.

If it’s consulting - pick a friend’s business, run an actual diagnostic, deliver real recommendations.

If it’s a creative pivot - make the thing, finish it, get it in front of someone who isn’t your mom.

The five hours is the magic number. It’s long enough that the novelty wears off and you encounter what the work actually feels like - including the boring parts. It’s short enough that you can do it on a Saturday without rearranging your life.

After the five hours, ask yourself one question: did time disappear, or did it drag?

That’s it. That’s the data. Not “do I love this?” but “did I lose track of the clock?” If yes, run another five-hour test. If no, cross it off and move on.

Build evidence, not theories

Most stuck people are theory-rich and evidence-poor. They have elaborate models of their career and almost no real-world data about what they actually like doing.

Reverse that ratio. Spend less time analyzing and more time generating evidence.

Every prototype is a piece of evidence. You’re not trying to find the answer in one experiment. You’re building a portfolio of small data points that, over six months, gives you something concrete to decide with.

This is the same logic behind why side projects die - most of them die because people scaled up too early, before they had any evidence the thing was worth scaling. Prototype, then commit. Not the other way around.

Reframe failure as data

Here’s the part that messes most people up. They run one prototype, it goes badly, and they take it as a verdict on the whole direction.

A failed prototype is not a failed dream. It’s information. It tells you something about which part didn’t fit - the work, the audience, the format, the conditions. The next prototype gets to be smarter.

I’ve watched people abandon a direction after a single bad test, only to realize months later that they tested the wrong version of it. They had the right idea, just the wrong prototype. The work wasn’t the problem - the conditions were.

You don’t get this kind of clarity from journaling. You only get it from running enough tests to spot the pattern.

Talk to humans who are doing it

This is the prototype Burnett emphasizes hardest and most people skip. Three conversations with people actively doing the work you’re considering. Not motivational coaches. Not authors of books about the work. The people doing it now.

The conversation isn’t “give me advice.” It’s “walk me through last Tuesday.” Real questions about real days. What was annoying? What did you avoid? What surprised you? What does the work actually look like at 3 PM on a regular Tuesday?

That’s the version of the job you’re signing up for. Not the keynote-speaker version. The Tuesday version.

If you don’t know anyone in the field, the introvert’s networking playbook is a softer way in. You don’t need to network like an extrovert. You need three honest conversations.

Run prototypes, not pilots

A subtle but important distinction: a pilot is a smaller version of the final thing. A prototype is a test designed to learn something specific.

Don’t try to build a small version of your future business. Build a test that answers the one question you’re stuck on. Different question, different prototype.

• Stuck on “will I like this work?” → run the 5-hour test
• Stuck on “will anyone pay for this?” → run the one-client test
• Stuck on “can I sustain this energy long-term?” → run the 30-day rhythm test

Each prototype has a single learning goal. Don’t try to test everything at once. You’ll just confuse the data.

Your homework

This week, pick one of your three directions. Design one prototype. Schedule the five hours. Put it on your calendar like it’s a paying client meeting - because it kind of is. You’re the client. You’re paying with your time, and the deliverable is data about your own future.

Don’t tell anyone you’re doing it. Don’t post about it. Just run the test.

Then run another one next week.

By the end of two months, you’ll have eight data points about your own preferences. That’s more than most people accumulate in a decade of thinking about it.

The career you actually want is on the other side of testing, not theorizing. Go run the first test. The clarity you’ve been waiting for shows up in the doing, not in the deciding.