AI Transformation Case Method

How do you turn a spec into a case for change?

Start with the business. End with a decision. AI is the redesign lens, not the subject.

Outcome

Produce a confidence case that makes one reader able to approve, reject, or investigate one bounded AI transformation bet. The work is rhetoric in service of wisdom: public judgment under pressure, aimed at a better decision.

Inputs

Input	Purpose
Business spec	Names the company, model, goals, constraints, and known pain.
Company evidence	Grounds the case in live public and private facts.
Workflow inventory	Names what work is real, artifact, or hybrid.
Market signals	Shows why the window is open now.
Existing playbook	Provides reusable method, not client-specific proof.

Steps

1. Internalize the spec. Name the reader, the business model, the decision, and the first workflow candidate.
2. Research reality. Gather company evidence, tech/data flow, customer signals, competitor signals, and operational constraints.
3. Develop the rhetoric. Use Ethos, Logos, Pathos, Topos, and Kairos to pressure the claim, objections, proof path, timing, and shared frame before writing report copy.
4. Backcast the bridge. Define the 24-month future state, 12-month milestone, 90-day proof, and day-14 prerequisites.
5. Assemble the report. Write present-day reality, desired future, bridge with confidence, evidence, rhetoric, and decision as one chain.
6. Gate the case. Every major claim must trace to the evidence ledger or argument map.
7. Close the loop. After dogfood, update the template or module that produced the weak output. Do not patch only the rendered page.

Rhetoric As Wisdom Work

Rhetoric is not polish. It is the skill that turns private belief into public judgment another mind can test. It develops wisdom because it forces the case to answer when, where, with whom, and under what proof condition the next action is right.

Use the belief articles as the philosophical spine:

• Rhetoric — public judgment under pressure: Ethos, Logos, Pathos, Topos, and Kairos.
• Wisdom — knowing when, where, and with whom to act.

Outputs

Output	Done When
evidence-ledger.md	Every major claim has source, date, status, and confidence tag.
argument-map.md	The thesis, objections, counters, and reader action are explicit.
confidence-case.md	Reality-Dream-Bridge is written as a decision argument.
_case-manifest.md	Input, research, rhetoric, presentation, and privacy status are mapped.

Checks

• The case has one named reader.
• The first workflow is named.
• The 90-day proof has a metric, owner, budget, and kill signal.
• Each major claim is tagged VERIFIED, INFERRED, ASSUMPTION, or CONTRADICTED.
• The report contains no fresh claim that is absent from the evidence ledger or argument map.
• Private client proof is not linked from public discovery surfaces without explicit consent.

Failure Modes

• AI-first framing. The report sells tools instead of business change.
• Research without rhetoric. Sources pile up but no belief changes and no decision becomes easier.
• Optimistic bridge. The plan has no kill signal, owner, or early proof.
• Output patching. A page improves once, then regresses because the module was not changed.

Context

• Case Report Template
• Evidence and Confidence Gates
• Future Backcasting for AI Transformation
• AI Transformation Roadmap
• Rhetoric
• Wisdom

Questions

• What does the reader need to decide after reading?
• Which first workflow can prove the whole thesis without betting the whole business?