1/6
The first AI leadership crisis will not be technical. It will be cultural.
Tech Lead Shift is a 10-article series on what happens to management when some of your team is not human.
Start here. Then follow for the rest of the argument.
1
12
On Thursday, Outlook, Teams, SharePoint, and Copilot went partly down together. The work didn't stop. The tools did.
A phone call. Another chat app. Personal email. A whiteboard. Or just waiting.
What did your team fall back to on Thursday?
3
A model can raise any count you report. Our PRs and Jira stories climbed, and the AI-written stories were fluff. One engineer's numbers rose with his value. The count alone couldn't tell which was which.
Volume is free now, so stop paying for it.
techleadshift.substack.com/p…
4
Machine output is cheap. I don't know yet whether the best facilitators become the architects or report to them.
Article 10 of 10:
techleadshift.substack.com/t…
3
The leader's job now is the system of work. Who can start it. Which exits need a name. What "accepted" means. Where refusal shows up.
1
3
Article 9 showed a change that left without a name. No amount of facilitation would have put one there. Somebody had to design the record so it couldn't leave blank.
1
3
Orgs keep hiring for presence. Change champions. Town hall people.
The failure I keep seeing is still an owner field with nothing in it.
1
3
Put the constraint in the platform. Owner field = a person. Split produced from accepted. Define the exits that need a name. Only those.
Shipping without owning isn't transformation. It's negligence at the speed of a generator.
1
Authorship can be mixed. Accountability cannot.
You cannot assign accountability to a model. You assign it to the human who let it out the door. The name on the exit ; not a slogan, not a committee.
1
1
An AI-built POC went live with a route to the outside. Everyone knew the exposure needed a review. Nobody owned that step.
Dummy data. Real exposure. No name on it.
1
1
Machines took the fingerprints — first drafts, tickets, the 11:40 p.m. spreadsheet, the small call that sat on top of the work.
When those leave without a name, you don't get shared ownership. You get a finished artifact and an empty chair.
1
2
We used to know who was accountable because we knew who typed it.
That wasn't a philosophy. It was a shortcut. And the shortcut is already dead.
1
2
What this show is:
Not vendor news.
Not “learn to code.”
What the job is actually like — helpdesk through leadership.
New episodes at theitxp.com
Longer leadership argument: @techleadshift
6/6
Read article 1 first. It is the frame everything else hangs on. techleadshift.substack.com/p…
Follow @techleadshift. When a new essay goes up, it lands here first.
5
5/6
How I write these:
Not vendor demos. Not framework cosplay.
Something that happened while leading technology teams that week, then the pattern underneath it.
If you lead IT, engineering, or a hybrid human–AI operation, this is for you.
1
6
4/6
Act II is the transformation (in progress):
Middle management in the age of AI
Why culture matters more when machines work for you
The accountability problem no one is ready for
The future leader is a system architect
New essay every four weeks. No weekly digest.
1
3
3/6
short version of Act I:
We built leadership for an all-human workforce. Agents don't sit in standups.
Delegation decays when you can't see the work. Theater looks like progress until the system is load-tested. If that matches what you are seeing, the essays are the receipts.
1
2
2/6
Act I is the diagnosis. Six essays, already live:
The crisis is cultural
Managing the invisible worker
Delegation drift
Why AI exposes bad management faster
Systems thinking as the new leadership skill
The end of productivity theater
Full series: techleadshift.com
1
4

