Why Ownership Without Compensation Eventually Breaks, and Why Autonomy Is the Real Currency of Growth

The hidden deal behind every system

What if the biggest problem in many organizations is not lack of talent, but a broken exchange rate?

A person is asked to carry real responsibility, make consequential decisions, keep critical systems alive, absorb urgency, and remain available when things break. In return, they often receive something vague: appreciation, visibility, maybe a future opportunity. That trade can feel acceptable for a while, especially when the work is exciting or the mission feels noble. But eventually the math changes. The effort becomes routine, the stakes rise, and the invisible cost starts compounding.

This is true in open source software, where maintainers are expected to support infrastructure that others depend on professionally, often without meaningful compensation. It is also true inside companies, where a high performer can become the person everyone calls because they are reliable, and then slowly become trapped by the very reliability that made them valuable. In both cases, the same pattern appears: responsibility expands faster than reward, and autonomy shrinks faster than trust grows.

The deeper question is not, “Why are people leaving?” It is, “What kind of system asks for ownership while denying the conditions that make ownership sustainable?”

---

When responsibility becomes a tax

There is a subtle difference between being trusted and being overused. Trust gives someone room to act. Overuse simply hands them the bill.

In open source, the bill arrives as unpaid support, bug triage, maintenance, design debates, release pressure, and emotional labor for users who treat the project like a utility rather than a volunteer effort. In a company, the bill arrives as endless context switching, crisis ownership, and the expectation that the same person will always know the answer. At first, this can look like prestige. Eventually, it feels like unpaid insurance against other people’s uncertainty.

The problem is not just fairness, although fairness matters. The deeper issue is sustainability. Any system that depends on a small number of people doing high-value, low-recognition work is fragile. It is like running a city on one power station and calling the outage a surprise when the station fails.

A useful mental model here is to think about ownership debt. Just as technical debt accumulates when shortcuts today create larger costs tomorrow, ownership debt accumulates when a person is repeatedly assigned responsibility without a matching increase in authority, compensation, or scope. The debt is invisible at first because the person keeps delivering. Then one day the system discovers that the delivery was held together by exhaustion, not design.

Responsibility without compensation is not a motivating strategy. It is a borrowing strategy.

That borrowing can work briefly because conscientious people often keep paying the interest. But interest compounds. People begin to protect their time, reduce their enthusiasm, and stop volunteering the extra effort that made them exceptional. What looked like loyalty was often just the last stretch of unsustainable commitment.

---

The real promotion is not more pressure, it is more leverage

Career growth is often described as moving upward: more scope, more people, more decisions, more visibility. But that framing misses a crucial distinction. Not all expansion is growth. Sometimes expansion is just more surface area for stress.

The transition from engineer to leader can become a trap if it is built on dependency rather than leverage. If the team relies on one person to make every decision, approve every change, and provide constant support, that person may appear indispensable. In reality, they are creating a bottleneck. Their calendar becomes the system architecture. Every road leads through them, which feels important until the throughput collapses.

The irony is that many people get promoted precisely because they solve too much. They become the person who knows the product, the codebase, the numbers, or the politics. One vivid example is maintaining a product that tells the company how much money it makes each day, week, and month. That kind of visibility naturally leads to trust. It also creates a powerful lesson: if you own the numbers, you begin to own the organization’s confidence.

But confidence is not the same as autonomy. A person can be trusted to execute and still not be trusted to shape the system around them. This is where many ambitious professionals stall. They become excellent at being relied upon, but not excellent at creating environments where others can act without them.

That is why autonomy is not a perk, it is the architecture of growth. If your role gives you more work but not more decision-making power, you are not ascending. You are just being loaded.

The shift from engineer to VP is less about knowing more and more about redesigning the conditions of work. The highest-leverage leaders do not answer every question. They create teams that can answer more questions without them.

---

The autonomy paradox: the more you give, the more you scale

At first glance, autonomy seems like a risk. If people are left alone, they might make mistakes. Standards may drift. Quality may wobble. That fear drives many managers and maintainers to centralize decisions, review every change, and stay involved in everything that matters.

But the paradox is that overcontrol produces the very fragility it is meant to prevent. When every meaningful choice depends on one person, the system becomes slower, less intelligent, and less resilient. People stop learning because learning is unnecessary when someone else always decides. They become compliant instead of capable.

The same dynamic shows up in open source when maintainers become gatekeepers for every issue, pull request, and roadmap discussion. The project may preserve consistency for a while, but it also loses velocity and burns out the people holding the center together. A project cannot scale forever on heroics. A team cannot scale forever on a single trusted adult.

This is where the connection between compensation and autonomy becomes especially important. Compensation is not just money. It is a signal that the system recognizes value and wants the relationship to continue. Autonomy is not just freedom. It is a signal that the system trusts the person to shape outcomes. When compensation is absent and autonomy is constrained, the message becomes impossible to ignore: the system wants your labor, but not your growth.

