Learn one boundary at a time.
Free. Build the vocabulary for workflow, evidence, evaluation, authority, memory, delegation, and human review.
The 19 Core Labs teach individual deployment boundaries. Deployment Missions force you to apply several of them at once, inside a realistic customer timeline with conflicting evidence, operational constraints, a staged complication, and a final release decision.
All eight environments are complete mission experiences with evidence rooms, working slices, quality gates, artifacts, complications, and published rubrics.
Each Mission assigns a role, a bounded operating decision, an evidence bundle, a hidden complication, and a final deployment recommendation. You are graded on the coherence of the whole deployment record, not on whether you guessed a predetermined answer.
Free. Build the vocabulary for workflow, evidence, evaluation, authority, memory, delegation, and human review.
Use the same methods under one customer timeline where data, incentives, policy, operations, and executive pressure interact.
Filter by practice area. Each case can be approached through different professional roles, producing different artifacts and decisions.
Role: Forward Deployed Engineer
Build a maritime delay decision system from unstable vessel, port, booking, and cost data.
Role: FDE / AI Deployment Lead
Unify production evidence to accelerate defect investigation without overstating causation.
Role: AI Deployment Lead
Deploy a governed knowledge assistant across manuals, bulletins, work orders, and technician notes.
Role: Solutions Engineer / FDE
Design inventory-transfer recommendations that balance demand, economics, inventory confidence, local knowledge, and human authority.
Role: Forward Deployed Engineer
Design dispatcher-controlled disruption recovery with hard accessibility, labor, safety, service-floor, and evidence constraints.
Role: FDE / Operational AI Lead
Create a resilient storm-response prioritization and crew-assignment system.
Role: AI Deployment Lead
Assist claims triage with source evidence, auditability, human authority, and bias controls.
Role: Enterprise Implementation Lead
Coordinate clinic capacity without overriding privacy, clinical restrictions, or local control.
Missions are not clean tutorials. They test what you trust, what you build, who must be involved, and how you respond when the first plan becomes incomplete.
Initial customer request and operating context.
Conflicting source material and missing facts.
Commit to the problem frame and open questions.
Minimum workflow, architecture, risks, and metrics.
A working operational slice with failure handling.
New evidence forces a documented revision.
Pilot, rollback, training, support, and ownership.
Mixed results lead to a scale, revise, or stop decision.
Launch access remains free while the mission layer is being calibrated. Standard individual pricing is $49 for Core Missions, $59 for the advanced Energy mission, and $79 for regulated Insurance and Health missions.
Learn the D2V method and vocabulary before entering a customer simulation.
FreeComplete evidence room, eight-stage workflow, complication, notebook, artifact studio, rubric, and portfolio export.
Launch access is currently freePlanned individual bundle for the full mission library, portable artifacts, and new missions released during the membership year.
Practice across the full libraryFacilitated missions, team calibration, manager review, and a final deployment decision record using the organization’s own operating context.
Discuss team access →Mission-specific subcriteria vary, but every case uses the same top-level assessment model.
| Dimension | What strong work demonstrates | Weight |
|---|---|---|
| Discovery and problem framing | The work identifies the actual operating decision rather than accepting the requested feature. | 15% |
| Workflow and stakeholder understanding | Users, authorities, incentives, handoffs, exceptions, and ownership are explicit. | 10% |
| Architecture and technical judgment | The design is coherent, appropriately scoped, secure, and grounded in constraints. | 15% |
| Implementation quality | The core workflow works, handles failures, and produces inspectable evidence. | 20% |
| Reliability, security, and governance | Controls match the risk of the operating environment. | 10% |
| Deployment and adoption | The pilot, rollout, support model, workflow transition, and owner are designed. | 10% |
| Value measurement | Technical, adoption, operational, and financial measures support a decision. | 10% |
| Communication and documentation | Technical and executive audiences can understand the evidence and recommendation. | 10% |
Review the sequence, twelve-week build plan, content-access model, and publication quality gate.