I wrote earlier about meetings as a tax. That piece was the symptom. This one is the disease.

The disease is a missing structural loop. Three rules. Each one supports the others. Most companies have none. A few have one. Almost no one has all three — which is why senior leaders everywhere find themselves doing junior work, junior people stop growing, and meetings somehow produce less every year.

The rule most people see is the meeting rule. Two types of meetings: stop me or I proceed, or find my blind spots. Companies read about that rule, try to copy it, and discover the meetings still drift. Half-baked thinking still arrives. Senior people still over-help.

That is because the meeting rule is the visible tip. Underneath it sit two rules that almost nobody copies — and they are the rules that make the meeting rule actually work.

Let me start at the top, where the reader already is, and work down to the bedrock.

The two meeting types are simple.

Type 1 — Stop me or I proceed. I have done the work. I have decided. I am bringing this to you so you can spot what is wrong. If you cannot, I proceed after this meeting as a direct result of it.

Type 2 — Find my blind spots. Here is the situation. Here is what I have already worked through. What am I missing?

Both types require a finished piece of work to walk in with. Type 1 cannot survive without one — there is nothing to stop. Type 2 cannot survive without one either — there is nothing to stress-test.

So far this is mechanics, and most operators reading this are nodding. Yes, fine. Two meeting types. Demand pre-work. Got it.

Here is what they miss. The meeting rule is enforcement. It does not produce the finished work. It only checks for it. If the rest of the system has not produced finished work in the first place, the meeting rule has nothing to enforce. The Type 1 review becomes a review of half-baked thinking. The Type 2 stress-test becomes the room cooking the thought together. The meeting rule, alone, fails.

Companies that try to adopt this rule without the rules underneath it discover this within a quarter. Meetings drift back to the loo-break discussion they were supposed to prevent. People conclude "this Amazon stuff doesn't work for us." It does work. They copied the wrong layer.

Underneath the meeting rule is a quieter rule that does most of the work.

A document is either a draft or it is finished.

The label matters. "Draft" is a public confession: I am not yet done with my work. The author is telling the room — do not review this seriously yet, the thinking is incomplete.

You do not put "draft" on something casually. You are signalling your state honestly. And you do not strip "draft" off casually either. The day you remove the label, you are publicly committing: this is the work, hold me to it, find faults if you can.

That label carries weight because the system has decided it carries weight. People honor the draft state by not pretending the work is finished. People honor the finished state by reviewing it as if their judgment matters.

This rule is what makes the meeting rule survivable. Without it, every author has the option to claim their work is finished when it is not. The reviewer cannot tell what they are looking at. The author cannot say "I am not done" without losing face. So everything gets presented as if finished, and nothing actually is. The Type 1 meeting fails because the "finished" paper was a draft in disguise.

The status rule fixes this. It gives the author a way to be honest about state without losing face — I am still drafting is a legitimate status — and it gives the reviewer a way to read the artifact accurately. Both sides know what they are looking at.

But the status rule cannot enforce itself. It can only label what exists. If nothing exists — if the work has not been written down at all — there is nothing to label. Which brings us to the bedrock.

Work is a paper.

Not a slide. Not a verbal update. Not a thought you have been turning over in your head. A written document, in prose, with the thinking finished and visible on the page.

If it is not written, it is not done.

The reason is not ceremony. Writing forces a kind of thinking that talking cannot produce. When you write a six-page narrative, you discover the gaps in your logic. You notice the assumptions you had been smuggling. You see which parts you can defend and which parts you have been hand-waving past.

A meeting cannot do this for you. A meeting moves at the speed of speech, with interruptions, with the loudest voice winning, with the person who has not thought about it asking questions already answered on page two. The hard thinking has to happen before the meeting, alone, in writing. The meeting confirms or rejects what the writing already settled.

This is the rule almost no one copies. Companies will adopt the meeting types. They will sometimes adopt the draft label. Almost none will commit to the artifact rule, because the artifact rule has a cost — it requires every senior person to spend hours alone, writing, in a culture that has trained them to "be visible" by being in meetings.

But this is where the loop terminates. Without the artifact rule, the status rule has nothing to label. Without the status rule, the meeting rule has nothing to enforce. Take this one rule away and the entire stack collapses, no matter how disciplined the meeting culture above it pretends to be.

The three rules together form a forcing function so strong that even average people will rise to it.

The artifact rule forces solitary thinking. You cannot write a finished document while sitting in a meeting. You have to leave, sit alone, and do the work.

The status rule makes that work publicly visible. You cannot hide an incomplete state. The label commits you.

The meeting rule makes the public state consequential. A draft cannot survive a Type 1 review. A finished paper invites the room to find faults — which it will, ruthlessly, because that is what the meeting is for.

Each rule is necessary. None is sufficient. Without all three, the path of least resistance wins. And the path of least resistance — for any human, no matter how disciplined — is to think out loud in a meeting, because that is easier than thinking alone at a desk.

The loop does not produce completeness by exhortation. It produces completeness by making it the only behavior that survives.

When the loop holds, every level of the organization becomes a craft.

Think of building cars. At the bottom, someone owns the tyre. Their scope is one component, and they deliver it complete — ready to ship.

One level up, someone owns the assembly. They take complete tyres, complete brakes, complete steering, and put them together into a working chassis. They do not rework the tyre. They integrate it.

