I tell founders what to fix first, what it costs when they ignore it, and what can be left alone.

Problem

This was a deep-tech hardware startup, founder-led and growing fast. The founder had the feeling that most founders learn to recognize and few can name: the company was working hard and still losing motion somewhere between the meetings and the work. There were three suspicions—that leadership and communication were not landing, that the team was carrying more than it could sustain, and that the day-to-day was simply disorganized—and a wish for someone from outside to say whether they were real or imagined.

That is the harder half of an operations problem. The symptoms are legible from the inside; the cause almost never is.

Approach

No survey, no off-the-shelf framework dropped on top of the team. For two weeks I sat in the meetings and watched the work happen, then read what I saw against organizational sociology and project-management practice rather than against my own opinion. The brief was deliberately narrow: take the founder’s three concerns and test each one. Confirm it, complicate it, or rule it out.

The point of starting from observation is that it separates what a team feels from what is actually happening. The two usually overlap, but the gap between them is where the useful recommendations live.

What I found

All three concerns were real, and they were connected. The communication problem and the workload problem were not two problems; they were the same coordination failure seen from two angles. Meetings were absorbing the hours that focused work needed, decisions were being made and then quietly remade, and ownership was diffuse enough that effort leaked at the seams. The team was not short on capability. It was short on the structure that lets capable people stop colliding with each other.

I wrote it up the way I work: raw observations first, then the conclusions they supported, then recommendations at two altitudes: the big-picture changes worth making over months, and a short list of fixes the team could start the next morning.

Within weeks the team was presenting work with far less prep overhead, and the founder’s meetings took less of his time and gave him what he needed to decide faster.

The 80/20 fixes

The high-leverage moves, the ones that cost little and return the most:

• A check-in checklist so status updates stop eating meeting time and stay consistent across the team.
• The note-and-vote: write the memo, read it in silence together, then discuss. It surfaces dissent that talking-first rooms bury and shortens the meeting at the same time.
• Protect Monday mornings as deep-work time rather than spending them in the weekly status ritual.
• Defend focused work generally: fewer interruptions, clearer boundaries around the hours where the real work gets done.
• In-person where it counts. Some conversations are worth the room; reserve them for it instead of diffusing them across a chat thread.
• Accountability to time: meetings start and end when they say they will.
• Regular one-on-ones, so the conversations that do not belong in a group meeting have somewhere to go.
• Reduce the friction in Slack rather than letting it become a second, unmanaged inbox.
• A simple RACI, so every recurring piece of work has one owner and everyone knows who it is.
• A pre-mortem before the next big commitment: assume it failed, and ask out loud why, before it has a chance to.

The through-line under all of them is the same: move the right information to the person who has to make the call, and clear the performative motion out of the way.

None of these are clever. That is the point. The damage in a growing organization is rarely caused by a missing insight; it is caused by a dozen small coordination costs no one has the standing or the time to fix. An outside read gives a team permission to fix them.