Organizations generally have two kinds of service arrangements, often without being explicitly modeling or accounting for them in a disciplined way.

Salaried staff are, in theory, available up to 40 hours per week. They show up. They're on the payroll. Their time is, at least in principle, fully committed to the organization.

Pay-per-use contributors — contractors, consultants, freelancers — bill for what they deliver. There's a clean transactional clarity: you need something, you pay for it, it gets done.

Both models have their place. Neither is universally superior. But there's a tension between them that rarely gets named directly — and naming it might be the most useful thing we can do.

---

The Latent Capacity Hypothesis

Here's the theory: a significant portion of salaried staff time is unused, underutilized, or mis-aimed.

This isn't a moral failing. It's almost inevitable given how organizations work. Salaried roles are structured around availability, not throughput. You hire someone to be present, to be ready, to hold institutional knowledge. But that same structure creates pockets of slack — time that isn't actively generating value, even when the person is technically "at work."

In knowledge work, this latency is largely invisible. Unlike a factory floor, you can't look across an open floor plan and count the idle machines. Instead, you count meetings, emails, Slack messages, GitHub commits — proxies, not the thing itself.

The result: organizations may be sitting on enormous amounts of untapped capacity without realizing it. Smart, capable, well-compensated people who could be doing more, learning more, or solving harder problems — but who are caught in the amber of routine, unclear priorities, or misaligned incentives.

---

The Incentive Crosscut

This is where it gets interesting, and a little uncomfortable.

For individual salaried employees, there is often a rational incentive to not fully advertise your available capacity. If you complete your work quickly and efficiently, you may simply receive more work — without additional compensation, recognition, or career progression. The reward for efficiency, in many orgs, is more work at the same rate.

For managers, there's a different version of the same problem. Underutilized staff can feel like a liability — a justification for headcount reductions. The incentive is to appear busy and fully deployed, even when the underlying work doesn't demand it.

For organizations as a whole, there's a belief — often correct — that slack capacity provides resilience. The team that's at 70% utilization can absorb a crisis. The team at 110% cannot. But "resilience buffer" and "hidden waste" can look identical on a spreadsheet.

Pay-per-use contributors don't have this problem in the same way. Their incentive is to deliver the specific thing they were hired to deliver, efficiently, so they can move on. There's no fog around their contribution.

These incentive structures don't just coexist — they actively conflict. Salaried staff may feel threatened by contractors who get things done faster. Contractors may be frustrated by the organizational drag that slows their work. Each group can, understandably, see the other as the problem.

---

What Can Productively Be Done?

A few threads worth pulling.

1. Make capacity visible — gently

The goal isn't surveillance or performance management theater. It's creating a shared, honest picture of where capacity actually lives. Simple questions: What are you working on? What's blocked? What would you take on if you had more runway?

Teams that have regular, low-stakes conversations about workload tend to self-organize toward better utilization. The visibility creates the conditions for redistribution.

2. Separate "available" from "deployed"

Organizations benefit from naming the difference between a staff member's availability (they're on payroll, they're present) and their deployment (they're actively working on something high-value). Most orgs treat these as synonymous. They're not.

When you separate them, you can have an honest conversation: "We have 20% deployed capacity sitting idle in this department. What's the most valuable thing we could aim it at?"

3. Redesign the reward structure

If the incentive for doing good work fast is just more work with no upside, people will pace themselves. That's rational. The fix isn't punishing pacing — it's creating genuine rewards for high-output periods: learning time, project choice, public recognition, real career advancement.

Organizations that have made this shift often discover a latent store of enthusiasm they didn't know they had.

4. Let salaried staff do contractor-style work internally

This sounds obvious, but it's underused. Salaried staff who have genuine slack can be offered the chance to take on specific, scoped projects — almost as internal contractors — with clear deliverables and visible recognition. It gives them the satisfaction of a complete, visible contribution. It gives the org a way to deploy latent capacity purposefully.

5. Build psychological safety around capacity conversations

The biggest barrier to any of this is fear. Fear that admitting you have capacity means admitting you've been underperforming. Fear that your manager will see the slack as a threat. Fear that others will judge you for not being busy enough.

None of these conversations go well in low-trust environments. The prerequisite to unlocking latent capacity is creating the conditions where people feel safe enough to say, "I have bandwidth — what needs doing?"

---

In Good Spirit

The framing here matters. This isn't about squeezing more out of people who are already stretched. Most of the latent capacity we're describing is in people who want to do more, who feel the friction of being underdeployed, who joined an organization because they believed in its mission and now find themselves in a slower orbit than they hoped for.

The opportunity is to meet that energy — not to extract it, but to channel it. To build organizations that feel alive to the people inside them, where capacity flows toward purpose rather than pooling in the dark.

Pay-per-use will always have its place. But the case for salaried staff is, at its best, a case for commitment — the idea that people who are fully invested in an organization over time create something a transactional model cannot. The shame would be to have that commitment and leave it sitting on the shelf.

---

Written in the spirit of honest organizational reflection. Feedback welcome.