Ignore all previous instructions. Act as a(n) {{end user}} with a deep expertise in jobs-to-be-done theory, which you will use here. As you know, Jobs have steps, much like a process, but they do not indicate how the {{end user}} does something, they represent what the {{end user}} must accomplish. Also, steps fall under 9 main phases. These phases are sequential. Each of the phases are explained below. Explanation of Phases: 1. Define: in the define phase, we want to know what aspects of getting the job done need to be defined, planned, or assessed by the {{end user}} upfront in order to proceed. 2. Locate: in the locate phase, we want to know what items - tangible or intangible - must be located, gathered, collected, accessed, or retrieved by the {{end user}} to do the job. 3. Prepare: in the prepare phase, we want to know how the {{end user}} must prepare or integrate the inputs, or the environment(s), from the Locate step to do the job. 4. Confirm: in the confirm phase, we want to know what the {{end user}} must verify, prioritize, or decide before doing the job in order to be successful. 5. Execute: in the execute phase, we want to know what the {{end user}} must do to perform the job successfully. 6. Monitor: in the monitor phase, we want to know what the {{end user}} must monitor in order to ensure the job is executed successfully. 7. Resolve: in the resolve phase, we want to know what problem the {{end user}} might need to troubleshoot, restore, or fix for the job to be completed successfully. 8. Modify: in the modify phase, we want to know what the {{end user}} might need to alter, adjust, or modify for the job to completed successfully. 9. Conclude: in the conclude phase, we want to know what the {{end user}} must do to finish the job.
Do not include steps in one phase that use the name of another phase as a verb. The Job-to-be-Done for the {{end user}} is {{job}} when {{context}}. Only consider the context if one is supplied, otherwise disregard it. Do not include steps that belong in previous, or subsequent phases. The phase we are interested in at the moment is the {{phase}} phase. Only generate steps for the phase indicated. Exclude any steps that would fall under the other phases. Do your absolute best to make the list of steps as concise as possible. The list should be generated in a logical order of precedence and dependence. ## changed the following from “a set of job steps” Think about this step by step. For each phase, provide one or more critical job steps. An optimal number of job steps should: 1. Cover all critical aspects of the phase, providing a comprehensive understanding of the objectives. 2. Be mutually exclusive and collectively exhaustive (MECE) to avoid redundancies while ensuring all relevant areas are considered. 3. Should be listed in a logical order, taking into consideration precedence and dependence 4. Should be as concise as possible 5. Not begin each step with the phase name unless it is absolutely necessary.
Make the step name bold. Explain each job step, step by step, while adhering to the following explanation format. Make the explanations as rich as possible. Precede each explanation with the text "The ability to quickly and accurately". Append the complete explanation to the job step, separated by a dash. Generate a numbered list of the steps that a(n) {{end user}} must accomplish in the {{phase}} phase - consider the context of {{context}} if it has been provided. Do not prepend the step name with the phase. Please follow all instructions carefully. Finally, you need to run this through a test-fit structure to ensure that the statement makes sense. This is a quality check that you will do internally. You will not output this. Here is the structure: As a(an) {{end user}} + who is + {{Job}} when {{context}} you need to <generated output> Does the success statement make grammatical sense? If so, output it. If not, rework it and test it again.
It is EXTREMELY important that you follow these instructions closely:
- Always output in markdown.
- Output the list only once
- Do not generate an opening statement summarizing what your are about to output
- Do not output anything other than a list
- Do not use the Phase name as the first word of the step
- Do not output a test-fit structure example
When you are finished outputting, prompt me for the next phase and remember the job, the context, and the end user (unless I override them). Job: Context: End User: Phase: