The framework existed long before the book did.

Every pattern in Scarcity Algorithm was something I had been living, observing, and applying across two decades of product and technology work. The ideas were not new when I started writing. They were already fully formed. I had been running the logic in my head, applying it to decisions, using it to diagnose problems in organisations I worked with.

I just had not written it down.

Not because I was not ready to write. Because I kept finding reasons why the timing was not quite right. The day job was demanding. The ideas needed more refinement. I wanted to validate the framework further before committing it to paper. I needed to complete the MSc first. I needed to wait until I had more consulting experience to draw on.

Every reason was legitimate. Every reason was also a deferral mechanism dressed as diligence.

The framework I eventually published in Scarcity Algorithm is not materially different from the one I had in my head three years before I started writing it. The delay did not improve the output. It just delayed the compounding.

That is the readiness threshold. And it is the most expensive habit highly capable people have.

What the readiness threshold actually is

The readiness threshold is the moving standard a capable person applies to their own work before they will commit it to the world.

It is not a quality standard. Quality standards have fixed criteria. You either meet them or you do not.

The readiness threshold has no fixed criteria. It moves. Every time you approach it, it recedes. You refine the idea, and the threshold demands more refinement. You gather more evidence, and the threshold demands more evidence. You wait for the right moment, and the right moment keeps arriving slightly later than wherever you currently are.

This is not procrastination. Procrastination is avoidance of work. The readiness threshold operates on work that is already done, already good, already real. It is the gap between the work being ready and the person deciding to release it.

The distinction matters because the solutions are completely different. Procrastination responds to accountability and structure. The readiness threshold does not. It responds to a direct challenge to the belief system underneath it.

Why intelligent people are most vulnerable

The readiness threshold is specifically a trap for high-capability individuals.

There is also a specific mechanism at work in analytical minds. Intelligence evolved to model risk. The more capable the mind, the more thorough the risk model. In a high-stakes decision with real uncertainty, this is an asset. Applied to the question of whether to publish a piece of thinking, it produces an infinite loop.

Every reason to release the work generates three reasons to refine it further. Every counter-argument against waiting generates a more sophisticated version of the waiting argument. The simulation never terminates because the environment keeps supplying new variables faster than the model can evaluate them.

I know this loop from the inside. I ran it for years on the framework that became the book.

The cruel irony is that the better your thinking, the more convincing your reasons for not yet sharing it.

What it costs

The readiness threshold does not feel expensive while you are in it. It feels responsible. Conscientious. Like the mark of someone who takes their work seriously enough to get it right before releasing it.

The cost only becomes visible in retrospect.

There is the direct cost: the compounding that did not happen because the work stayed private. Every piece of thinking that stays in a notebook rather than in the world is a piece that cannot be found, cannot generate a response, cannot build a reputation, cannot route an opportunity toward you. The work is doing nothing. The capacity that produced it is occupied with refining something that is already good enough.

There is the indirect cost: the market does not wait for you to be ready. While the readiness threshold is moving, other people are shipping. Not because their work is better. Because they made a different decision about the cost of imperfection.

And there is the compounding cost: visibility builds on visibility. The first piece you publish makes the second piece easier to find. The second makes the third easier. The reputation compounds from the moment you start, not from the moment you feel ready. Every month inside the readiness threshold is a month the compounding clock is not running.

I waited three years to write down a framework I had already built. That is three years of compounding that did not happen. Three years of people who needed the thinking not finding it. Three years of the career coach conversation not yet having happened.

The cost of the readiness threshold is not the imperfect work you might have released. It is the compounding you did not start.

What the threshold is protecting

Understanding the readiness threshold requires naming what it is actually protecting, because it is not protecting quality.

It is protecting against the specific discomfort of being seen and found wanting.

When work stays private, it remains perfect in potential. It could be the best version of the idea. It could land with exactly the right reader. It could change the conversation. None of that potential can be disproved because the work has never been tested.

The moment it is released, it becomes real rather than potential. Real things can be criticised. Real things can be ignored. Real things can fall short of the internal standard that justified the delay.

The readiness threshold is the defence mechanism that keeps the work in the state where it cannot fail, because it has never been tried.

This is what makes it so resistant to logic. You cannot argue someone out of a threshold by pointing to the quality of the work. The threshold is not about the work. It is about the exposure.

The only thing that moves the threshold is a direct decision to accept the cost of being seen.

What moves it

The framework that eventually became Scarcity Algorithm did not get written when I felt ready. It got written when I ran the Scarcity Filter on the decision to keep waiting.

Is deferring the writing scarce work or abundant work?

Abundant. Refining an idea that is already complete is abundant work done by me. It produces no new output. It generates no signal. It builds no leverage. It keeps me comfortable in the quadrant that costs the most.

Is waiting until the timing is right protecting the scarce work or feeding the abundant?

Feeding the abundant. The timing question is the intelligence trap in its purest form. Understanding the right moment to act feels like progress. It is not. It is the most comfortable place to hide from the risk of exposure.

Once you apply the filter to the readiness threshold itself, the threshold loses its authority. It is not a quality standard. It is not a timing mechanism. It is abundant work dressed as diligence. And every hour inside it is stolen from the compounding that starts the moment you decide to release.

