LESSON 6 OF 7 · DELIVERY METHODOLOGY

Most deployments don't fail on the technology. They fail on the handoff.

By the end of this lesson, you'll be able to spot all six failure modes that appear consistently across Claude Code deployments, what each one looks like before Day 30, and the specific action that prevents each one.

What Goes Wrong

Six failure modes. All of them are preemptable.

None of these failures are technical. Every one of them is a process gap that appears before Day 30 and compounds after the consultant leaves.

Failure 1

No baseline captured

The ROI case falls apart at the Day 30 readout because there is no before state to compare against. The sponsor has no defensible number. Renewal conversation cannot land.

Preemption: baseline sprint in the week before kickoff, non-negotiable.

Failure 2

Champion not identified

Adoption drops sharply 30 to 60 days after the engagement ends. No one owns the CLAUDE.md. New developers don't get onboarded. The deployment decays to zero within a quarter.

Preemption: name the champion by Day 15, begin handoff preparation in Phase 2.

Failure 3

Use case too marginal

Metrics look flat at Day 30 even with high usage. The sponsor expected transformational impact and saw incremental improvement. Executive support evaporates and the renewal fails on scope, not execution.

Preemption: run the structural vs. marginal qualification from Lesson 1 before scoping the pilot.

Failure 4

Supervised mode stagnation

Usage metrics are low or plateau after week one. Developers report the tool is "slow" or "not useful." PR cycle time doesn't change. The Day 30 readout has no productivity story.

Preemption: weekly CoE touchpoint with usage review; workflow-fit coaching for stalled developers in Phase 2.

Failure 5

CLAUDE.md not maintained

Claude reverts to generic behavior as the codebase evolves past what the initial CLAUDE.md describes. Team trust erodes. Developers stop using Claude for complex tasks. Adoption regresses to supervised mode.

Preemption: weekly CLAUDE.md review as a named champion responsibility; include in the champion plan artifact.

Failure 6

Readout not tied to business outcome

The Day 30 readout presents usage metrics and developer testimonials but no business-level translation. The CIO is not engaged. The conversation moves to cost rather than value. Renewal stalls in procurement.

Preemption: align the CIO narrative with the sponsor in week one using the framework from Lesson 3.

What Leaving Well Looks Like

A clean engagement close has four artifacts

If any of these four artifacts is missing at Day 30, the deployment's 90-day health is at risk. The list is short by design. Every item on it addresses at least one of the six failure modes above.

Delivery Plan Pack (complete). All four sections: qualification, pilot design, ROI scorecard, and champion plan. This is the document that anchors the renewal conversation and serves as the reference point for phase two scoping.

CLAUDE.md and custom command catalogue. A populated enterprise-level CLAUDE.md, at least one repo-specific CLAUDE.md for the pilot project, and a command catalogue with a minimum of three to five documented commands. These are the primary tools the champion needs to maintain deployment quality without consultant support.

Day 30 readout with metrics against success criteria. The headline number, the supporting data, and the CIO narrative. The readout should be in the client's hands 48 hours before the showcase meeting, not distributed during it.

Named champion with documented escalation path. A person, a role description, and a clear line to the consultant for issues that exceed the champion's scope. Include the 30-day post-engagement check-in date in the handoff documentation before you leave.

Scenario

Which items put this deployment at risk?

A Day 30 readout is two days away on a 12-developer pilot. Review the engagement status below. Select the 3 items that indicate this deployment is at risk of not renewing.

0 / 3 selected

HIGH

ROI measurement

No baseline captured in the week before kickoff

Pre-pilot data collection was deferred to week one of the pilot

LOW

Adoption

Four of 12 developers are still in supervised mode at Day 28

Tracked in weekly CoE touchpoint notes

HIGH

Champion plan

No champion identified as of Day 28

Champion conversation has not happened yet

LOW

Productivity metrics

PR cycle time improved 20% vs. baseline for the migration cohort

GitHub data, weeks 2 to 4

HIGH

Configuration

No custom commands built during the pilot

CLAUDE.md exists but command catalogue is empty

LOW

Usage telemetry

Usage data shows three developers at high weekly session counts

Claude Code telemetry dashboard

Result

0 of 3 correct

The three risks are: no baseline (the ROI case has no before state to anchor to), no champion identified (the deployment has no owner after Day 30), and no custom commands (the handoff lacks the configuration infrastructure the champion needs to maintain quality).

The non-risks are all normal pilot variance: some developers still in supervised mode at Day 28 is expected and not a renewal risk. A 20% PR cycle time improvement is a good result that should anchor the CIO narrative. Three high-usage developers are champion candidates, not a risk signal.

Course artifact

Course artifact · Complete

Delivery Plan Pack: All four sections complete

You have built the complete Delivery Plan Pack across this course. Four sections, each one directly connected to the engagement decisions it supports.

Qualification section (Lesson 1): use case named, structural or marginal labeled, four criteria scored
Pilot design section (Lesson 2): cohort, scope, duration, two to three measurable success criteria
ROI scorecard section (Lesson 3): three baselines, telemetry metrics, CIO headline number
Champion plan section (Lesson 5): champion candidate named, three handoff artifacts listed, post-engagement health check defined