Every leadership team I talk to describes the same symptom. Things move slowly. Decisions take weeks. Work gets handed between functions and loses fidelity at every pass. The diagnosis is almost always the same word: communication. So they add a sync. They add a status document. They add a project manager whose job is to move information between the people who already have it.
A year into building Nika Finance, we had the same symptom and reached for the same fix. We were three people building a consumer finance product across five lines at once, and we started scheduling check-ins to keep the work aligned. Product sync. Engineering sync. User feedback review. It sounded responsible.
Then we looked at what those weeks had actually produced. Execution was fine. Everything that shipped, shipped. What had stalled was decisions. We were not blocked on skill or capacity. We were blocked on waiting for a scheduled moment to decide something that any one of us could have decided on the spot.
That is not a communication failure. Nobody was uninformed. It was an ownership failure, and the meetings were the symptom rather than the cure.
Meetings are what you schedule when nobody is allowed to decide
Watch where recurring meetings come from. Almost none of them are created to share information, because information can be written down and read asynchronously by anyone who needs it. They get created because a decision is pending and no single person has the standing to make it alone.
So the calendar becomes the approval mechanism. The work waits for Thursday. On Thursday four people discuss something one person already understood well enough to resolve on Monday, and the organization treats the delay as the cost of alignment.
The tell is easy to check. Take any recurring meeting and ask what would break if it were cancelled tomorrow. If the honest answer is that certain calls would go unmade, that meeting is holding a decision hostage. If the honest answer is that some people would be less informed, it should have been a written update.
What we replaced it with
We collapsed nearly every internal meeting and put one rule in its place. If you own it, you ship it. If it breaks, we fix it together.
Ownership at Nika is assigned by surface, not by function. One person owns a product area end to end, including the calls that in a larger company would route through product, design, and engineering as three separate approvals. That person makes the decision, ships it, and the rest of us see it in production. We flag it if something looks wrong. That almost never happens, and when it does, the correction costs less than the meeting would have.
The second half of the rule matters as much as the first. Ownership without shared responsibility for failure produces defensive behavior, because people stop shipping anything they might be blamed for. Attaching collective repair to individual authority is what makes the authority usable.
The result was not only faster shipping. The work got better. When the decision-making layer and the execution layer are the same layer, feedback loops run in days rather than quarters. A user reports an issue, we trace it, one of us fixes it, and it ships. No handoff. No approval chain. Nothing degrades in translation, because there is no translation.
Why this holds outside a three-person team
The obvious objection is that this is a story about being very small, and that it stops working at scale. I would put it differently. Three people did not give us the principle. Three people made it impossible to avoid the principle, because we had nobody to hand the problem to.
Larger organizations can hide the same defect for years. The handoffs absorb it. The coordination roles absorb it. The cost shows up as slowness that everyone accepts as the price of being a real company. It is not the price of scale. It is the price of separating the authority to decide from the responsibility to execute.
The scaled version of the rule is not a flat structure. It is a specific discipline about where authority sits. For any recurring decision, one named person should be able to make the call without convening anyone, and that person should be close enough to the work to feel the consequence. When you cannot name that person, you have found the meeting you are about to schedule.
What this does for retention
The retention effect surprised me more than the speed did.
People do not generally leave because the work is hard. They leave because the work is not theirs. When every meaningful call gets escalated, reviewed, and softened by three layers above, the job becomes assembling recommendations for other people to approve. That is the experience most talented operators are describing when they say they feel stuck, and no amount of compensation or culture programming fixes it, because the problem is structural rather than emotional.
Give someone real ownership of a surface and the calculation changes. The work carries their judgment. The outcome is legible and attributable. That is a far stronger retention mechanism than most of what sits in a formal engagement program, and it costs nothing except the willingness of leadership to stop being the bottleneck they complain about.
The takeaway
Before adding another sync, run one audit. List the decisions your organization made in the last month and mark who could have made each one alone. If most of them required a meeting, you do not have a communication problem, and another channel will not fix it. You have distributed the authority to decide away from the people doing the work, and the calendar is where that shows up.
Move the authority back. The meetings disappear on their own.
Frequently Asked Questions
Is this just a case for having fewer meetings?
No. Fewer meetings is the outcome, not the intervention. Cutting meetings without moving decision authority produces the same delays with worse information flow. Assign ownership first and the calendar corrects itself.
How do you assign ownership without creating silos?
By pairing individual authority with shared responsibility for failure. One person decides and ships; everyone repairs what breaks. Silos form when ownership includes protection from consequences, not when it includes the right to act.
What about decisions that genuinely need several people?
Those exist, and they deserve a real conversation. The test is whether the decision requires negotiation between competing constraints or merely requires approval. Negotiation earns a meeting. Approval means the authority is sitting in the wrong place.
Does this work in a regulated or high-risk environment?
The controls change, not the principle. Where a decision carries legal or safety exposure, the review is part of the work rather than a management layer over it. The failure to avoid is routing a routine call through a senior approver who adds no information and only adds delay.
How do you know if you have this problem?
Look at what your recurring meetings are actually resolving. If the pattern is a group ratifying something one attendee already knew the answer to, the meeting is compensating for authority that was never delegated.
Be the first to comment