The framework was ready three years before I wrote it down. The book was ready before I queried it. The newsletter was ready before I made it public.

What changed was not the work. What changed was the decision about the cost of waiting.

Effort loses its memory. The compounding that does not start because you are not yet ready loses its memory too.

Decide. Ship. Let the market correct you. That is the only sequence that builds leverage.

Key Points

• The readiness threshold is not a quality standard. It is a moving standard with no fixed criteria. Every time you approach it, it recedes. Recognising it as a mechanism rather than a metric is the first step to breaking it.

• Intelligent people are most vulnerable to the readiness threshold because their analytical capability generates more sophisticated reasons to wait. The better your thinking, the more convincing your deferral arguments become.

• The cost of the threshold is not the imperfect work you might release. It is the compounding you do not start. Visibility builds on visibility from the moment you begin, not from the moment you feel ready.

• The threshold is protecting against exposure, not protecting quality. Work that stays private remains perfect in potential but generates no signal, no feedback, and no leverage.

• The Scarcity Filter applied to the readiness threshold: deferring complete work is abundant work done by you. It produces nothing new. It is the intelligence trap in its purest form.

Consider and Act

• Name one piece of work that has been complete for longer than three months and has not been released. What specifically is the readiness threshold requiring before you will publish it? Write it down.

• Run the Scarcity Filter on the decision to keep waiting. Is refining complete work scarce or abundant? Is the work doing anything while it stays private?

• Calculate the compounding cost. If you had released the work three months ago, what signal would it have generated by now? What relationships might it have started? What opportunities might it have routed toward you?

• Identify the specific exposure the threshold is protecting against. What is the worst realistic outcome if you publish the work as it stands today? Is that outcome worse than three more months of no compounding?

• Set a publish date for the piece of work you named above. Not when it is ready. A date. Treat it as a constraint, not a target. Constraints force the simulation to terminate. Targets allow it to extend indefinitely.

Every organisation I walk into at this stage has revenue. It has headcount. It has ambition.

And somewhere between the strategy deck and the quarterly results, something is not converting.

The default diagnosis is always the same. We need better talent. We need a clearer strategy. We need to move faster on AI.

None of those are the real problem.

The real problem is structural. The decision layer has collapsed.

What the decision layer is

Every organisation has three layers that need to function independently and connect cleanly.

The first is strategy. What are we building, why, and for whom. The second is decision architecture. Who decides what, at what speed, and with what authority. The third is execution. The work that delivers on the decisions that serve the strategy.

In a healthy organisation these layers are distinct. Strategy informs decisions. Decisions direct execution. Each layer has its own owners, its own rhythm, and its own accountability.

In most growth-stage organisations I encounter, the decision layer has quietly disappeared.

The people who should be deciding are executing. The people who should be executing are waiting for decisions that never arrive clearly enough to act on. And the leadership team is running the organisation from inside the execution layer, which means nobody is holding the structural picture.

This is not a talent problem. The people are capable. This is not a strategy problem. The direction is usually clear enough. It is an architectural problem. And architectural problems do not respond to personal improvement solutions.

What it looks like from the inside

The meeting happened. The analysis was thorough. The options were presented clearly.

Nothing was decided.

This is the signature pattern. Leadership teams that are technically excellent at evaluating options and structurally unable to close on them. Every decision becomes a further analysis. Every analysis generates new variables. Every new variable extends the timeline.

Meanwhile the organisation is moving, but not in a chosen direction. It is moving in the direction of whatever has the most internal momentum, the loudest voice, or the most urgent client.

That is not strategy. That is drift with a slide deck.

The individual contributor experiences this as constant context switching and unclear priorities. The middle layer experiences it as being asked to execute on things that keep changing before they are finished. The leadership team experiences it as never having enough information to decide with confidence.

All three experiences are symptoms of the same structural failure.

What AI is doing to this

Every organisation I speak to right now is somewhere on the AI adoption curve. Most are in the experimentation phase. Some are in the deployment phase. A small number are in the compounding phase.

The difference between those groups is not the AI tools they have chosen. It is the structural condition underneath the tools.

AI amplifies what is underneath. If the execution layer is strong and the decision layer is clear, AI compounds the throughput. If the decision layer has collapsed and execution is running on momentum rather than intent, AI accelerates the drift.

I see this repeatedly. Organisations that deploy AI productivity tools into a structurally misaligned team do not get more output from the right work. They get more output from the wrong work, faster.

The volume of execution increases. The quality of the decisions directing that execution stays exactly the same. The gap between activity and compounding widens.

Most AI consultants do not talk about this because most AI consultants are selling the tools, not diagnosing the structure underneath them. The structural question gets bypassed in favour of the deployment question. And the deployment lands on a foundation that was already fragile.

The four signals of a collapsed decision layer

After running the diagnostic across organisations at different stages, four patterns appear consistently.

First, the leadership team is involved in decisions it should not need to make. Not because the team below lacks capability but because the authority structure is unclear enough that everything escalates by default.

Second, the time between a decision being needed and a decision being made is longer than the pace of the market requires. The analysis is thorough. The outcome is late.

Third, the same strategic questions keep reappearing in different meetings. Nothing is fully closed. Everything is provisionally agreed. The organisation is re-litigating its own positions on a quarterly cycle.

