From fieldwork to lasting business capability.FORWARD-DEPLOYED ENGINEERING
FDE Academy
WEEK 10 / PHASE 4

Attribution and project acceptance

Acceptance · Observation windows · Controls · Outcomes

Prove value. Leave capability behind.4 lessons · 8–10 suggested hours including practiceOutcome: Create three-layer acceptance evidence, reproducible analysis, attribution limits and next actions.
FIELD JOURNAL / 04Acceptance and reuse

See the structure, then implement and verify with the notes.

Acceptance and reuse
This page retains the English overview and workshop. The expanded practitioner lecture notes are currently available in Chinese. Read the complete Chinese lecture →
AIelsen / FIELD BOARD · W10
10.1
An 8-point rise is not all incremental impact

Synthetic arithmetic: treated +8 pp, control +5 pp, difference +3 pp. Four points do not establish causality or uncertainty.

THIS WEEK IN THE FIELD

What situation are you walking into?

Repeat purchase rose alongside a holiday campaign and price changes. Finance asks how much the system caused. A polished growth chart cannot answer that alone.

DELIVERABLE / Attribution analysis + acceptance pack + outcome boundaries

01 / Three evidence layers are not interchangeable

System evidence covers quality, authority and reliability; behavior covers use, edits, rejections and execution; business evidence covers agreed outcomes. Good quality with low adoption suggests workflow problems. Adoption without outcomes calls for testing assumptions and observation windows.

Report target, sample, window, result and limitation for each layer.

02 / Design attribution before calculating it

Prefer randomized controlled pilots when feasible. Otherwise document comparison selection and assumptions. Difference-in-differences compares changes but requires a credible counterfactual, no contamination and relevant trend assumptions. Non-significant pre-trends do not prove validity; small samples and staggered rollout need care.

When assumptions are unsupported, report descriptive change rather than causal impact.

03 / Released hours are not automatically cash savings

Measure task-time distributions and frequency before valuing released capacity. Revenue contribution needs discounts, fulfillment, returns and acquisition cost adjustments. Avoid double-counting overlapping initiatives. Separate observed benefits, attributable benefits and commercial payment outcomes.

The cost lab computes scenario economics, not customer revenue forecasts.

04 / Outcome-linked acceptance needs shared boundaries

An acceptance pack includes scope, versions, tests, usage, analysis, unmet items and next actions. Outcome-linked agreements require definitions, data access, responsibilities, external-factor handling and dispute limits. The source course’s Outcome-Level Agreement is not a standard acronym; IT service OLA commonly means Operational Level Agreement.

Actual contracts and outcome pricing need professional review; templates are not legal advice or performance guarantees.
WORKED EXAMPLE · SYNTHETIC

Put the method to work

Synthetic data: treatment moves 20% to 28%; comparison moves 18% to 23%. The raw change is eight points; DiD is (28−20)−(23−18)=three points. A causal interpretation needs credible assumptions, and statistical significance is not established by this arithmetic.

Practice this week

  • Complete three-layer acceptance evidence with unmet items.
  • Reproduce before/after and comparison calculations with assumptions.
  • Rehearse reporting inconclusive results and propose the next test.

Acceptance checks

  • Percentage points and percent changes are distinct.
  • Correlation, adoption and prediction are not presented as causation.
  • Unmet targets and shared conditions are disclosed.
FIELD WORKSHOP / W10

90 minutes: write a defensible value report

Synthetic treatment retention rises from 20% to 28%; comparison rises from 18% to 23%. Separate observations from identification assumptions. Two time points cannot test pre-intervention parallel trends.

  1. 0–20 min: define eligibility, windows and contamination: simultaneous promotions, price changes, attrition and cross-store spillovers.

  2. 20–55 min: calculate changes and DiD. Judge whether causal interpretation is justified; propose history or an alternative design if necessary.

  3. 55–90 min: build an acceptance index separating system quality, usage, outcomes and unmet conditions. Authorized parties confirm commercial decisions.

Artifact excerpt · synthetic example

Observed: treatment +8 pp; comparison +5 pp
Arithmetic difference: 8 - 5 = 3 percentage points
Not: 3% revenue growth or a threefold improvement
Assumptions: parallel trends, no differential shocks, stable composition
Missing: pre-trends, sample size, clustering and uncertainty
Report: a teaching calculation, not demonstrated causal impact

Instructor review

Separate controllable actions from external conditions. Do not conflate SLAs, outcome metrics and payment terms. Define the course-specific OLA usage and obtain professional contract review.

An unseen field challenge ↗

If the system meets acceptance but outcomes do not improve, specify evidence-based conditions for continuing, changing course or stopping.

Download offline practice kit ↓
AIelsen / FIELD BOARD · W10
10.2
Review the system, adoption and outcomes separately

The three evidence classes are related, not interchangeable. Frequent use is not causal uplift, and growth does not waive safety.

ONE-MINUTE CHECK

Treatment gains 8 points; comparison gains 5. What is DiD?

Local storage is not encrypted; do not store sensitive content on shared devices.

References and further reading

World Bank DIME ↗ · Difference-in-Differences2023-08-07 · World Bank DIMEWorld Bank ↗ · What to do about parallel trends when you only have baseline data?2023 · World Bank神策数据 / Sensors Data ↗ · 从卖工具到卖效果:RaaS 如何重塑 ToB 市场格局?2025-10-29 · 神策数据 / Sensors Data

Read alongside the assignment and record design constraints and tests. Verify specifications against your deployment version.

Teaching board
Download SVG ↓

Search runs locally. Queries are not uploaded.