AI Enablement: Shift Harness's collection on AI Enablement of Delivery Teams. Expect field-tested guidance on developer productivity metrics, written for CTOs and delivery teams.
AI Enablement
Eighteen months into the agentic-coding wave, the question CTOs are asking has shifted from which tool to why the delivery numbers have not moved despite real adoption and real developer speed gains.
AI Security
Three lines of hidden text in a README can exfiltrate your AWS credentials while Claude finishes your task. That is not a thought experiment. It is a documented production attack vector.
AI operating model
Adoption metrics say AI is in. Delivery metrics say nothing changed. The gap lives in one place: the manager layer. Five behaviors to redesign before the next quarterly readout.
AI in Software Delivery
Ticket, code, review, test worked when senior engineers carried the goal, the architecture, and the risk in their heads. Coding agents cannot read minds. The work those four stages hid now has to become explicit, or the agent guesses.
AI in Software Delivery
Your developers ship code faster, pull-request volume doubles, and the lead-time number your board watches does not move. The speedup was real. It just relocated the constraint to the stages nobody re-staffed.
AI operating model
Your engineers are shipping more code than ever and the delivery metrics still have not moved. The gap is usually a missing control layer: written intent that an agent's output gets reviewed against, before anything is generated.
AI Enablement
Most open with license count: a procurement number dressed up as a transformation metric. Here is what an honest dashboard drops, what it tracks instead, and why it is really a decision about your operating model.
AI governance
Every AI failure I have investigated had a human who pushed the button. Automation is a delivery mechanism, not a transfer of responsibility.
AI Adoption
Eighteen months in, the licenses are paid and the dashboards haven't moved. AI adoption fails as procurement and succeeds as role redesign. Five issues that compound in this exact order.
AI Enablement
Dev, QA, PM, BA, SA - five delivery roles, five different ways AI breaks them. Generic training fits none. The fix is a per-role playbook with four components, the last of which is the part a manager can inspect in five minutes.
AI Adoption
The 4-Level AI Adoption Evaluation Model: How to Tell What Your Delivery Team Has Actually Changed
AI Adoption
Most AI programs stall around month nine because nobody can show the board what actually changed. A five-rung ladder that places an org by the artifacts it produces - PRs, ADRs, test plans, postmortems - and names the missing operating asset at each rung.