The forward-deployed engineering kit
Working documents for deciding whether an enterprise needs an internal forward-deployed engineering (FDE) practice, for setting one up, and for running it. Each is a Markdown file that pastes into any wiki, and a page that prints to PDF. Where an article gives a worked example, the template carries it as a specimen. The specimens are hypothetical.
Deciding01 doc
From What Forward-Deployed Engineering Does
- 01Delivery diagnosis.md
Trace stalled requests, classify what stopped each one, and decide whether the pattern justifies a practice.
Setting up05 docs
From Setting Up an Internal Forward-Deployed Engineering Practice
- 01Engagement brief.md
The business process, the proposed solution and its alternatives, the dependencies, the intake gates, and the first commitment.
- 02Decision authority map.md
Each delivery decision assigned to the person who can make it, with the escalation route and the incident route.
- 03Funding plan.md
Three allocations, the value test, the observation period before a chargeback rule, and the proposal portfolio.
- 04Data access request and semantics record.md
The access request by field, the design when access is restricted, and the record that keeps each meaning with the solution.
- 05Interview loop.md
Four rounds with observable behaviours, for engineers who will build with AI coding agents.
Running it04 docs
From Running an Internal Forward-Deployed Engineering Practice
- 01Measurement plan.md
The result, the eligible population, the comparison, the costs, and which value claim the evidence supports.
- 02Operating review.md
Four evidence streams, adoption with its denominator, incidents, changed conditions, and the next commitment.
- 03Transfer record.md
The readiness exercises, what stays with specialists, and which learning later teams can reuse.
- 04Portfolio and practice review.md
The portfolio view, the practice measures, where work waits, and the renewal decision: expand, reorganise, partner, transfer, or close.