Fourth, the people with the most institutional knowledge are the most operationally buried. The judgment that should be shaping decisions is trapped in execution, which means the decisions being made are informed by less of the picture than they should be.

Any one of these is a signal. All four together is a diagnostic.

What the structural fix looks like

The fix is not a new strategy. It is not a new hire. It is not a new AI tool.

It is a decision architecture review. Who decides what. At what level. With what information. By what deadline. With what escalation path.

This sounds administrative. It is not. It is the most leverage-generating work a leadership team can do at the growth stage because every downstream problem traces back to it.

Talent retention traces back to it. The best people leave organisations where their judgment is neither sought nor acted on. That is a decision architecture problem wearing a culture label.

AI ROI traces back to it. Tools deployed into a structurally misaligned organisation generate activity, not compounding. That is a decision architecture problem wearing a technology label.

Leadership pipeline traces back to it. People do not develop into decision-makers in organisations where decisions are not clearly owned. That is a decision architecture problem wearing a talent label.

The structural question most organisations avoid is not which AI tools to deploy. It is who holds the picture when strategy, talent, and AI all need to connect.

That position does not exist inside the functional silos. It sits above them. And in most growth-stage organisations it is currently vacant.

Key Points

• The decision layer is the structure between strategy and execution. In most growth-stage organisations it has quietly collapsed, and no amount of talent, strategy, or AI investment fixes a structural problem.

• AI amplifies what is underneath. Deployed into a misaligned structure, it generates more output from the wrong work, faster. The deployment question cannot precede the diagnostic question.

• The four signals of a collapsed decision layer: leadership involved in decisions it should not make, slow time from decision needed to decision made, same strategic questions re-litigating on a quarterly cycle, best judgment trapped in execution.

• Talent retention, AI ROI, and leadership pipeline development all trace back to decision architecture. They are structural problems wearing functional labels.

• The position that holds the picture when strategy, talent, and AI all need to connect does not exist inside the functional silos. In most growth-stage organisations, it is currently vacant.

Consider and Act

• Map the last five significant decisions in your organisation. How long did each take from identification to closure? What was the cost of that timeline?

• Name the three decisions your leadership team re-litigates most often. What would need to be true for each of those to be permanently closed?

• Run the Scarcity Filter on your team’s weekly calendar. How many hours are in the Scarce + Me quadrant (structural decisions, judgment calls, irreplaceable thinking)? How many are in Abundant + Me (execution, status updates, coordination)?

• Identify the person in your organisation with the most institutional knowledge and the least decision authority. That gap is your most expensive structural inefficiency.

• If AI doubled the output of your execution layer tomorrow, would your decision layer be able to direct that output toward the right work? If the honest answer is no, that is where to start.

Eighteen months ago a career coach told me something I had not heard before.

Not about my work. Not about my capability. About my visibility.

“You are probably one of the most unique individuals I have met. But you are lacking the visibility to get it into the right rooms.”

I had spent sixteen years building things that worked. Greenfield technology projects that had never existed before. Teams built, led, and developed across product and technology at scale. The results were real. The track record was unambiguous.

And almost none of it was visible.

Not because I had hidden it. Because I had assumed the work would speak for itself. That excellence, sustained long enough, would eventually be selected. That the right people would notice, connect the dots, and the recognition would follow the performance.

It does not work that way anymore. It probably never did. But in the AI era, the gap between the two has widened into a structural divide.

What changed

Classical selection was slow. A career built through institutional progression gave time for track records to accumulate and reputations to travel. Your manager knew what you had built. Their manager heard about it. Seniority was partly a signalling system, even if an imperfect one.

That system has been disrupted at every level simultaneously.

At the individual level, the market is saturated. Everyone has credentials, everyone has results, and AI has made competent execution available to anyone with a subscription. The question is no longer who is best. It is who is legible enough to be selected.

At the leadership level, internal mobility has compressed timelines. The decision about who gets development, sponsorship, and visibility is made faster and with less context than it used to be. The person who is excellent but invisible does not lose on merit. They simply do not appear in the frame when the decision is made.

At the company level, investors, clients, and partners are filtering on signal before they evaluate substance. A founder with a clear, consistent public position gets a different kind of attention than a founder with equivalent results and no visible framework.

In all three cases, the same mechanism is operating.

Recognition does not follow performance anymore. It precedes it.

Why excellent people stay invisible

There is a specific failure mode I see repeatedly. Capable, genuinely scarce individuals who have built something real and have almost no external signal to show for it.

It is not modesty. It is not a lack of confidence. It is a structural misunderstanding about how value gets selected in saturated markets.

The assumption is: build something excellent, let it speak, wait to be found.

The reality is: in a saturated system, excellent work that stays local is indistinguishable from work that does not exist. The selection mechanism cannot find what it cannot see.

I call this the local execution trap. The work is real. The capability is real. But it never leaves the room it was built in. And a room, however impressive, has a ceiling.

What scarcity without signal looks like

The career coach did not tell me I needed to be better.

He told me I needed to be seen.

That distinction matters because the response to each is completely different. If the problem is capability, you build more capability. If the problem is visibility, you build signal. Doing more excellent work in response to a visibility problem is the most common and most expensive mistake I have seen senior professionals make.

I had been doing it for years.