Above them, someone owns the whole car. Above them, someone owns the fleet — the portfolio of products the company sells.

At every level, the maturity of output is identical. What changes is scope. The tyre owner integrates one set of tradeoffs. The fleet owner integrates customer segments and competitive positioning. Same craft. Different canvas.

This is what the loop is for. It is not a meeting hygiene tool. It is the structural protection that lets each level deliver its craft, completely, without dragging the level above into doing the work.

Inside the loop, the work at every level looks the same.

One. Inspect what comes up to you from below. The artifact arriving on your desk is supposed to be a complete piece of work at that level. If it is not — if it is a draft labeled as finished — reject it and send it back. Do not fix it. Do not absorb it as your own. Hold the gate.

Two. Do your level's craft. Alone. In a focused, solitary, high-intensity thinking mode that the rest of your day rarely allows. This is the work you are actually paid for. It does not happen in meetings. It happens in the hours you protect for thinking — reading, drawing, writing, running numbers, considering angles nobody handed you.

Three. Once your work is finished — not before — take it to peers and stakeholders. Not to think. To stress-test. You are looking for what you were blindsided on. Different angles, different lenses, different experiences. Integrate what is useful. Document what is contested.

Four. Take to your senior only what genuinely needs the next level's judgment. Calls that require a wider scope than yours. Tradeoffs that touch their canvas, not yours. Bring those up cleanly, with all factors visible, in the form: here is what I have decided, here is why, here is what I am uncertain about, stop me or I proceed.

That is the job. Every level. Same four moves, different scope.

Here is where this gets uncomfortable.

If those four moves are the job, there is a fifth thing that is not the job. Teaching you how to do it.

At a senior level, no one is supposed to teach you how to do your craft. Figuring out how to do the work at your level is part of what you are paid for. Through peers. Through your network. Through reading. Through paying attention. Through doing it badly the first time and learning what to fix.

When you walk into your senior's office with "how do I approach this?" — you are asking them to do tyre work. They are working on the car. Their attention belongs there. The day they start answering "how do I approach this" questions is the day three things break: you stop growing, they stop doing their own work, and the whole stack collapses one level down.

This sounds harsh. It is not.

The senior who refuses to teach you is not being cold. They are respecting you enough to treat you as a craftsman at your level — not as a student who needs leading by the hand. The day they start teaching you is the day they have decided you cannot be trusted to figure it out yourself. That is the actual insult. The refusal is the compliment.

When the loop breaks, it breaks in two symmetric ways.

Senior over-helps. The senior person stops mid-meeting. Suggests a solution. Solves a problem two levels below their scope. Feels generous. Looks like leadership. Actually destroys the system. The junior person never gets the chance to discover that gap themselves. The senior burns thinking time on work that is not theirs.

Junior under-pushes. The junior person, faced with a senior suggesting an idea, accepts it. Writes it down. Says thanks. What they should have said: I considered that. Here is why I rejected it. Or: I had not considered that — give me a day to evaluate before we proceed. Either response keeps the work at the right level. "Thanks, I'll add it" hands the work upward and the credit downward.

Both failures look virtuous. Both feel like good meetings. Both are the disease.

The cost is invisible in any one meeting. It compounds. The senior, doing work two levels down, has no bandwidth left for the work only they can do — looking at the horizon, deciding which markets to enter or exit, which products to kill. They spend their year fixing tyres. The car drives off the road slowly, and nobody can quite say why.

If you are looking at your feet, you are not steering. That is the cost of breaking the loop. Not bad meetings. A car driven by someone who is too busy to look up.

Here is the test I now run on myself.

If anyone — anyone at all — can spend ten minutes listening to your work and give you a legitimate improvement you had not evaluated, when you have spent hours living, breathing, thinking, and validating the issue — you are fucked. You don't know your job.

Not because you missed one idea. Everybody misses ideas. But because the quality of your thinking was so shallow that a stranger, in a tenth of your time, beat you on a dimension you should already have considered.

Run the test on your last three reviews. The last three times you presented work to a senior. Did anything land that you had not already weighed and either incorporated or consciously rejected? If yes — what does that tell you about how complete your work was when you brought it?

Run the test on your team. The last three times your reports came to you. Did you find yourself "adding" obvious improvements? Or were you genuinely catching the rare gap they could not have seen from their level?

If you are constantly adding obvious improvements, your team is operating one level below where they should be. If you are constantly receiving them — you are operating one level below where you should be.

The diagnostic is uncomfortable. It is also the cleanest test I know.

Most "fix your meetings" advice is downstream. Pre-reads. In-reads. Decision-only meetings. Useful. Worth doing.

But meeting hygiene cannot fix what a missing loop produces. If your organization has not decided that work means a paper, that draft means not-done, and that meetings demand finished thinking — no amount of pre-read discipline will save you. The senior will keep over-helping. The junior will keep under-pushing. The bandwidth at the top will keep getting eaten by work two levels below.

The loop is the upstream fix. Three rules. Each one ruthless about a single thing — produce the artifact, label your state, gate the meeting. Together they create the only environment where completeness at every level becomes the path of least resistance instead of the heroic exception.

That is the work you owe your level. Not effort. Not loyalty. Not visibility. Completeness — produced through writing, signaled through status, enforced through meetings.

Stop me or I proceed.

Not the only way. Probably not even the best way. Just one practitioner's version that worked.

~Discovering Turiya@work@life