Yet as we talked, he framed the subtle trade-off better than anyone I’ve heard. Not backfilling saves payroll. But if that person had learned to use these new tools, losing them means you have permanently lost their capacity to scale that part of the business.
His observation cuts straight to a strategic choice leadership faces when deploying modern technology: Are you optimizing for immediate margin, or are you building long-term leverage?
When modern tools and automation strip operational friction out of daily workflows, capacity is unlocked. Tasks that previously required 40 hours of fragmented coordination shrink to 10.
In that moment, leadership arrives at a fork in the road:
[ Friction Automated ]
│
┌────────────────┴────────────────┐
▼ ▼
[ Path A: Harvest Savings ] [ Path B: Reinvest Capacity ]
• Direct margin expansion • Tackle pent-up demand
• Extended runway • Build high-leverage scale
• Lower fixed overhead • Capture new market opportunities
Allow headcount to shrink through attrition or targeted reductions, choosing not to backfill roles whose primary utility was managing low-leverage output.
Redirect freed employee bandwidth toward a backlog of high-value ideas, strategic bets, and market opportunities that were previously blocked by operational drag.
Both choices are strategic. If a company is capital-constrained, extending runway, operating in a mature market, or hasn’t spent time developing strategic bets, Path A might be the only option.
If a company is pursuing market expansion or sitting on a backlog of high-value initiatives, Path B offers a route to scale.
Taking Path A is (typically) a permanent choice in relation to the affected individual. They rarely return when circumstances change. It is important to consider the opportunity cost of separating.
The fundamental difference between Path A and Path B isn’t just immediate payroll: it’s the cost of reversing your decision later.
When an existing operator transitions into high-leverage work (Path B), you are upgrading a worker who already possesses deep domain knowledge, company trust, and institutional context. The cost to transition them is simply the time and space required to learn new tools and shift their mindset.
If you choose Path A and dissolve that role, you capture immediate payroll savings. But if the business accelerates six or twelve months later and you decide you need that capacity back to pursue growth, the cost to re-enter Path B skyrockets.
TRANSITIONING AN EXISTING OPERATOR
[ Existing Salary ] + [ Ramp Time on New Tools ]
= Fast, Low-Cost High-Leverage Capacity
REPLACING CAPACITY LATER
[ Recruiting Fees ] + [ Higher Base Salary ] + [ 6-12 Months Ramp on Domain Context ]
= High-Cost, Delayed Capacity
To buy back that capacity down the line, you face:
Reinvesting capacity preserves the organization’s absorptive capacity: the team’s collective bandwidth to take on new, high-value work without having to hire new talent down the road.
Path A delivers immediate, linear savings today. But if your long-term strategy requires growth, dissolving experienced roles creates a high financial barrier to capturing market opportunities tomorrow.
In almost every organization, there are high-performing operators carrying deep context alongside a heavy volume of manual work. They manage vendor back-and-forth, assemble routine reports, and put out operational fires.
When manual tasks are streamlined behind them, leadership will likely ask: Do we need someone to do these manual tasks anymore?
The answer to that question is almost always no.
TASK EVALUATION
┌─────────────────────────┐
│ Low-Leverage Manual │ ──► Automated ──► Role no longer needed
│ Tasks & Coordination │
└─────────────────────────┘
CAPACITY EVALUATION
┌─────────────────────────┐
│ Deep Domain Knowledge │ ──► Supported via ──► High-Leverage Growth
│ + Operational Context │ Modern Tools Engine
└─────────────────────────┘
A secondary question to evaluate alongside it is: Does this domain represent an opportunity to absorb higher-value demand using new tools?
The manual tasks may no longer be necessary, but an operator with deep domain context who is given the tools to build higher-leverage systems becomes the ideal candidate to execute on the company’s backlogged growth initiatives.
If leadership chooses Path B, reinvesting capacity into growth, management structures often need to evolve to support that objective.
Performance is often measured by visible effort: hours logged, manual throughput, or team size. When efficiency tools enter that culture, management may default to Path A because reducing headcount is a clear metric.
To capture the benefits of Path B, leadership can realign incentives around leverage and outcomes:
When managers know that creating efficiency unlocks resources for higher-value projects, they are empowered to turn their teams into internal systems-builders.
As operational friction continues to drop across every industry, the core question for leadership isn’t whether automation will change your workflows. It is how you choose to allocate the capacity that gets unlocked:
Both options are valid strategic paths. Evaluating them intentionally ensures that your headcount and capacity decisions directly serve your broader business goals.
This is a field note from the Urnicus practice. For more writing, visit the field notes.
]]>Within a few weeks, we had broken his workflows down. We automated many of them. We determined others could be deprecated because they weren’t mission-critical. The emotional burden of losing a good teammate was still raw, but the operational burden his departure created was largely mitigated.
That is when the fear started. His teammates had been worried about how the work would get done without him. Then they watched it get done without him, and they learned the business did not intend to replace him. If the company could absorb the loss of a high-production contributor, what did that say about everyone else?
One senior employee pulled me aside. He admitted he was scared. He didn’t know how to navigate this changing landscape, he didn’t know where to start, and he felt too overwhelmed to find the time to figure it out on his own. He asked me directly: “Am I next?” That’s a reasonable question in a news environment dominated by headlines about AI replacing humans.
His problem wasn’t a lack of intelligence, creativity, or willingness. He recognized the benefits of the new economy and the risks of not becoming a part of it. He had no idea where to start.
To understand why this transition is scary for many employees, look at how value has traditionally been measured inside organizations.
For years, employees have been rewarded for effort and execution. They are “patted on the head” for spending eight hours wrestling with a complex spreadsheet, coordinating across departments, or manually processing files. The effort itself was the proof of value. They receive a “good job ol’ chap” and a paycheck.
THE TRADITIONAL VALUE LOOP
[ 8 Hours of Effort ] ──► [ Manual Output ] ──► [ Reward ]
When new tools compress that eight-hour job into one hour, there is visible amazement. And then there is visible fear.
If the thing you are rewarded for doing suddenly takes no time at all, it feels like your worth to the company has vanished overnight. People aren’t afraid of technology. Their identity as a valuable contributor comes under threat.
THE DISRUPTED VALUE LOOP
[ 1 Hour of Output ] ──► [ "What am I getting paid for now?" ] ──► [ Fear ]
The transition out of this fear isn’t about teaching people how to code or forcing them to become tech experts. It is about helping them shift from low-leverage execution to high-leverage building.
Thirty years ago, nobody was born knowing how to use Excel, Lotus 1-2-3, or Microsoft Word. Secretaries, accountants, and office managers had to learn those tools from scratch. The ones who did didn’t replace themselves; they multiplied their output and became central to how the business operated.
The exact same paradigm shift is happening today with a new set of accessible tools.
Low-Leverage Execution High-Leverage Agency
(Doing the task manually) (Building the workflow)
┌─────────────────────────┐ ┌─────────────────────────┐
│ • Rewarded for effort │ ───────► │ • Rewarded for outcomes │
│ • Time-constrained │ Mental │ • Unlocked capacity │
│ • High risk of burnout │ Shift │ • Direct business impact│
└─────────────────────────┘ └─────────────────────────┘
I’ve written software for a long time. One of the most fun experiences is when you show someone a piece of software that solves a problem for them. It’s like showing a magic trick to a kid. I never get tired of those unveilings.
Now, many of my unveilings breed anxiety. There is a fear that I am there to take their job. While I often have specific deliverables to execute on, the most valuable output I deliver is the investment I make in existing employees, helping them make the mental shift into high-leverage work. This is my high-leverage contribution.
When you help an employee find that first practical foothold, showing them how to use modern tools to solve a problem they face every day, an “aha” moment occurs.
They realize these tools aren’t there to replace them. They are there to give them agency.
I spent time with the senior employee who asked me “Am I next?”, and we built his first tool together. It pulled the full history on a customer service issue in seconds. That had been costing him an hour of research every time it came up.
When that senior employee and his teammates saw that we were investing in them, the entire dynamic in the office shifted. By showing them how to bridge the gap between their daily friction and these new capabilities, fear turned into trust. They realized the goal was not to eliminate their roles, but to release them from low-value grind so they could do work that actually mattered.
This shift transforms how leadership views the workforce as well:
Before the shift: An employee trapped in low-leverage work looks like a cost center running manual loops. When they leave, the company has an opportunity to lock in savings.
After the shift: An employee who learns to use modern tools to absorb demand becomes a growth engine. The company no longer looks for ways to cut them; it looks for ways to invest in them because their capacity to drive outcomes has multiplied.
The employee who burned out under the weight of manual work never got the chance to make this shift. Had he been a part of our exercise to acquire these high-leverage skills, I have no doubt his impact on the company would have expanded dramatically. His former boss agreed and lamented the opportunity cost.
For modern employees, my message is straightforward: this is an acquirable skill.
You do not need to wait for a top-down corporate initiative to start. The shift begins the moment you look at a repetitive task and ask: “How do I move from doing this manually to building a tool that handles it for me?” That mental transition is where your value explodes in the new economy. It turns technological change from something that happens to you into a tool that works for you.
This is a field note from the Urnicus practice. For more writing, visit the field notes.
]]>That reactive approach misses a rare operational window.
Roles quietly drift over time. Responsibilities shift, undocumented workarounds accumulate, and critical knowledge concentrates into single points of failure, because in almost every business, work flows toward competence.
An unexpected resignation forces an immediate audit of a role that you likely haven’t examined closely in months or years. If handled with structured execution, an unexpected exit becomes a rare lever to audit workflows, eliminate operational debt, and permanently upgrade your infrastructure.
Traditional offboarding fails because it asks departing employees to spend their final days writing prose documentation: a tedious task that usually produces vague, unusable documents.
Instead, compress active knowledge retention into a 2-week timeline, anchored by an intensive 5-day capture sprint in Week One. Front-loading the effort ensures capture is finished while momentum is high, reserving Week Two for testing, gap identification, and clean handoffs.
WEEK 1: Intensive 5-Day Capture Sprint
├── Stop routine output; focus 100% on knowledge capture
├── Record narrated screen walkthroughs of daily/weekly logic
└── Conduct daily async reviews to flag gaps and edge cases
WEEK 2: Testing, Refinement & Final Handoff
├── Test documentation through peer execution
├── Structure knowledge assets for ongoing operational use
└── Finalize staffing evaluation and corrected job specifications
Executing a structured resignation response yields six concrete assets that convert temporary instability into long-term operational resilience:
Instead of asking leavers to write manuals, record screen-share walkthroughs of their exact daily, weekly, and monthly workflows. Capturing narrated walkthroughs extracts the decision logic, vendor nuances, and edge cases that standard SOPs miss.
Static PDF documentation quickly becomes obsolete. By structuring captured video transcripts and procedural logic into clean, AI-queryable text formats, remaining staff can query tools like ChatGPT or Claude for instant procedural answers without interrupting management.
Do not default to a 1:1 backfill. Evaluate the real-world captured workload objectively to determine whether leadership should backfill the exact seat, split specialized duties across existing roles, or absorb non-critical tasks permanently.
Legacy job descriptions rarely match real-world execution. Updating the role specification against actual captured logic gives leadership an accurate, battle-tested asset to hand directly to a recruiter.
Turn captured workflows and narrated walkthroughs into a structured onboarding guide. This provides a clear, step-by-step ramp for the eventual replacement hire, radically shortening their time to full competency.
An objective assessment of why the departure occurred and where internal operational friction exists. This provides grounded food for thought for leadership without resorting to subjective HR fluff or prescriptive demands.
The biggest obstacle to proper offboarding isn’t intent; it’s executive bandwidth. Founders and CEOs running daily operations rarely have time to sit in recording sessions or synthesize raw transcripts into structured guides.
Executing this process requires zero new “homework” for leadership. By simply sharing existing role context (such as old JDs or organizational charts) during a 1-hour kickoff, the heavy administrative synthesis and QA can run entirely in the background. Executive oversight is restricted to high-leverage decision points: 10-minute daily async updates and a 1-hour final review.
A resignation is always an interruption, but it does not have to be a setback. By treating the notice period as a structured capture sprint, you protect your remaining team, eliminate knowledge silos, and build an operationally resilient organization that is stronger after the exit than it was before.
]]>The exit interview is largely an exercise in corporate theater.
Departing employees almost never offer unvarnished truth during offboarding. They want to protect professional relationships, avoid last-minute friction, and secure clean references. The result is low-friction boilerplate: “It’s not you, it’s me,” “I found an opportunity I couldn’t pass up,” or “I just need a new challenge.”
If you rely on the exit interview to diagnose your organization, you will operate on false signals. More critically, focusing exclusively on the person leaving ignores the real vulnerability: the team staying behind.
Humans are social animals. In an organizational setting, a key resignation acts as a loud, immediate signal to the rest of the group. It destabilizes the floor and instantly triggers three unspoken questions across your team:
If leadership stays quiet or relies on generic announcements, employees fill the silence with speculative anxiety. Unmanaged operational drift turns into turnover contagion.
To stabilize team sentiment, shift your primary communication focus from the leaver to their immediate peers. Schedule structured, individual 1:1s with remaining team members within 24 to 48 hours of the announcement.
These conversations serve two specific, operational purposes:
Peers know why the departure actually happened. They saw the daily operational friction, felt the management gaps, or heard the informal feedback long before the resignation landed on your desk.
In a direct, peer-to-peer 1:1, ask focused questions:
You will gather more actionable operational context from fifteen minutes with a remaining teammate than from an hour-long exit interview.
Your team is acutely aware that work flows toward competence. When a high-performing peer leaves, remaining staff immediately worry about being quietly saddled with extra coverage indefinitely.
Use the 1:1 to eliminate ambiguity:
Reassurance without operational structure feels like empty rhetoric. The fastest way to restore team confidence is demonstrating immediate, systematic control over the transition.
When remaining employees see leadership launch an intensive 5-day capture sprint (redirecting the departing employee’s time toward documented walkthroughs and rapid handoffs), the emotional climate shifts. Anxiety turns into operational certainty. They see that leadership is actively protecting them from unmanaged workload spillover.
Stabilizing team sentiment is the emotional half of triage. The operational half requires systematically extracting what the departing employee knows before they walk out the door.
To learn how to convert a sudden exit into a permanent infrastructure upgrade, read our full framework: Converting Crisis into Leverage: Building Operational Resilience from an Unexpected Exit.
]]>That approach is a mistake. Resignations are not uniform, and treating every departing employee with the same playbook wastes critical management bandwidth.
To respond with authority, you need an objective diagnostic tool before launching execution. That tool is the Aptitude vs. Attitude Matrix.
Every role in your organization sits at the intersection of execution and interpersonal behavior. When someone departs, these two dimensions dictate where your management focus belongs:
HIGH ATTITUDE
│
The Emotional │ The Core Loss
Dilemma │
│
LOW APTITUDE ───────────┼─────────── HIGH APTITUDE
│
The Hiring │ The Operational
Misstep │ Trap
│
LOW ATTITUDE
This is the hardest resignation to absorb. You are losing both technical leverage and organizational stability simultaneously.
These individuals are often emotionally exhausting for managers and peers. They deliver results, but their behavioral friction creates subtle, ongoing conflict.
When a team member is well-liked but technically underperforming, their resignation is often a blessing in disguise operationally.
An employee who delivers poor work and brings friction to the team environment.
Once you have triaged the departure, your immediate focus shifts to execution:
The problem is not a lack of discipline. The problem is a cognitive mismatch.
When you ask someone to execute a complex task and simultaneously write a Standard Operating Procedure (SOP) about it, you are forcing them into a state of dual-task interference. They are trying to execute real-time problem solving while simultaneously attempting metacognitive synthesis and structural editing.
As philosopher Michael Polanyi noted, “We know more than we can tell.” Your operators possess deep tacit knowledge: subconscious, intuitive patterns built through repetition. Forcing them to stop, format a document, and articulate those subconscious steps creates severe behavioral friction.
To capture operational truth, you must uncouple the capture mechanism from the synthesis mechanism.
Instead of asking operators to write, ask them to talk.
Have them record their screen and use their microphone to explain what they are doing, while they are doing it. Instruct them to work stream-of-consciousness in their regular day-to-day flow. No syllabus, no agenda, no formatting. Just raw, narrated execution.
This reduces the activation energy to near zero. It leverages the “Think-Aloud Protocol,” a proven cognitive science method where verbalizing actions in real-time bypasses mental blockades and makes tacit knowledge explicit.
Once you have the raw video and transcripts, large language models (LLMs) take over the heavy administrative lift. AI can extract screenshots, organize themes, identify process variances across a team, and generate structured process documents.
You capture the reality of the work without dragging down the productivity of the worker.
You cannot scale what you do not accurately understand, and you will never accurately understand your operations if you rely on forced, manual documentation.
Shift to stream-of-consciousness capture. Let operators do the work, let AI handle the synthesis, and secure your operational resilience before the next unexpected transition forces your hand.
]]>Take the evening. Learn from it, but don’t over-index on it. Take a breath: you’re going to be okay.
Then, focus on execution. The one thing you must not do is sit on the news.
Under normal circumstances, you get about ten business days of notice. Far too often, managers let daily fires and awkward emotions quietly consume three, five, or all ten days. Before they know it, years of institutional knowledge walk out the door in a cardboard box and a goodbye lunch.
When someone retires, companies plan for months: phased hours, mentoring, capture interviews. A resignation compresses all of that into two weeks. That means your response has to be immediate, deliberate, and structured.
Before launching into action, sort the situation on two axes. This dictates where management effort belongs:
The standard resignation pattern is a week of drift followed by a panic scramble in the final 48 hours, which is the worst possible time to ask someone to dump their brain onto a blank page.
Instead, compress the active knowledge capture into a 5-business-day sprint.
The 5 days are hard on purpose so that the final days are easy.
Front-loading the capture in the first week accomplishes three things:
The kickoff happens the morning after the resignation:
While knowledge capture runs, a second track runs beside it: evaluating the seat itself.
Because you front-loaded the capture into Week One, Week Two is about validation and closure:
Immediate Kickoff (Day 1)
Active Capture Sprint (Days 2–5)
Testing & Handoff Phase (Week 2)
Attack the problem. Take advantage of the learning opportunity. You’re gonna be okay.
This is a field note from the Urnicus practice. For more writing, visit our field notes.
Last updated: August 3, 2026
]]>Sergiovanni’s “heartbeat” is an organization’s shared beliefs and sense of identity, often referred to as core values. His argument is that lasting success doesn’t come from mandates, rules, and incentives handed down from the top. It comes from moral authority: a community whose members are intrinsically motivated because they believe in the work and in each other.
He draws a sharp line between two ways to lead:
The distinction sounds academic. I’ve been fortunate to work in many different organization types (software, manufacturing, political campaigns, elected boards, volunteer boards) and the pattern shows up in all of them. I could never put my finger on what leadership transitioned those organizations into effective ones until Sergiovanni helped me recognize it. I always “felt” I was on the wrong path when I started to “over-systematize” in response to missed outcomes. I now recognize that feeling as the cue to step back and reassess the culture, not the rules.
The extrinsic trap is when control becomes a substitute for commitment. You feel it the moment the rules stop serving the mission and start standing in for it: rigid hour requirements, attendance policing, narrow scripts for how every task must be done. Leaders (myself included) are tempted to reach for these rules when commitment runs thin: monitoring software pointed at employees, process gates bolted onto a manufacturing line, a volunteer board that socially criticizes attendance instead of inspiring it, or a manager who dogmatically requires process meetings.
At some level you have to operationalize outcomes: name the goal and track whether you’re hitting it. Even the most values-driven leader needs that discipline, and a dashboard that helps a committed team see how it’s actually doing is a good tool. The instrument panel isn’t the problem. It’s when it is treated as the mechanism to make people care.
It backfires in a specific, predictable way. Decades of motivation research point in the same direction: a 1999 meta-analysis of 128 experiments found that tangible, expected rewards reliably undermine people’s intrinsic motivation for work they were already inclined to do. Pile enough external reward and surveillance onto something someone cared about, and you slowly teach them it was only ever a means to an end.
The people held inside those rules stop being creative, they burn out, and they stop caring. The rules fail to produce compliance and the real cost is the loss from the benefits of intrinsically motivated humans.
Create the environment that unlocks people who are already aligned with the mission and would do the work whether or not anyone was watching. A different phenomenon starts to take shape: they don’t need to be managed into motion. They need to be trusted and pointed in a direction.
Sergiovanni’s word for the container that holds these people together is a covenant, as opposed to a contract. A contract is transactional: do X, get Y. A covenant is a shared set of commitments to a purpose and to one another. When a group operates on a covenant, people work hard not because they’re forced to, but because they believe in what they’re building together, and they don’t want to let the others down.
A covenant is socially contagious, which makes rollout within a rigid organization possible. Once a handful are genuinely operating in this manner, the covenant becomes a social construct and people start to fold into it. An individual who spent years inside extrinsic systems arrives expecting to be managed by carrots and sticks, and within a few months recalibrates when they observe the people around them working from something else. Culture does the onboarding, and most people are simply waiting for permission to care.
Build that covenant, get buy-in from your social group, and the outcomes are remarkable. Intrinsically motivated people in a moral community don’t just execute the plan, they improve it. The most exciting outcome is the creativity that explodes. Your reach extends past anything a manager could have scripted, because you’ve multiplied yourself through people who are excitedly thinking and not just complying.
Strengthening your organization’s heartbeat is a discipline. A few things I try to practice:
Sergiovanni was writing about schools, but the heartbeat is universal. Campaigns, nonprofits, companies, boards: anywhere people gather to do something that matters, the same choice presents itself. You can try to control your way to compliance, or you can build a community worth committing to and lead by moral authority.
The second path asks more of you as a leader. It’s also the only one that scales past what you can personally supervise, and the only one that leaves people better than you found them.
This is a field note from the Urnicus practice. For more writing, visit the field notes.
Last updated: July 6, 2026
]]>