Every project I delivered that nobody outside the organisation knew about. Every framework I built that lived in a slide deck. Every result I produced that became a footnote in someone else’s quarterly review. Excellent, local, invisible.

Scarcity without signal is just depth. And depth, however real, does not compound. It accumulates in a room that eventually you leave, taking it with you, with nothing portable to show for it.

What changes when visibility comes first

The career coach session did not immediately solve anything. But it reframed the problem.

I stopped asking how to do better work. I started asking how to make the work legible to the systems that select for it.

That meant writing the framework down. It meant publishing the thinking, not just living it. It meant building a body of work that could walk into rooms I was not in, be read by people who had never met me, and signal something specific about what I see and how I think.

My book Scarcity Algorithm is part of that. Scarcity Economics is part of that.

None of it required me to become someone different. All of it required me to make what was already scarce visible to the people it was most relevant to.

The practical shift

If you recognise the pattern in yourself, the shift is not complicated. It is uncomfortable.

The work that builds signal is the work you have been deferring because it feels exposed. The piece you have not written because you are not sure it is ready. The position you have not taken publicly because you are not certain enough. The framework you have not named because naming it makes it real and therefore criticisable.

That discomfort is not a warning signal. It is the signal that you are in the right quadrant.

Scarce work done by you and made visible is the only thing that compounds across time, context, and room changes.

Everything else, excellent, local, unshared, loses its memory.

Recognition now precedes performance. Build the signal before the room needs to see the work.

Key Points

• In saturated markets, selection filters on signal before it evaluates substance. Being excellent is necessary. Being visible is non-negotiable.

• The local execution trap is not a capability problem. It is a distribution problem. Doing more excellent work in response to a visibility gap is the most expensive mistake senior professionals make.

• Scarcity without signal is just depth. Depth does not compound. It accumulates in a room you eventually leave, taking it with you, with nothing portable to show for it.

• Recognition now precedes performance. The work has to leave the room it was built in before the room needs to see it.

• The discomfort of publishing, positioning, and naming your framework is not a warning signal. It is the signal that you are in the right quadrant.

Consider and Act

• Where is your best work currently living? Name the room it is in and whether anyone outside that room can see it.

• What is the one framework, idea, or perspective you have built across your career that has never been written down or made public? That is the signal the market cannot yet find.

• Run the Scarcity Filter on your visibility activity this week. How many hours went into doing excellent work that stayed local? How many went into making existing work legible to the selection system?

• Identify one piece of work from the last twelve months that deserved to be seen more widely and was not. What would it take to give it a second life in public?

• The readiness threshold is not a quality standard. If you are waiting until the work is good enough to share, name the specific thing that would make it ready. If you cannot name it, the threshold is moving. Publish anyway.

Twenty years in software engineering gives you a dangerous superpower. You can look at almost any tool, any platform, any SaaS subscription and think: I could build that. And you would be right. Most of the time you actually could.

Right now the default move for anyone with a technical background is to spin up their own version of whatever they are paying for. Custom CRM. Bespoke analytics dashboard. Self-hosted everything. The tools exist. The skills exist. The logic feels sound.

But the logic is wrong.

I have built solutions that ended up incomplete. I have built things that worked but consumed months I did not have. I have built the technically correct answer to the wrong question. And every time, the real cost was not the hours. It was what I was not building while I was building the wrong thing.

That pattern is what gave me the filter.

The question underneath everything

Most professionals sort their work into two buckets. Important and not important. Urgent and not urgent. High value and low value.

These are the wrong splits.

The question that actually determines whether your work builds leverage or consumes it is simpler and sharper than any of those.

Is this work scarce or abundant? And am I the one doing it?

Scarce work is work that requires you specifically. Your judgement. Your voice. Your relationships. Your original thinking. Work that loses something essential if someone else does it, or if a tool generates it.

Abundant work is everything else. Competent, useful, necessary, but available. Anyone sufficiently capable could do it. A tool could do it. Another person could do it. It does not require you to be you.

Those two questions produce four answers. Only one of them builds leverage.

The four quadrants

Scarce work, done by you. Do more.

This is the only quadrant that compounds.

Writing your thinking. Developing your framework. Building relationships that cannot be templated. Making the strategic calls that require your specific judgement and no one else’s.

Every hour here builds something that keeps working after the hour ends. A piece of writing someone returns to. A relationship that routes opportunity toward you. A reputation that walks into rooms before you do.

Most professionals spend less than 20% of their week here. The rest is consumed by the other three quadrants, two of which are traps.

Abundant work, done by a tool or someone else. Buy it.

Scheduling. Formatting. Editing. Transcription. Hosting. Design production. Anything that is useful and necessary but does not require you to be you.

Buy it. Automate it. Delegate it. This quadrant should cost money, not time. Every pound you spend here is buying back hours for quadrant one. That is not a cost. It is an investment in your scarce time.

The SaaS subscription you are considering building yourself lives here. Almost always. The monthly fee is not waste. It is the price of staying in the right quadrant.

Abundant work, done by you. Eliminate or offload.

This is the trap. And it is where most professionals spend the majority of their week.

It feels productive because you are busy. Output is visible. Progress feels real. The competence trap is particularly cruel here because you are often genuinely good at the abundant work. It is comfortable. The system rewards it in the short term.

