Audit your recurring meetings.
If nobody can say what decision it produces, cancel it for two weeks and see who notices.
Process should save time, not spend it.
Week one: access and introductions.
Week two: one real task with a clear finish.
Week three: feedback.
Week four: expectations for month two.
A plan that fits on a sticky note gets used.
There's a gap nobody names.
Too big for the admin to run HR. Too small to justify a $250k HR hire or a $2M consulting engagement.
Most founders sit in that gap for years and call it fine.
If they resigned this morning, who does the thing tomorrow?"
"Seniority" is a statement about scope.
"Critical" is a statement about dependency.
https://t.co/UYGzbs1VZC
If the meeting falls apart the week you're out, it was never a system.
It was you, holding it together in real time.
Build it so the work runs without you in the room.
You have a job to do, and part of your job is leading your people, but not all of it.
So, why does the 'people' part consume so much?
https://t.co/wSReCea23U
Teams don't break gradually. They break at multiples of 3 and powers of 10.
10 people, you're the hero.
30 people, that stops working.
100 people, the culture can't be "felt" anymore. It has to be designed.
Most founders try to solve 100-person problems with 30-person tools.
"What if I don’t want more? Then I’m not ambitious enough?"
Who is asking you to want more?
Do they have what you want?
If not, there's nothing to listen to.
Carry on.
Your business is paying a "Founder Tax" of at least 25% of your total income every year.
The gap between 'what you can do' and 'what you should do' is your Bottleneck Tax.
Stop paying the tax. Get your score: https://t.co/7dOnnyCM8B
Most founders think their business is scaling when it's actually just getting bigger.
Scaling means the business grows without you doing more. Getting bigger means you're handling more.
If you run a team of 20 to 80 people, this was built for you: https://t.co/do1CEuYhD5
Most founders hire to fill gaps, not to build the structure.
The correct question to hire for: who is needed for this part of the business to run without me?
That is a different conversation, with a different outcome.
The GROW model comes after feedback.
Goal: where do you want to be in 6 months?
Reality: where are you now, and what is in the way?
Options: what could you try?
Will: what are you committing to, and by when?
The difference between managing and developing is this model.
When did you last give feedback to a direct report that was specific enough that they knew exactly what to do next?
One clear Action. One clear Impact. One clear Direction.
Managers give feedback in generalities because specifics feel aggressive.
Wrong.
Specifics are helpful.