Planning is the most productive-looking way to procrastinate.
You can give it a full afternoon. You can give it a whiteboard, a template, and a colored pen. In the end, you have a document that feels like evidence, and you can say with a straight face that you worked on the quarter.
I've done it. I watch smart people do it all the time.
Why It Matters
Here's the trap. If you can't plan, you can't prioritize. If you're not prioritizing, you're planning the wrong things. The two are locked together, which most people figure out eventually, and then they stop there and call it a system.
There's a step before both.
Reflect. Then prioritize. Then plan.
Skip reflection, and you're sorting a list you never examined. Every item on it got there somehow. Some of them are real. Some are legacy, still on the list because they were on last quarter's list (this is why I love burning things down to ashes and rebuilding them). Some you added because your boss expected them, or because a version of you from five years ago would have. Even if you prioritize that list well, you're still executing somebody else's quarter.
What You'll Learn
- Why planning feels like progress and often isn't
- What reflection actually asks, in four questions
- How to tell a real priority from one you inherited
- Why goals quietly die at the prioritizing step
- What to do when the reflection you need has to come from somewhere else
What reflection actually means
It's a vague word, so here's the concrete version. Reflection is looking backward at real evidence before you look forward.
Reflect on the last quarter. What actually happened, not what you intended. Reflect on how the work felt, because that's data too, and most people throw it away. Reflect on the lessons, including the ones you earned the hard way and would rather not revisit.
Four questions will do it:
- What did I keep saying yes to that I'd take back?
- What did I finish that nobody needed?
- What was on the list all quarter and never moved?
- What did I dread, and was the dread about the task or about the
person attached to it?
That takes less than ten minutes, not an afternoon. The reason people skip it isn't time.
People skip the uncomfortable
Reflection produces answers you have to act on or reveal decisions you made you wish you hadn’t.
The clearest example is goals. People set a goal without asking what they'd have to prioritize in order to reach it. Then the prioritizing turns out to require giving something up, or adding something they don't want to add, and that's the moment the goal quietly dies. Not at the goal-setting stage, where everything is still free. At the implementation and execution stage, where it costs.
The other one is the priority you've been carrying that was never yours. Something you call a priority because your boss said so, or society did, or you did once and never revisited. Reflection surfaces that, and then you have to either recommit to it out loud or put it down.
If your boss hands you eight priorities, that's a list, and the sorting will happen either way. Better that it happens out loud, with your boss in the room.
The journalist test
Here's how to get evidence instead of opinion.
Imagine a journalist followed you for a day and wrote down what they saw. Would they write that you're living the priorities you claim? Or would they write that you're worried about a health metric, and you just stopped for fast food, and you haven't moved yet today?
That gap is the whole finding. Sometimes it means you need to protect the time. Sometimes it means the thing isn't your priority and never was, and you've been paying interest on the guilt for years. Both answers are useful, and only one of them requires work.
Sometimes the reflection has to come from outside
A client asked me to fix a meeting. They'd already shortened it, tightened the agenda, and cut a name off the invite.
The meeting wasn't the problem. A director was attending alongside his own senior manager, which made his presence redundant, and he constantly inserted himself. Nobody in the room wanted to say so, because he sat at the top of the hierarchy and everyone else had a career to think about.
Last episode I asked whether you're quietly disempowering someone by making them loop you in on everything. This is what that looks like with a face on it, and he'd have told you he was being supportive.
It took an outside consultant to ask, and I only got to ask because I had nothing to lose. I said the presence seemed redundant. He told me he was there to support his senior manager.
So I asked him how. In what specific ways was he supporting her?
He answered it himself. "I'm talking over her. I'm saying what I think first, which means everybody's going to think what I think, because I'm at the top of the hierarchy."
That's reflection. It just needed someone to ask the question, because he was never going to ask it of himself. If you manage people, that's worth sitting with. The reflection your team needs most is usually about you, and they won't volunteer it.
Then prioritize, then plan
Once you've reflected, prioritizing gets easier, because you're sorting a list you believe in. And planning gets faster, because you're scheduling work that deserves the slot.
A quick note on where you're starting from. There are three levels: essential, relentless, and radical, and they move with the season you're in. I go through all three here: The Three Levels of Prioritization
And if you want the version of this argument aimed squarely at the optimizing we all do instead:
Relentless prioritization beats endless optimization. Every time.
Want a mini-course and playbook to guide you in reflecting, prioritizing, and planning? Check out the Powered Path Program.
FAQ
What does "reflect, prioritize, plan" mean? It's the order the three have to happen in. Reflection looks backward at what actually happened. Prioritization decides what deserves the time. Planning schedules it. Most people start at planning, which means they're scheduling a list they never examined.
How long should reflection take? No more than ten minutes and four honest questions beats an afternoon and a template. What did I keep saying yes to that I'd take back, what did I finish that nobody needed, what never moved, and what did I dread?
Isn't planning the same as prioritizing? They're linked, and they aren't the same. Planning is sequencing and scheduling. Prioritizing is deciding what earns a place at all. You can build a beautiful plan for the wrong quarter, and it will look like work the entire time.
Why do my goals keep dying? Usually at the prioritizing step. A goal is free to set. Reaching it requires giving something up or adding something you'd rather not, and that's where most goals quietly stop. Ask what the goal costs before you commit.
How do I know if something is really my priority? Imagine a journalist followed you for a day. Would their notes match your stated priorities? If they wouldn't, either protect the time or admit the thing isn't a priority. Both are honest answers.
What if the thing I need to reflect on is my boss? Then someone outside probably needs to ask the question, or a version of it that focuses on the work rather than the person. "In what ways is this helping?" is often enough, and it's a question anyone can ask without accusing anyone.
Resources
- The Right Things First: A Pocket Guide to Relentless Prioritization, available for teams in packs of ten or more
- Questions about copies for your team
- Episode 129: Ways We Optimize Instead of Prioritize
- The three levels of prioritization
- Powered Path Program and playbook
