The instructional decisions, evidence, and next steps.
Teach the workflow, not the interface inventory.
The proposed audience is a new user who needs to get work to a teammate. The target performance has five observable parts: a named project, a review task, an owner, a due date, and a workflow state that communicates readiness.
Orbit is a purpose-built simulation of a fictional product. It offers real form entry and validation within a bounded workflow; it does not claim to reproduce a commercial application.
Demonstrate the structure. Remove the prompts.
The first task breaks the workflow into three manageable steps. Contextual explanations connect each field to its purpose. A second brief changes the project, task, reviewer, and deadline, then removes the step-by-step coaching.
This uses scaffolding and fading: initial support helps learners organize the task; independent practice asks them to apply that structure. A workflow hint remains available, and the debrief reports whether it was opened.
Align the framework with the evidence.
Backward design starts with the completed handoff and works back to practice. ADDIE provides a planning lens for the proposed gap, objective, activity, and evaluation. Iterative prototyping makes the validation rules and feedback concrete before any learner study. These are design methods for a concept, not a claim of a completed organizational rollout.
Measure independence, then remediate.
The debrief preserves the first submission against five criteria, even after corrections. A proposed pilot would compare completion, field-level errors, hint use, and time on task between this activity and a static quick-start guide. A later, unfamiliar handoff would check retention.
Remediation targets the missed field. An incorrect workflow state triggers a distinction between a draft ready for review and a completed task. Learners keep their entries, correct the issue, and resubmit. Repeated errors across participants would prompt a revision to the instruction or interface.
Simulation success is a proximal measure. Transfer would require an equivalent task in the real target product, observed without coaching. No learner results or business impact have been measured.
Design the support into the product.
Orbit uses a violet-and-ink product language, compact workspace navigation, native form controls, and contextual feedback. The interface is deliberately separate from the portfolio’s visual identity so the work reads as customer education inside a product.
My contribution.
Performance objective, task sequence, simulation scope, assessment criteria, remediation copy, visual direction, and iteration, with AI-assisted implementation.