# The Last Mile

> A demo is L0. Delivery is L4. Enterprise AI dies in the last mile, not in the model. Written for the people inside a company who take an AI project to production and into daily use: 27 chapters, 24 field templates, 22 zero-dependency scripts.

Site: https://hallieren.github.io/the-last-mile/  
Full text, single file: https://hallieren.github.io/the-last-mile/llms-full.txt

## Chapters

- [0 · The Opening 48 Hours: Turn a Vague Ask into a Field MVP in Two Hours](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch00-field-mvp.md): The Challenge. The business side says "we want an AI assistant." You do not know what is behind that sentence, and neither, in fact, does the business side.
- [1 · The Last Mile Problem: Why Enterprise AI Dies After the Demo](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch01-last-mile.md): The Challenge. The demo was a hit, and the applause was real. Three months later nobody uses the system. You want to know what killed it, and more, how not to die next time.
- [2 · The Internal Deliverer's Position, and Where This Method Comes From](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch02-inheritance.md): The Challenge. The business side gets your name wrong, and you cannot say clearly who you are either. You are not a vendor, yet to the claims department you are an outsider. You are one of their own,
- [3 · Four Identities: Builder, Advisor, Operator, Teacher](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch03-four-identities.md): The Challenge. Four things land on you in one day. A bug to fix, a meeting to take, a person to teach, a weekly report to write. Every one is reasonable, every one has someone waiting, and there is
- [4 · Opening and Agreement: Write the Deployment Charter](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch04-charter.md): The Challenge. After the readout everyone says "continue," and each person's "continue" is a different project. You do not want to find that out in week 10.
- [5 · Trust Ships First: Your First Deliverable Is Not Software](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch05-trust.md): The Challenge. The business side will not give you data, meetings are all pleasantries, and the people who matter can never be booked. Nobody can fault your technical plan, and the project still does
- [6 · Field Archaeology: Dig Out the Real Workflow and Its Tacit Knowledge](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch06-field-archaeology.md): The Challenge. Interviews do not get you the truth, and the flowchart the business side gave you does not match reality. How the work actually happens, you do not know, and you are starting to
- [7 · The Opportunity Screen: Five Questions That Kill Most Ideas](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch07-opportunity.md): The Challenge. The business side and your boss have a dozen AI ideas stacked up, and every one of them sounds workable. Which one, and on what grounds? The harder half is telling the sponsor to his
- [8 · From Use Case to Boundary: Cut the First Thin Slice](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch08-thin-slice.md): The Challenge. The use case is chosen, the charter is signed, and the next day the scope starts to swell. Each extension proposal is reasonable on its own. Accept all three and the project dies. And
- [9 · Data Reality: Score Every Source on the Data Fitness Ladder](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch09-data-fitness.md): The Challenge. The business side thumps its chest and says "the data is all in our system." Why is none of it usable the moment you touch it?
- [10 · Pick the Pattern: Start with the Dumbest Thing That Works](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch10-pattern-selection.md): The Challenge. Does this scenario call for an agent, for RAG, or for a few rules? The whole world is talking agentic (letting the model decide its own next step and call its own tools), and the two
- [11 · Eval as Spec: Write the Eval Before the Architecture](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch11-eval-as-spec.md): The Challenge. The business side asks "what accuracy can this reach," and you cannot give a number. "Accurate" has never been defined. Most internal projects have no acceptance meeting, but on launch
- [12 · Trust Constraints: Turn Your Reviewers into Designers](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch12-trust-constraints.md): The Challenge. Security, compliance and privacy reviews always block the project at the last minute. The reviewer's first sight of the design is the final gate, and saying "no" is his safest move.
- [13 · The Trade-off Story: Win the Decision on One Page](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch13-tradeoff-narrative.md): The Challenge. The plan sounds airtight to an engineer, and the executive hears it out and commits to nothing. Making it clear is not enough. You need the decision.
- [14 · Prototype, Pilot, Production: Three Different Games](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch14-prototype-pilot-production.md): The Challenge. The prototype feedback is good, and yet "let us polish for two more weeks" and "let us watch it another month" both sound right too, and you cannot tell prudence from delay. You have
- [15 · Co-build with the Engineers Who Will Take Over: Handoff Starts at the First Line of Code](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch15-cobuild.md): The Challenge. The claims-ops IT engineers have no time, uneven skill, and a fear of being replaced by AI. "Co-build" sounds fine, and the reality is silence in meetings, assigned tasks done, and
- [16 · Production Engineering: Set the Running Budget Before You Launch](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch16-production-engineering.md): The Challenge. Everything was fine in the pilot, so how does real traffic bring an exploding bill, latency over the line, and something acting up every few days?
- [17 · From Dashboard to Action Queue: Put the Next Action in Front of the User](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch17-dashboard-to-queue.md): The Challenge. The business side loved the dashboard you delivered. Three months later nobody opens it. What is missing between "we can see it" and "someone acts on it"?
- [18 · Launch and Measure: Prove the Gain, Not the Trend](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch18-launch-and-metrics.md): The Challenge. The system is live and the numbers are moving. How do you get everyone to believe the system deserves the credit? An incident happens. How do you keep one error from eating months of
- [19 · Talking to Executives: Three One-Page Memos](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch19-executive-memos.md): The Challenge. An executive gives you ten minutes at a time. The project runs for months. How many times do you actually deal with him, and what do you say each time? Too early is an interruption,
- [20 · Resistance Is a Signal: Decode It Before You Answer It](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch20-resistance-as-signal.md): The Challenge. Someone challenges you in front of the whole room. A team quietly stops cooperating. Are they being unreasonable, or did you miss something?
- [21 · Adoption Engineering: From Usable to Missed When It Is Gone](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch21-adoption-engineering.md): The Challenge. The training was held, the email went out, and the system really is good. The same few people are still the only ones using it. What does adoption actually run on?
- [22 · Make the Business Side Self-Sufficient: Stepping Out of the Daily Transfers Capability, Not Files](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch22-handoff.md): The Challenge. The project is winding down. How do you step out of the daily so that the system does not die three months after you leave?
- [23 · The Pattern Library: Turn Hero Stories into Assets](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch23-pattern-library.md): The Challenge. Every project feels like starting from zero, and the team gets through on individual heroics. How do you make the second project cost half of what the first one did?
- [24 · From the Field to the Platform: Field-to-Product](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch24-field-to-product.md): The Challenge. The project has stepped out of the daily, and the custom code and dozen-odd platform judgments the field produced are rotting in the business line's repo and inside your head. The
- [25 · When to Say No: Intake Rules and Red Lines](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch25-saying-no.md): The Challenge. A project you know is a trap gets pushed at you, and the person proposing it is the one who trusts you most. How do you refuse without burning the relationship? One layer down, how do
- [26 · The Deliverer's Career Path: F1 to F5](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/chapters/ch26-career-path.md): The Challenge. Three years in this work, then five, and what are you? Will you just be a firefighter who costs more every year?

## Field Template Library

- [Template 0 · Field MVP Pack](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-00-field-mvp-pack.md): Companion chapter(s): Chapter 0. The five templates (0.1–0.5) follow the order of the two-hour process and can be copied and modified directly. 0.6, the red line declaration, is an input set before
- [Template 2 · Deliverer Role Charter](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-02-role-charter.md): Companion chapter(s): Chapter 2. Write it inside week 1 and walk your sponsor through it line by line in 15 to 30 minutes. It comes before the Chapter 4 deployment charter. The charter defines the
- [Template 3 · Capability Self-Assessment and F1–F5 Rating](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-03-capability.md): Companion chapter(s): Chapter 3 (capability self-assessment), Chapter 26 (F1–F5 rating and the growth agreement). The first half (3.0–3.6) is the five-axis radar self-assessment: one paragraph of
- [Template 4 · Deployment Charter and Pre-mortem Memo](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-04-deployment-charter.md): Companion chapter(s): Chapter 4 (the pre-mortem sections, Chapter 1). The fillable one-page charter with its seven elements, the 60-minute contracting meeting agenda, and the pre-mortem memo, ready
- [Template 5 · Stakeholder Map](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-05-stakeholder-map.md): Companion chapter(s): Chapter 5. One map plus one self-check. Draw it in week 1 of the project, then update it every two weeks.
- [Template 6 · Field Archaeology Kit](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-06-field-archaeology.md): Companion chapter(s): Chapter 6. The three tools are in order of use. Use the half-day guide to book and complete one shadowing session, keep the friction log throughout, and switch on the
- [Template 7 · Five-Question Opportunity Rubric](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-07-five-questions.md): Companion chapter(s): Chapter 7. The three pieces are ordered by use. Score question by question first (7.1), then summarize and eliminate (7.2), then report (7.3).
- [Template 8 · Thin Slice Definition Sheet and Scope Decision Log](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-08-thin-slice.md): Companion chapter(s): Chapter 8. The four tools work together. Fill in the definition sheet once at project approval and recheck it at every milestone. Draw the boundary map at the same time as the
- [Template 9 · Data Source Inventory, Fitness Scorecard, Reconciliation Checklist, Source of Truth Decision Log](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-09-data-fitness.md): Companion chapter(s): Chapter 9. The four tools are in order of use. Inventory first (9.1), then score (9.2), verify the most expensive rung by reconciliation (9.3), and finally settle the conclusion
- [Template 10 · Pattern Decision Table and Anti-pattern List](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-10-pattern-decision.md): Companion chapter(s): Chapter 10. The three tools are in the order you use them. Learn the spectrum first (10.1), then take every step where AI intervenes through the criteria card by card
- [Template 11 · Eval Spec, Golden Case Collection List, Annotation Disagreement Log](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-11-eval-spec.md): Companion chapter(s): Chapter 11. The three tools are in order of use. Set up the spec skeleton first (11.1), then collect cases by the list to fill it (11.2), and record every disagreement during
- [Template 12 · Trust Constraint Matrix and Security Review Packet](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-12-trust-matrix.md): Companion chapter(s): Chapter 12. The two tools are used in time order. The matrix (12.1) starts being filled after the week 2 constraint interview and updates all the way through the design, a
- [Template 14 · Stage Gate Checklist and Pilot Kill Criteria](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-14-stage-gates.md): Companion chapter(s): Chapter 14. The three tools are in order of use. Use 14.1 first to judge which game you are in and which rules you have to keep, rule item by item with 14.2 at the escalation
- [Template 15 · Co-build Agreement and Knowledge Transfer Cadence](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-15-cobuild.md): Companion chapter(s): Chapter 15. The two tools are used in time order. The agreement (15.1) is signed after the pilot is called and before it starts, one page, signed by both sides, the
- [Template 16 · Production Readiness Checklist and Running Budget Sheet](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-16-production-readiness.md): Companion chapter(s): Chapter 16. The three tools are in order of use. Before launch (prototype up to pilot, pilot to production) run the gate item by item with 16.1. Fill in 16.2's four-ledger
- [Template 17 · Action Queue Design Patterns, Decision Trail Schema, Before/After Workflow Map](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-17-action-queue.md): Companion chapter(s): Chapter 17. The three tools are in design order. Set the column structure first (17.1), then the trail schema (17.2), and last, check the embedding points with the workflow map
- [Template 18 · Metric Tree, AI Incident Runbook, Same-Day Notice](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-18-metric-tree.md): Companion chapter(s): Chapter 18. The three tools are in launch order. Before launch, build the metric tree and baseline (18.1), write the incident runbook (18.2), and have the same-day notice
- [Template 19 · Three-Memo Set (with ADR)](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-19-memo-suite.md): Companion chapter(s): Chapters 13 and 19. The four tools are in project order. Fill the kickoff template (19.1) before a phase starts, the decision memo, which is the ADR memo (19.2), at any midpoint
- [Template 20 · Resistance Decoder, Hard Conversation Scripts, Visibility Governance Pledge](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-20-resistance-decoder.md): Companion chapter(s): Chapter 20. The three tools are in order of use. Decode first (20.1), then have the conversation (20.2), and when it hits the fear of visibility, give the governance pledge
- [Template 21 · Adoption Plan, Super-user Agreement, Operating Cadence Sheet](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-21-adoption-plan.md): Companion chapter(s): Chapter 21. The three tools are in order of use. Do the plan first (21.1), then sign the agreement with your first super-user (21.2), and last lay the cadence into the calendar
- [Template 22 · Handoff Plan, Five Self-Sufficiency Tests, Handoff Cadence Sheet](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-22-handoff.md): Companion chapter(s): Chapter 22. The three tools are in order of use. Fill in the plan template (22.1) when the handoff starts, because until the owners are named, the two sheets after it have no
- [Template 23 · Pattern Extraction Sheet, Asset Register, Library Admission Checklist](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-23-pattern-extraction.md): Companion chapter(s): Chapter 23. The three tools are arranged in flywheel order. At the closeout retrospective, use the extraction sheet to turn hero stories into candidate patterns (23.1), register
- [Template 24 · Field-to-Product Memo and Closeout Asset Recovery Checklist](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-24-f2p-memo.md): Companion chapter(s): Chapter 24. The two tools are arranged in the direction the signal flows. At the asset inventory, run the recovery checklist (24.2) first to count the assets, then take the
- [Template 25 · Intake Rubric, Red Line List, Saying No Scripts, Kill Register](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-25-intake-redlines.md): Companion chapter(s): Chapter 25. The four tools are in order of use. A candidate project clears the red lines first (25.2, any one vetoes), then gets scored (25.1). When the ruling is no, use the
- [Field Template Library](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/template-library-index.md): The master entry point to the book's appendices. The library holds 24 templates, numbered to match the chapter each one serves ("Template N goes with Chapter N"), grouped by the six Parts of the main

## Appendix

- [Vendor Crosswalk](https://raw.githubusercontent.com/hallieren/the-last-mile/main/docs/appendices/internal-fde-mapping.md): Who this is for. You are the vendor-side FDE or delivery engineer, on site at a client under contract, pushing an AI system from demo to production. The text keeps saying "the business side", "your