Think of a musician in a band. If they are paid, they can justify rehearsal, travel, and repetition. If they are not paid, but still expected to arrange every set list, carry equipment, and show up for every sound check, the arrangement cannot last. Now imagine the musician is also forbidden from choosing the songs. That is not a creative partnership. It is extraction.

The same logic applies to technical leadership. Ownership must be paired with the power to redesign the work. Otherwise, ownership becomes a form of captivity.

---

Why good people stay too long

One of the most dangerous features of these systems is that they often reward the right personality types. Reliable people, conscientious people, mission-driven people, and ambitious people are the ones most likely to accept expanding responsibility. They do not want to let others down. They derive identity from being useful. They are willing to endure awkward imbalance because they assume it is temporary.

That assumption is usually wrong.

People stay too long in broken arrangements for three reasons.

First, identity: they have become the person who “keeps things running.” Leaving would feel like abandoning a duty, not making a career move.

Second, optionality: the current role appears safer than the uncertainty of change, even if the long-term trajectory is worse.

Third, future bargaining: they believe the system will eventually recognize their value and fix the imbalance. Sometimes it does. Often it simply normalizes it.

This is why complacency is the enemy of progress. Not just because it slows ambition, but because it disguises stagnation as stability. A role that once stretched you can quietly become a holding pattern. You are still busy, still needed, still respected, yet no longer developing the muscles required for the next level.

Here is the uncomfortable truth: being indispensable can be a career ceiling. If a company cannot function without you doing the same narrow set of tasks, it will hesitate to move you. If an open source project cannot function without one maintainer reviewing everything, that maintainer may be praised but also trapped. In both cases, competence becomes a cage when the system fails to distribute capability.

The goal is not to be the only one who can do the job. The goal is to build a system that does not collapse when you stop doing it.

That is a far more mature definition of success. It turns the question from “How much can I personally handle?” into “How much capacity can I create around me?”

---

A better framework: value, authority, and replenishment

If the old model is broken, what should replace it?

A useful framework is to evaluate any role, project, or collaboration through three lenses: value, authority, and replenishment.

1. Value: Are you creating something materially important, whether to a company, community, or product?
2. Authority: Do you have enough power to shape how that value is created, including decisions, priorities, and process?
3. Replenishment: Are you receiving enough compensation, recognition, learning, rest, or freedom to keep contributing sustainably?

If value is high but authority and replenishment are low, the arrangement is extractive. If authority is high but value is low, the arrangement is often political or ornamental. If replenishment is high but value is low, the arrangement may be comfortable but not meaningful.

The healthiest roles align all three.

This framework also explains why transitions matter so much. A promotion should not simply increase the amount of output expected from you. It should increase your ability to shape output, distribute responsibility, and improve the system. Likewise, sustaining an open source project requires more than gratitude. It often requires sponsorship, shared maintainership, documentation, governance, and lower-friction pathways for contribution.

In other words, the answer is not merely “pay people more,” though paying people more is often necessary. The answer is to stop pretending that labor, leadership, and stewardship are free. Every serious system has a maintenance cost. If you do not pay that cost explicitly, you will pay it later through burnout, churn, or stagnation.

---

Key Takeaways

• Audit your responsibilities: List the work you own, then ask whether each item comes with matching authority and compensation.
• Watch for bottlenecks: If every decision runs through you, your role may be limiting the system more than strengthening it.
• Build replacement, not dependency: Document processes, mentor others, and delegate real decisions, not just tasks.
• Treat autonomy as a signal: More trust should come with more influence over priorities, process, and outcomes.
• Leave or renegotiate when the math is broken: If your contribution keeps rising while recognition, compensation, and decision power do not, the arrangement is becoming unsustainable.

---

The real measure of maturity

We usually think of career growth as climbing toward more status, more money, or more authority. But there is a deeper measure of maturity: whether you can create systems that do not depend on your constant sacrifice.

That is the bridge between open source and leadership. In both worlds, the temptation is to celebrate the person who keeps everything alive, whether by volunteering endless support or by heroically solving every team problem. Yet heroism is a brittle operating model. It works until it does not.

The most durable leaders and maintainers are not the ones who carry the most alone. They are the ones who convert personal effort into shared capability. They know that compensation is not just a transaction and autonomy is not just a benefit. Together, they are the terms under which human effort can remain generative instead of draining.

So the next time a role asks you for more ownership, ask a better question than “Can I do it?” Ask:

Does this arrangement help me grow, or is it simply making me more available to a system that has not learned how to stand on its own?

That question changes everything, because it reveals the real choice. Not between comfort and challenge, but between being used to maintain a system and becoming powerful enough to redesign one.