FDE01Forward deployment
Handbook 02

Echo and Delta: complementary responsibilities

How do business discovery and engineering work together?

On this pageChapter guideDiscussion questionRelated exercise

Chapter guide

The course uses Echo for business discovery and Delta for engineering delivery. One asks whether the problem is worth solving and whether the organization can change; the other asks whether the solution will work in real systems. These Palantir labels are not a universal division of work. Engineering roles generally also require production coding skills.

Share four kinds of information: field findings, technical constraints, solution options and interpretation of pilot results. Ask the recipient to explain the facts, decisions and open questions in their own words to check understanding.

When a customer says, “Just decide for us,” confirm the actual authority being granted. Take options, costs, consequences and review conditions to an authorized customer owner. If you handle both discovery and engineering, check each perspective separately.

The five stages of the course
The five stages of the courseFollow this sequence to learn and practice. Revisit earlier judgments when findings, risks or permissions change.FoundationsRoles & ownershipDiscoveryField evidenceDesign & riskOptions & controlsPilot & adoptionTest & adoptValue & handoverTransfer & learnKeep four records current: facts / assumptions / decisions / outcomes
Follow this sequence to learn and practice. Revisit earlier judgments when findings, risks or permissions change.Swipe to view the full diagram.

Discussion question

Are you recommending an option, or committing on behalf of someone you cannot represent?

Related exercise

Follow the related lesson below and try its exercise. Use the linked template to record your judgment, evidence and open questions, then revise with the checklist. With a partner, check which parts of each other’s work need clarification.