Designing Your Life
Leaders & Managers
DropRegion · Lessons from Designing Your Life · Bill Burnett & Dave Evans

What Leaders and Managers Can Learn from Designing Your Life

Managing a team means you're expected to have answers, which makes it easy to treat a stuck team dynamic or your own flattening motivation as a fixed condition of the job rather than something worth examining. Designing Your Life's approach — get curious about what's really going on, test changes small before rolling them out wide, and keep checking decisions against what actually matters to you as a leader — works well against that habit. It won't hand you a formula for managing people, but it gives you a steadier way to work the problem than either pushing through or waiting for a clean answer to arrive.

01 · The Book in One Minute

The whole book, compressed

01Get Curious About What's Actually
02Pilot The Change Before You
03Get Clear On What Kind
04Imagine A Few Different Paths

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

What's different for your conditions

Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.

Your decisions ripple through other people's workdays immediately, so an untested change carries visible cost.
You're evaluated on team output, which pressures you toward quick fixes over slower investigation.
Org structure, budget, and your own manager set real limits on what you can experiment with.
Admitting uncertainty about your approach can feel like it undercuts the confidence your team needs from you.

0 of 4 selected

03 · Core Lessons

The core lessons, applied to you

Get Curious About What's Actually

Get curious about what's actually not working

The idea

Instead of assuming a team problem is just "how this quarter goes" or a fixed trait of certain people, treat it as a question you haven't investigated yet.

What it looks like

A manager notices morale sagging after a reorg and assumes it's normal change fatigue that will pass on its own. Three months later, two strong performers quit, and only in their exit conversations does she learn the real cause was unclear ownership between two teams that nobody had actually named or asked about.

Try this

Once a week, pick one team friction point and turn it into a specific question — "who actually feels unclear on priorities right now, and why?" — then ask two or three people directly instead of guessing from your own vantage point.

Pilot The Change Before You

Pilot the change before you roll it out

The idea

Before announcing a new process, structure, or policy across the whole team, try it in miniature first.

What it looks like

A department head rolls out a new project-tracking system to the entire org at once after reading about it in a single article, without testing it with even one team first. Three weeks in, it's clear the tool doesn't fit how half the teams actually work, and unwinding it costs more time than the pilot would have.

Try this

Before any team-wide change, run it with one small group for two to four weeks, and explicitly ask them what should change before it goes further.

Get Clear On What Kind

Get clear on what kind of leader you actually want to be

The idea

It's easy to inherit a leadership style from a former boss or company culture without ever checking whether it fits you or the outcomes you actually want.

What it looks like

A manager keeps running meetings the same command-and-control way her first boss did, though it visibly drains her and shuts down the input she says she wants, because she's never stopped to ask what kind of leadership actually reflects her own values.

Try this

Write down the three qualities you want people to experience working for you, then compare them honestly against how your last few meetings or decisions actually went.

Imagine A Few Different Paths

Imagine a few different paths your leadership role could take

The idea

Rather than assuming the next step is automatically a bigger title or a bigger team, it's worth sketching a few different directions your role could grow into — deeper specialist influence without more direct reports, a lateral move into a different part of the organization, or the path you're already on — and noticing which one you'd actually choose if all were equally available.

When the clusters compete

Curiosity and small pilots take time your team's urgent needs won't always allow. When a decision genuinely can't wait, make the fastest reasonable call, and put the slower investigation on the calendar for right after — don't let "no time to test" quietly become "never test."

04 · Choose Your Priority

Name one thing, honestly

What's one thing about how your team operates that you've assumed is fixed but have never actually asked anyone about?


Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.

05 · Put It Into Practice

The practices from this edition

Once a week, pick one team friction point and turn it into a specific question — "who actually feels unclear on priorities right now, and why?" — then ask two or three people directly instead of guessing from your own vantage point.
Before any team-wide change, run it with one small group for two to four weeks, and explicitly ask them what should change before it goes further.
Write down the three qualities you want people to experience working for you, then compare them honestly against how your last few meetings or decisions actually went.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Write down the three qualities you want people to experience working for you, then compare them honestly against how your last few meetings or decisions actually went.

07 · Remember This
If you remember only 4 things
01Get Curious About What's Actually. Instead of assuming a team problem is just "how this quarter goes" or a fixed trait of certain people, treat it as a question you haven't investigated yet.
02Pilot The Change Before You. Before announcing a new process, structure, or policy across the whole team, try it in miniature first.
03Get Clear On What Kind. It's easy to inherit a leadership style from a former boss or company culture without ever checking whether it fits you or the outcomes you actually want.
04Imagine A Few Different Paths. Rather than assuming the next step is automatically a bigger title or a bigger team, it's worth sketching a few different directions your role could grow into — deeper specialist influence without more direct reports, a lateral move into a different part of the organization, or the path you're already on — and noticing which one you'd actually choose if all were equally available.
08 · Your Next Step

What will you do differently because you read this?

This is a compressed starting point. For the fuller process, read Designing Your Life by Bill Burnett and Dave Evans.