But every hour spent in this quadrant is stolen from quadrant one. Directly. There is no neutral. Time spent on abundant work done by you is time not spent on scarce work done by you. That is the whole trade.

Building the custom tool instead of subscribing to the existing one. Maintaining infrastructure that a managed service could run. Fiddling with systems because you know how they work and fixing them feels satisfying.

I have done all of it. It is the quadrant that costs the most and announces itself the least.

Scarce work, done by a tool or someone else. Never.

Your voice. Your judgement. Your framework. Your relationships.

These cannot be outsourced without destroying the value. Not because the output would be worse, though it often would be. Because the value of scarce work is inseparable from its origin.

A ghostwritten post in your name is not your thinking made more efficient. It is your thinking replaced. A strategy built by an agency running your positioning is not your strategy with better execution. It is someone else’s strategy wearing your name.

The moment you outsource the irreplaceable, it stops being irreplaceable. And it stops being yours.

This is the quadrant most people think they are protected from. Few of them are.

How to use it

The filter is not a planning tool. It is a decision metric.

When a task arrives, or a tool is pitched, or a project is proposed, run it through two questions before anything else.

Is this work scarce or abundant? Could someone or something else do it without being me?

The intersection tells you what to do. Do more. Buy it. Eliminate. Never.

One verdict. No committee. No extended analysis. The filter is designed to produce a position, not a conversation.

The three checks for when it is ambiguous:

Am I doing the abundant work because I am good at it and it is comfortable? That is the competence trap. Stop.

Am I thinking about this instead of doing the scarce work? Understanding the problem is not the same as solving it. That is the intelligence trap. Decide and move.

Is this building something scarce, or just keeping me busy? Motion is not leverage. Test it honestly.

What changes when you use it

The filter does not tell you to work less. It tells you to work differently.

Most professionals who run their week through it find the same thing. The scarce work they should be protecting is buried under layers of abundant work they are doing themselves. The writing that never gets written. The relationships that never get built. The thinking that stays in their head because the week ran out before it got on the page.

The filter surfaces the trade you are making every week without realising it.

I built it because I kept making the wrong trade. Twenty years of engineering capability pointed at problems that a forty-pound-a-month subscription would have solved. Months of my own time building incomplete tools while the work that actually mattered waited.

The question is not whether you can build it.

The question is whether building it is the most scarce thing you could be doing with that time.

Almost always it is not.

Protect the scarce. Buy the abundant. Never confuse motion for leverage.

Most people feel it but cannot name it.

Think about how a context window works in AI. You are deep in a conversation. Everything is live. Every detail, every decision, every line of reasoning is present and connected. The model knows exactly what is happening and why.

Then the window fills. The compression comes.

All of that depth gets reduced to a summary. The outline is there. The shape of what happened is there. But the texture, the reasoning, the hours of work that built it, gone. Condensed into tokens that gesture at what existed rather than hold it.

I have lived that pattern more times than I can count.

Months inside a software project. The team locked in, pulling in the same direction, building something that had never existed before. Then it ships.

And within weeks the work is already becoming a summary. The detail of what it took, forgotten. The effort compressed into an output that the organisation moves on from. What remains is the system, not the story of how it was built.

That is not a technology problem. That is how organisations process work.

In the last few years of my corporate career I built a suite of greenfield technology applications and infrastructure that had never existed before. Not an iteration. Not an improvement. Something from nothing.

The recognition never came.

What came instead was more work. A push to build on what had been built, to improve on what had never existed, to keep delivering on a baseline that kept moving. I kept going. I told myself that if I delivered enough, for long enough, it would eventually be acknowledged.

It was not.

Looking back, the sharpest part of that experience is not the lack of recognition. It is the feeling of being trapped by my own output. The better I performed, the more indispensable I became to the process. The more indispensable I became, the less the organisation could afford to move me. I had built the walls of my own ceiling.

I only understood what had happened when I started writing the framework. I saw my own story in it immediately.

The belief

Hard work is rewarded. Most professionals carry this assumption into their careers for good reason. In the early years, it is true.

You work harder than the person next to you and you move faster. The feedback loop is clean. Input produces output. Output produces recognition.

Then it stops working. Not immediately. Gradually, then suddenly.

The environment changed. The game changed. But the strategy did not.

What got you here was effort. What gets you to the next level is leverage. Most people keep pulling the effort lever long after it stopped producing returns, because it is the only lever they know.

I pulled it for years.

What actually happened

The environment changed around me without announcing itself.

In the early stages, effort is a genuine differentiator. Most people at that level are not working that hard, not delivering that consistently. Standing out by working harder is a viable strategy because the bar is low enough for effort to clear it.

Then two things happen simultaneously.

Everyone around you starts working harder too. Effort stops being a differentiator because it becomes the baseline. Everyone at this level is reliable. Everyone delivers.

And the organisation stops selecting on effort and starts selecting on something else entirely.

What it selects on is scarcity.

What organisations actually reward

Organisations do not promote the hardest worker. They promote the person they cannot afford to lose from the next level up.

Those are not the same person.

The hardest worker is often the person they cannot afford to move from their current role. The person who holds the institutional knowledge, puts out the fires, keeps the engine running. Indispensable where they are. Impossible to promote without creating a problem.

