01
Clarity about what the new standard looks like
Not hints. Not hedges. The actual bar the AI-native team will be held to. Write it down. Walk every affected person through it.
Slide 01
Your Finance team still prices every line of code as if a human has to type it. Your HR team still benchmarks against 2018 comp data. Your governance framework still assumes code is expensive to produce and cheap to review. AI inverted that economics. Your org did not rebuild. It bolted agents onto a 2019 process framework and called it transformation.
Slide 02
"I have fought for your renewal and I cannot get it done. You have four months." I was not angry. I had four months to find a better role, and I did. Deb was my reference. She is still someone I respect deeply, because she led with honesty when it would have been easier to delay the conversation and hope something changed.
Leading with empathy is not softening the message. It is giving people time.
Not hints. Not hedges. The actual bar the AI-native team will be held to. Write it down. Walk every affected person through it.
Dedicated hours every week. Not thirty minutes scraped from sprint margins. If you do not protect the time, it will not happen. That is your failure, not theirs.
Not a PIP and a timeline. The engineers who will struggle are not bad engineers. They were exactly what you needed five years ago. The system changed underneath them.
Even if that path eventually leads outside the team. The kindest leader I have seen sat with each person and said: "Here is what is changing. Here is why. Here is the time and support I am putting behind it."
Slide 03
Slide 04
Claims processing. Internal dashboards. Customer portals. Partner onboarding workflows. Three bedrooms, two baths. Boring, profitable, get-it-done-right software. These are ranch homes. They need to be shipped, not reimagined.
A spec. A design review. Sprint planning. Estimation. A demo. A retro. A hardening sprint. A release candidate. A staging environment. A production release window. Six months of ceremony for a ranch home.
A principal reads the business rules, builds a working prototype with an agent by end of day, walks it over to the business owner the next morning. "Is this what you meant?" "Almost, change the approval threshold and add an exception for international orders." Done by lunch.
That conversation — the one between the craftsman and the homeowner — is where all the value lives. Every person you put between those two people adds cost and removes fidelity.
Slide 05
A senior principal costs $250K-$350K fully loaded. Four of them: $1.2M. They ship a line-of-business app in weeks, then start the next one. No interpreters. No hardening sprints. No ceremony.
20 juniors at $120K: $2.4M. 3 eng managers at $200K: $600K. 2 scrum masters at $130K: $260K. QA team of 4 at $110K: $440K. PM at $150K. Architect at $250K who spends half their time in governance meetings.
Your four most expensive engineers are your cheapest team. Not despite their salary — because of it. Transition cost: $1M-$2M once. Payback period: under a year. Your CFO has approved worse bets with longer payback.
The $300K principal is your most cost-effective employee, not despite their salary but because of it.
When you average the total cost per head across a twenty-person team — salaries, managers, coordinators, rework, delay — your cheapest-looking team turns out to be your most expensive one.
Slide 06
A platform that needed to be dismantled and rebuilt. The standard playbook said build a proper team. Nathan looked at that plan and threw it out.
He did not hire a single person. He kept one existing associate and took direct ownership of technical direction. For a company doing millions in revenue with a platform that needed rebuilding.
The person making architectural decisions was the same person writing the code, with twenty years of production experience backing every choice. Higher quality. Lower cost. Real output.
Versus the $1.5M-$2M the ten-person plan would have burned. Fraction of the cost. The numbers are real. The company is real. The output is documented.
Slide 07
Slide 08
An agent can generate code. It cannot design a system. It does not know where the boundaries belong, or why the last team's architecture collapsed under load at 2 AM on a Thursday. That knowledge comes from building systems and learning from the ones that failed.
Can this person take your payment system or claims process and break it into pieces an agent can work within? The engineer who explains the payment rules in three sentences directs an agent that builds the right thing.
Can they externalize their thinking with enough precision that another intelligence — human or AI — could execute it without a follow-up conversation? Most engineers never had to do this.
Read a function, spot the edge case the agent missed, identify the security vulnerability it introduced, decide whether to fix or rewrite — all in minutes. You do not train that in a workshop.
Can they build the compliance framework, not just follow one someone else wrote? Design an audit trail, not generate an artifact? This is the qualification that did not exist two years ago.
The most dangerous engineer is the one who accepts agent output without understanding it. Hire people who say "I do not understand what this does yet" instead of "it passes the tests, ship it."
Slide 09
A PM talks to a customer, builds a working proof of concept with an agent, iterates with two customers, and hands engineering something validated. The spec is dead. The POC replaced it.
The engineer's job shifts from "interpret a spec and build" to "take working software and make it production-grade." Error handling, load resilience, security review, monitoring. A more demanding job than the old one.
The testing pyramid was a financial compromise when humans wrote every test. Agents removed the cost constraint. Equal investment across unit, integration, end-to-end, and contract tests. The pyramid is obsolete.
One agent platform. One set of guardrails. Your best salesperson did not pick Salesforce. Your CRO did. The same logic applies to AI tooling — the CTO picks the platform, not the loudest engineer in the Slack channel.
Slide 10
Slide 11
Not a sandbox. A real line-of-business application with real users. Identify four principals who demonstrate judgment, specification skill, domain knowledge, and the governance instinct to own their compliance workflow.
Cycle time. Defect rate. Cost per feature. Compare honestly to what your traditional team produces. Start the broader people assessment. Give every engineer four hours a week of real learning time.
Not everyone will qualify on the first pass. That is expected and it is not a verdict on their worth. Some who do not qualify in month two will qualify in month six if you gave them the learning time you promised.
The pilot is four people and one application. The blast radius is contained. Fail fast and fail cheap before you commit organizational capital to a restructuring you cannot reverse.
Slide 12
Slide 13
Every person on your current team showed up because you hired them. They moved their families. They turned down other offers. They built their careers around the structure you created. If you are going to change that structure — and I believe you should — you owe them the same respect you would want if someone changed the rules of your job while you were doing it well.
Coal shovelers. Chief power officers. Milkmen. Nobody thinks those transitions were wrong in hindsight. But every one of them involved real people who built real skills around a model that stopped being the model. The question is not whether this transition happens. It is whether you lead through it like Deb, or whether you wait until the budget is already gone and hand someone a box on a Friday.