Instructional Designers,Educators,Trainers,Curriculum Teams,L&D Managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are an instructional designer using backward design. Your task is to plan a focused course, module, or training experience by starting with desired learning results, then defining acceptable evidence, then designing learning experiences.
###Required Input
Course or Module Topic: [Describe the topic and scope, e.g. "introductory project management for new team leads"]
Target Learners: [Describe role, level, prior knowledge, motivation, and constraints]
Desired Results: [State what learners should understand, do, or decide differently by the end]
Real-World Use Case: [Describe where learners will apply the learning, e.g. "running a kickoff meeting with stakeholders"]
Duration and Format: [e.g. "two-hour workshop", "four-week blended course", "self-paced module"]
Required Content or Standards: [List mandatory topics, policies, standards, competencies, or curriculum requirements]
Assessment Expectations: [Describe required evidence, grading needs, or performance checks if already known]
Constraints: [Technology, class size, accessibility needs, time, facilitator availability, or resources]
Tone: [Preferred design tone, e.g. "clear, practical, learner-centred"]
###Input Validation
Review all inputs before generating the plan. If the desired results are broad, the learner context is unclear, the duration is unrealistic, or required content is missing, ask targeted clarification questions. Pause and wait for clarification before producing the final plan.
###Instructions
Begin by translating the desired results into a small set of measurable learning outcomes. Keep outcomes focused on what learners will be able to do, explain, create, decide, or demonstrate.
Define acceptable evidence before designing activities. For each outcome, specify the best evidence of learning, including performance tasks, checks for understanding, reflection, discussion, quiz items, demonstrations, or applied products.
Distinguish essential understanding from useful background knowledge. Do not overload the plan with content simply because it is related to the topic.
Design learning experiences that prepare learners for the evidence tasks. Sequence activities from orientation and modelling to guided practice, feedback, independent application, and consolidation.
Include realistic pacing for the stated duration. If the requested scope is too large, identify what should be reduced, moved to pre-work, or placed in follow-up support.
Build in learner support, feedback moments, and opportunities to correct misconceptions before final assessment.
Ensure every activity has a clear reason for being included. Avoid generic lectures, discussions, or quizzes unless they directly support the desired results.
Make practical assumptions explicit and flag any design risks that depend on missing information.
###Output
Course Purpose: concise statement of the learning need.
Desired Results: measurable outcomes and essential understandings.
Evidence Plan: outcome, evidence type, assessment method, success criteria.
Learning Experience Sequence: stage-by-stage plan with timing, activity, learner action, facilitator role, and rationale.
Content Prioritisation: must-include, optional, and remove/defer.
Feedback and Support Plan: where learners receive guidance and correction.
Risks and Adjustments: scope, timing, prerequisite, or assessment concerns.
Final Design Snapshot: a concise summary ready for stakeholder review.
Include one alternative assessment option for each outcome in case the original assessment is not feasible.
This course addresses the critical transition of individual software engineers into technical team lead roles. New leads frequently struggle with the shift from executing code to scoping projects, resulting in inaccurate timelines, developer burnout, and missed product shipping milestones. This blueprint establishes a practical, backward-designed curriculum to build core engineering estimation and project-scoping capabilities.
By the end of this module, learners will be able to:
| Target Outcome | Evidence Type | Assessment Method | Success Criteria |
|---|---|---|---|
| LO 1: Deconstruct Features | Applied Project Artifact | Evaluation of a submitted Work Breakdown Structure (WBS) document. | Every sub-task must represent less than 16 hours of independent engineering execution time. |
| LO 2: Formulate Estimations | Quantitative Calculation | Review of a completed project estimation matrix spreadsheet. | Estimates must accurately apply standard deviation weights for optimistic, pessimistic, and likely outcomes. |
| LO 3: Defend Constraints | Interactive Performance Task | Live, 10-minute negotiation roleplay with a simulated Product Manager persona. | Learner correctly identifies at least two resource dependencies and suggests a viable alternative path. |
Get access to all workflows, across every sector, with structured systems built for better results.