That was me. I had built something irreplaceable and been rewarded with more work. The organisation needed me exactly where I was. It had no incentive to move me.

The person who gets promoted has built something the organisation needs at a higher level. Not more effort. A different kind of contribution. One that is harder to find, harder to replicate, harder to route around.

That is scarcity. And it has nothing to do with how many hours you logged.

The trap inside the belief

The belief that hard work is always rewarded is not just wrong. It is actively dangerous, because it directs your energy toward the wrong thing.

Every hour spent proving how hard you work is an hour not spent building something that compounds. Every late night fixing a problem that only you can fix makes you more indispensable to a process and less visible as a candidate for the next level.

I kept delivering and hoped recognition would eventually come. It did not. Because I was solving the organisation’s problem, not building my own leverage.

Deserving and receiving are different systems. Effort alone does not bridge them.

What compounds instead

The question that led me to write Scarcity Algorithm was not how do I work harder.

It was: what do I build that keeps working when I stop?

Effort gets compressed. The fires you put out last quarter are forgotten. The late nights are absorbed into the baseline expectation. The reliability that felt like a differentiator becomes the minimum requirement, invisible until it fails.

What survives compression is different. A framework someone else uses. A reputation that precedes you into rooms you have not entered yet. A body of work that signals something the organisation cannot easily find elsewhere.

These things do not require you to stop working. They require you to be deliberate about what the work produces beyond the immediate output.

The reframe

Hard work is not the problem. Hard work in service of abundant output is the problem.

The question is not whether to work hard. It is whether the work you are doing is building something scarce or just maintaining something that anyone sufficiently reliable could maintain.

I spent years maintaining something irreplaceable and being rewarded with more maintenance. The exit was not working less. It was understanding that the framework I was building in my own head was worth more than anything I was building for someone else.

Hard work got me there. It did not get me out.

Understanding the difference did.

Effort loses its memory. Only scarcity survives compression.

They write the code and close the deals. They answer support tickets at midnight and present to investors at nine the next morning. They hire the first people, onboard them personally, and then cover for them when they leave. They are the product, the process, and the safety net, all at once.

This is not a flaw. In the beginning, it is the only way.

The problem is what happens next.

Most founders never stop.

The company grows. The headcount grows. The revenue grows. But the operating pattern does not change. The founder is still the decision point for everything that matters. Still the one who gets called when something breaks. Still the person the team is waiting on before they can move.

The company scaled. The founder did not.

Why it happens

The doing-everything phase works. That is the trap.

It works so well, for so long, that the founder internalises it as the reason for the company’s success. And they are not entirely wrong. In the early stages, founder involvement is the competitive advantage. Speed of decision, clarity of vision, personal relationships with early customers. All of it flows through one person because one person is faster than a system.

But what makes a company fast at ten people makes it slow at fifty. What makes a founder indispensable at seed stage makes them a liability at Series A.

The role that built the company to its first million is the role that caps it there.

Most founders do not see the transition coming. They are too close to it. They are still solving problems, still shipping, still in every room that matters. The company feels like it is moving. It is. But it is moving because of the founder, not because of what the founder built.

That distinction is everything.

The bus test

There is a question investors ask that founders hate.

What happens if you get hit by a bus tomorrow?

Founders hate it because it feels morbid. They hate it more because they do not have a good answer.

The honest answer, for most founder-dependent companies, is: it collapses. Or it stalls badly enough that collapse becomes likely. The customers who bought because of the founder relationship start asking questions. The team that was following the founder’s judgement starts second-guessing its own. The pipeline that was moving because the founder was in the room stops moving.

The bus test is not really about buses. It is about leverage.

A company that passes the bus test has built structures, systems, and people that compound without the founder’s constant intervention. A company that fails it has built a job for the founder, with staff.

Most early-stage companies fail the bus test. That is expected and acceptable.

Most growth-stage companies fail it too. That is a structural problem, and it is the founder’s fault.

What founder dependency costs

The most visible cost is scale. A company that runs through one person can only move as fast as that person. Every bottleneck traces back to the founder. Every decision waits for their input. Every hire needs their approval. Every client relationship runs through their phone.

The company is not scarce. It is abundant, dressed up as a founder’s personality.

The less visible cost is valuation. Investors price key person risk directly. A company where the founder is the product, the relationship, and the operating system is a company with a structural discount built in. The question is never whether the company is good. The question is whether the company is good without this specific person. If the answer is no, the multiple reflects it.

The least visible cost is the founder themselves. Seventy-two percent of founders report experiencing mental health challenges. The pattern underneath most of those numbers is the same. A person who built something they cannot put down. Not because they do not want to. Because they built it around themselves so tightly that stepping back feels like abandonment.

The company became the trap.

The transition most founders miss

There is a specific shift that separates founders who scale from founders who stall.

It is not hiring. Plenty of founder-dependent companies have large teams.

It is not raising money. Capital does not fix a structural dependency. It funds it.

The shift is from solving problems to building systems that solve problems.

The founder who solves a problem has solved it once. The founder who builds a system has solved it permanently, and freed themselves to work on the next level of problem.

Delegating tasks keeps the founder in the loop. Delegating outcomes removes them from the process entirely. The first feels like control. The second builds leverage.

