What I Learned From My Last 90 Days (And What I Changed)

Most quarterly reviews produce a plan.

Mine produced a list of things to stop doing.

That felt like failure the first time it happened. Now I understand it’s the point. A review that only confirms what you’re already doing isn’t a review – it’s a ritual. The useful version is uncomfortable. It surfaces what you’ve been avoiding naming.

This is a walkthrough of my last 90 days. Not a highlight reel. Not a framework pitch. A real look at what I asked, what I found, and what I actually changed because of it.

How I structure the review

I use four questions. Same ones every quarter. The consistency matters more than the questions themselves – you start to see patterns across cycles, not just within them.

The four questions:

  1. What worked well enough to repeat?
  2. What consumed energy without producing results?
  3. What did I avoid, and why?
  4. What would I do differently if I started this quarter over?

I don’t start with metrics. Metrics come later, as evidence for what the questions already surfaced. Starting with numbers before questions is backwards – you end up rationalizing instead of reviewing.

The session takes about 90 minutes. I block it at the end of a week, not the start of a new one. Starting fresh feels good but it also makes it easy to skip the uncomfortable parts. Ending a period is a different headspace than beginning one.

What the last 90 days actually looked like

I’ll be direct about what I found.

What worked: Publishing on a consistent schedule. Not because the individual pieces were great – some weren’t – but because consistency created a baseline. I stopped making publishing decisions daily. The system made them. That removed a significant source of friction.

What didn’t: Three projects running in parallel, each with its own content cadence. On paper it looked manageable. In practice, context switching between them cost more than I’d accounted for. The output was there. The thinking wasn’t as deep as I wanted it to be.

What I avoided: Saying no to new angles that didn’t clearly fit the content plan. Every time something felt interesting, I added it to a “maybe later” list. That list has 23 items on it. That’s not a backlog. That’s distraction with good intentions.

What I’d do differently: I would have defined “done” for each project before starting the quarter. I had activity targets but not completion criteria. That’s a different thing.

The part that surprised me

I expected the review to surface productivity problems.

It surfaced clarity problems instead.

Most of what wasn’t working traced back to decisions I’d never actually made – I’d just started moving. The difference between a decision and a direction feels small when you’re inside a quarter. At the end of one, it’s obvious.

Two examples:

One content series I was running had no defined end. I kept publishing because stopping felt like quitting. But there was no reason it needed to continue – I’d covered the core material in the first four pieces. The remaining eight were filler with extra steps.

One collaboration I’d said yes to had a vague scope from the start. I kept showing up because I’d committed. But I’d never committed to anything specific – just to the relationship. The work kept expanding because neither of us had named what done looked like.

Both of these required a decision, not a system tweak.

What I changed

Three things. Not ten. Not a full restructure.

First: I cut the parallel content cadences to two active projects instead of three. The third moves to a defined hold – nothing published, but the foundation stays in place. This reduced my weekly decision surface immediately.

Second: I added a completion criterion to every ongoing series before the new quarter starts. One sentence: “This series is done when ___.” If I can’t fill in that blank, the series doesn’t continue.

Third: I closed the “maybe later” list. Not moved it – closed it. If something was genuinely worth doing, I’d remember it or re-encounter it. If I had to maintain a list to keep it alive, it wasn’t as important as it felt.

These aren’t dramatic changes. That’s deliberate. I’ve learned to be suspicious of quarterly reviews that produce dramatic plans. The review that tells you to rebuild everything is usually a review that happened too late.

What makes a review actually useful

The temptation is to use the review as motivation – to leave it feeling energized, with a full plan and a reset mindset.

That’s not what it’s for.

A useful review leaves you with fewer open questions, not more momentum. It should feel like a decision made, not a direction chosen. The energy comes later, from the clarity, not from the review itself.

The signal a quarterly review produces isn’t “here’s what to do next.” It’s “here’s what was actually happening, versus what you thought was happening.”

Those are different things. The gap between them is where the useful work is.

If you want the template I use – the exact four questions, how I structure the 90 minutes, and how I turn findings into decisions – it’s in the Solo Founder’s Quarterly Review. Free to download here.

Did you like this article? Share it with a friend!