Trainers, Educators, Instructional Designers, Coaches, Assessors
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 designing scenario-based assessment questions.
### Required Input
- Topic: [e.g. "Customer service conflict"]
- Learning Objectives: [e.g. "Handle complaints professionally"]
- Audience Level: [e.g. entry-level staff]
- Number of Scenarios: [e.g. 3]
- Context Setting: [e.g. "Retail store", "Call centre"]
- Desired Skills: [e.g. communication, decision-making, problem-solving]
### Input Validation
Review all inputs carefully.
If context is too generic (e.g. "business"), ask for specificity.
If skills are unclear, request concrete behaviours.
Pause until all inputs are clear and actionable.
### Instructions
For each scenario:
- Build a realistic, detailed situation (who, where, what problem)
- Include constraints or tension (time pressure, conflicting priorities)
- Avoid obvious or overly simple situations
Then create 1-3 questions per scenario that:
- Require decision-making or judgement
- Force the learner to apply knowledge, not recall
- Avoid leading or giving away the correct answer
Ensure variation across scenarios (different problems, stakes, perspectives).
Align each scenario with at least one learning objective.
Ensure language matches audience level.
### Output
Provide:
1. Scenario description (clear and concise)
2. Questions per scenario
3. Key evaluation points (what a strong response should demonstrate)
4. Skills mapping per scenario
Increase difficulty by introducing incomplete information or conflicting goals.
Instructions: Read the following workplace scenarios. Provide a written response (200-300 words) for each, detailing your exact approach and the logic behind your communication strategy.
It is 4:45 PM on a Friday. Your Lead Developer, who is critical for Monday’s product launch, has just been pulled by the CTO to fix a critical security patch for a different department. You have no remaining buffer in your timeline, and your team is already hitting burnout levels.
A backend migration has failed, meaning the new user dashboard will be delayed by 48 hours. You must explain this to the Marketing Director, who has already spent $50,000 on “Launch Day” ad spend starting tomorrow morning. They do not understand API latencies or database sharding; they only see the lost revenue.
A strong response for Scenario 1 should demonstrate negotiation skills by acknowledging the CTO’s priority while presenting the impact on the launch’s ROI. For Scenario 2, the candidate must avoid jargon and focus on “Business Impact” and “Mitigation” rather than technical excuses.
[…]
Get access to all workflows, across every sector, with structured systems built for better results.