The scarce founder is not the one who knows everything and does everything. It is the one who has built a company that knows enough and does enough without them in the room.

That company is hard to replace. Hard to route around. Hard to ignore.

The founder who built it is scarce because of what they created, not because of what they are doing right now.

The question to ask this week

If you disappeared for ninety days tomorrow, what would break?

Not what would be harder. What would actually break. What decisions would not get made. What relationships would go cold. What processes would stall because no one else knows how they work.

Write it down. That list is not a testament to how valuable you are.

It is a map of where you have not yet built leverage.

Every item on that list is work the founder needs to stop doing personally and start building into the structure of the company.

That is the job. Not the product. Not the sales. Not the hiring.

Building the thing that runs without you. That is founder leverage.

The line underneath it

The reliability trap keeps individuals in place.

The hoarding trap keeps leaders small.

The founder trap keeps companies dependent.

All three are the same mistake at different scales. Optimising for what is needed now at the cost of what compounds later.

The individual builds leverage by creating what cannot be substituted.

The leader builds leverage by developing what cannot be replaced.

The founder builds leverage by building what cannot be stopped.

Effort loses its memory. Structure doesn’t.

It should not be. But it is.

The leader reads it and runs the same script every time. They did not see it coming. The person seemed happy. There were no signs. The team is going to feel this. The timing is terrible.

None of that is the real problem.

The real problem is what the leader does next. They counter-offer. They appeal to loyalty. They remind the person what they have here, what they are walking away from, how much potential they have in this organisation.

What they do not do is ask the one question that matters.

Why did it take a resignation letter for this conversation to happen?

What talent hoarding looks like

Most leaders do not think of themselves as talent hoarders. The term implies malice. It is rarely malicious.

It is structural.

The best person on the team is the best person on the team. Moving them creates a gap. Promoting them creates a problem. Letting them go to another team feels like losing. So the leader keeps them in place. Not through cruelty. Through need.

The work requires them. The team depends on them. The leader cannot absorb the disruption of losing them right now.

Right now becomes next quarter. Next quarter becomes next year. The best person on the team stops being a person with potential and starts being a fixture. A load-bearing wall. Something the structure cannot afford to lose.

And then they hand in their notice.

The economics of hoarding

Here is what the research says.

A study of 96,712 internal applications across a Fortune 50 company over four years found that managers who blocked internal mobility received significantly fewer and lower quality applications when they had open roles. The reputation persisted even when those managers changed teams.

The leader who hoards talent does not keep talent. They repel it.

The best candidates in any organisation know which managers develop people and which ones keep them in place. They route toward the developers. They route around the hoarders. Not loudly. Quietly. Through the decisions they make about where to apply, where to transfer, where to invest their energy.

The hoarding leader ends up with the people who had nowhere else to go.

Why the system rewards it anyway

The incentive structure in most organisations is built for retention, not development.

Headcount is a resource. Losing headcount is a problem. A manager who loses their best person to another team is solving someone else’s problem at their own expense. The system does not reward that. It punishes it.

So the rational move, inside most organisational incentive structures, is to keep people in place. Block the transfer. Delay the promotion. Make the person feel valued without actually advancing them.

The system is designed to produce hoarding. Most leaders are just following the logic of the environment they are in.

The problem is that the environment is wrong. And the leaders who figure that out first are the ones who win.

The scarcity inversion

The leader who develops people and lets them go creates something the leader who hoards never does.

A reputation.

Each person who gets promoted, transferred, or advanced becomes a signal. Not just to the organisation. To the market. To the talent pool that is always watching, always routing toward the leaders worth working for.

The MIT Sloan research is unambiguous on this. Managers with higher promotion rates attracted more internal applications, better candidates, and more functionally diverse talent. That reputation persisted when they changed jobs. They brought it with them.

The leader who lets leverage walk out the door does not lose leverage. They compound it.

Every person they develop becomes a node in a network that routes opportunity back toward them. Former direct reports make introductions. They recommend. They send the best candidates they know. They become distributed intelligence working in the leader’s favour.

The hoarder builds a team. The developer builds a reputation. A reputation outlasts any team.

The question worth asking

If your best person handed in their notice today, what would the conversation reveal?

Would it surface ambitions you already knew about and did nothing with? Would it show a ceiling you kept in place because removing it was inconvenient? Would the counter-offer you reach for be the conversation you should have had six months ago?

The resignation letter is not the problem. It is the invoice.

The bill for every conversation that did not happen. Every promotion that was delayed. Every transfer that was blocked because the timing was not right.

Scarcity-positive leaders do not wait for the invoice. They have the conversation before it becomes a resignation. They ask where the person wants to go, and then they help them get there. Even when it costs them something. Especially when it costs them something.

Because the leader who builds leverage in others is building the most durable leverage there is.

The line underneath it

The reliability trap keeps individuals in place.

The hoarding trap keeps leaders small.

Both are versions of the same mistake: optimising for what you need right now at the cost of what compounds over time.

Effort loses its memory. So does hoarding.

What lasts is what you built in other people.

They become reliable.

They show up. They deliver. They say yes when others say no. They solve the problem no one else can solve. They become the person the team cannot function without.

And then they wonder why nothing changes.

Not the title. Not the salary. Not the scope. Not the recognition. Everything stays exactly where it was, except the dependency. That grows. Every quarter, a little heavier.

