Am I improving the work, or just slowing my team down?

You call it thoroughness. Your team calls it a wait. Both of you are right, and that is the problem. You are not failing at judgment — you are running two different jobs through one gate, and you never decided which one goes first. One job is making the work better. The other is keeping the work moving. They are not enemies, but they cannot sit at your desk at the same time. When you open a review, you owe your team a clear answer: which job are you doing right now? No one taught you where the line sits, so you have been drawing it by feel — review after review, and feeling worse each time. Too soft, and quality slips. Too hard, and people stop trusting the process. They start working around you instead of with you.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

This is mostly a habit to build with a team, not a concept to master, so guidance leads while a short reframe anchors it.

How the two dials adapt to you →

What’s really going on

Set the line before you open the file. Decide what "good enough to ship" means before you read a word. Then ask, for each change: is this required, or only preferred? Required, fix it now. Preferred, name it and let it go. One job at a time — never both.

🔒 What you’ll build togetherUnlock by starting

A moveBefore you review anything, say out loud which job you're doing: raising the bar, or clearing the queue.

A moveWrite down, with your team, what counts as broken versus what counts as better — before the next review, not during it.

A moveLabel every note you give as 'required' or 'suggested.' Never leave one unmarked.

A moveSet a time limit for each review before you start it, and stop when it ends, like anyone else would have to.

A moveOnce a week, ask whoever is waiting on you: did my last review help you, or hold you up? Believe what they say.

PractiseRequired or Preferred · a Pod of 4 · 30 min

What changes unlock by starting

You stop guessing whether you're helping or stalling — you have a rule instead of a feeling.
Your team knows what to expect from your reviews and stops padding schedules around you.
You catch yourself polishing work that was already good enough, before you burn another day on it.
The reviews that truly matter get sharper, because you're not spending judgment on the ones that don't.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.