This is the reliability trap. And it is the most common ceiling in professional life.

How it works

Reliability feels like leverage. It is not.

Leverage is what works when you stop. Reliability is what breaks when you leave.

The distinction matters because organisations do not reward people for being needed. They reward people for being scarce. Those are not the same thing.

Being needed means the system depends on you. Being scarce means the system cannot replace you. One keeps you in place. The other moves you forward.

The reliable person is indispensable to a process. The scarce person is irreplaceable in a category.

The organisation does not promote the person the team cannot function without. It keeps them exactly where they are. Because moving them creates a problem. And organisations avoid problems.

You built the trap. You are sitting in it. And every day you perform reliably, you make the walls a little thicker.

Where it comes from

The reliability trap is not a character flaw. It is a rational response to an environment that rewarded effort early in your career.

In the first few years, effort works. You work harder than the person next to you and you move faster. The feedback loop is clean. Input produces output. Output produces recognition.

Then it stops working. Not immediately. Gradually, then suddenly.

The environment changed. The game changed. But the strategy did not.

What got you here was effort. What gets you to the next level is leverage. Most people keep pulling the effort lever long after it stopped producing returns, because it is the only lever they know.

The signal you are in it

You are the person called when something breaks. You are the one who stays late to fix what others could not. You are the institutional memory, the problem-solver, the one who knows where everything is buried.

People appreciate you. They depend on you. They would be lost without you.

And when the promotion conversation happens, someone else gets it. Someone who was not in the room as often. Someone who broke fewer fires. Someone who, if you are honest, delivered less.

That is not unfair. It is a signal.

The person who got promoted was not more reliable. They were scarcer. Their contribution was harder to categorise, harder to replace, harder to route around. The organisation did not know what it would do without them. Not because they were needed, but because they were irreplaceable in a way that had no obvious substitute.

Reliability has a substitute. It is called hiring someone else who is reliable. There are many of them.

The exit

Getting out of the reliability trap is not about working less. It is about working differently.

The question to ask is not “what can I do that no one else is doing?” It is “what can I build that keeps working when I stop?”

Reliable people solve problems. Scarce people build things that solve problems.

The transition is not comfortable. The system will resist it. The team still needs the fires put out. The manager still needs the gap filled. The organisation will keep pulling you toward the work it knows you can do.

The trap is maintained by the people who benefit from it. Not through malice. Through inertia.

The only way out is to start building something scarce while the reliable work still gets done. Not instead of it. Alongside it. Until the scarce thing is visible enough that the reliable work becomes a negotiation, not a default.

The line underneath it

Effort loses its memory.

No one remembers the fires you put out last quarter. They remember what you built that is still standing.

Reliability is abundant. Everyone is trying to be dependable.

Build something that cannot be substituted. That is the exit.

Why Value Flows to the Scarce

There is one principle underneath every career plateau, every leadership failure, and every founder who hits a ceiling they cannot see.

Value flows to what is scarce.

It drains from what is abundant.

That is not a motivational claim. It is an economic one. And once you see it, you cannot unsee it.

The pattern shows up everywhere

The individual who works harder than anyone in the room and still gets passed over. Not because effort is worthless. Because effort is abundant. Everyone is working hard. Hard work stopped being a differentiator the moment everyone started doing it.

The leader who builds a team of exceptional people and then wonders why the exceptional people leave. Not because the culture is broken. Because the system rewards hoarding talent, not developing it. Hoarding is abundant. Development is scarce.

The founder who cannot take a holiday without the company stalling. Not because the company is too small. Because the company is too dependent. On one person. On the founder. That dependency is the ceiling.

Three levels. One mechanism.

What scarcity economics says

Classical economics tells you value is determined by supply and demand.

Scarcity economics is more specific. In a world where effort, competence, and execution are commoditised, the only thing that commands a premium is what cannot be easily replaced, copied, or routed around.

That applies to you as an individual. It applies to how you lead. It applies to what you build.

The question is never “am I working hard enough?”

The question is: “am I building something scarce?”

What this platform is

This is not a newsletter about productivity.

It is not about working smarter, building habits, or optimising your morning routine.

Scarcity Economics is a framework applied at three levels, in sequence.

The individual. How to stop accumulating effort and start building leverage. Why what scales is not what you do, but what you build that keeps working when you stop. This is the territory of soon to be publish Scarcity Algorithm.

The leader. How to build leverage in others when the system punishes you for it. Why the leaders who win are not those who accumulate scarce people, but those who create them. This is the territory of Scarce Leaders.

The founder. How to build a company that does not depend on you. Why hustle is the abundant activity, and what founders who scale actually do differently. This is the territory of Scarce Founders.

One framework. Three levels. A complete arc.

What you will get here

Each issue applies the framework to something real. A decision, a pattern, a trap, a case study. Sometimes from consulting work. Sometimes from the books. Always from the framework.

No filler. No motivational content. No advice that could apply to anyone.

If you are an individual who suspects effort alone will not save you, this is for you.

If you are a leader who feels the tension between developing people and losing them, this is for you.

If you are a founder who cannot step back without something breaking, this is for you.

The mechanism is the same at every level.

Effort loses its memory. Leverage doesn’t.

Welcome to Scarcity Economics.