Job Map

Act as a(n) {{end user}} with a deep expertise in Jobs-to-be-Done theory, which you will use here. Set the temperature to {{temp}}. 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:

Do not assume a method or solution in any of these phases unless it is provided in the job or context inputs. For example, if the job is “Commuting to work” do not assume the commuter is using a personal vehicle. If the job is “Driving to a destination” then you can assume they are using a personal vehicle.

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.
1. Include anything that needs to be defined, planned or determined prior to performing any of the subsequent steps.
2. If I’m driving a car to a destination, I might need to determine where I am going, where I can park, assess traffic conditions, and/or determine the available route options
2. Locate: in the locate phase, we want to know what items or resources - tangible or intangible - must be located, gathered, collected, accessed, or retrieved by the {{end user}} to do the job.
1. Include anything that you might need access to and that you must take action in order to obtain it or them.
2. If I’m driving a car to a destination, I might need to locate my vehicle, find my drivers license, locate my glasses, etc.
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.
1. Include anything that might need attention or setup before executing the Job. The planning is done, and the necessary tangible or intangible resources have been obtain, but now the might need to be setup, or configured to work together
2. If I’m driving a car to a destination, I might need to inflate my tires to the proper pressure, or fill the gas tank to an adequate level, etc.
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.
1. Include anything that is critical to double check, or any final decisions that must be made
2. If I’m driving a car to a destination, I might need to select the best or fastest route, or verify that the car is in proper working order.
5. Execute: in the execute phase, we want to know the primary thing the {{end user}} must do to execute the job successfully.
1. Include anything that is core to getting the job done, and would otherwise leave a gap in the process.
2. If I’m driving a car to a destination, the logical step would be “Drive to the destination”
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.
1. Include anything that should be checked in real-time, or while the execute step(s) are happening, to determine if if something is going off track.
2. If I’m driving a car to a destination, I might want to monitor the fuel level, or my tire pressure, worsening traffic conditions, or emergency situations.
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.
1. When a risk is identified we want to resolve it before it becomes an issue. If an issue emerges, we need to resolve it in order to proceed
2. If I’m driving a car to a destination and I run low on fuel, I would want to find a gas station to fill my tank
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.
1. If I’m driving a car to a destination and traffic worsens, I may want to alter my route to one that has less car volume, or is moving at a faster pace.
9. Conclude: in the conclude phase, we want to know what the {{end user}} must do to finish the job.
1. If I’m driving a car to a destination, I may want to park my car, secure my belongings and/or make sure it’s still in good condition for the next drive.

The Job-to-be-Done for the {{end user}} is {{job}} {{context}}. Only consider the context if one is supplied, otherwise disregard it. Generate a list of job steps that consider each of the phases. There should be a minimum of one step per phase. However, there could be more than one.

Steps should be always begin with a verb. A bad step would be “Route Planning” and a good step would be “Plan the route.”

The job steps should be focused on what the {{end user}} is trying to accomplish faster, with better output, or better throughput when {{job}} {{context}}. Always ask WHY you are about to output a task. For example: Why would I “Conduct Customer Interview”? To learn what? An interview is a solution. The explanation should touch on the ‘why.’

Do not reference the phase in a job step unless absolutely necessary.

Fidelity

An ideal job map will have 10 to 18 steps. If {{fidelity}} = ‘low’ then the number of steps should be closer to 10. If {{fidelity}} = ‘med’ then the number of steps should be closer to 14. If {{fidelity}} = ‘high’ then the number of steps should be closer to 18.

Example:

• Low = 10 - 12 steps
• Med = 13 - 14 steps
• High = 15 - 18 steps

MECE

The job steps should be mutually exclusive and collectively exhaustive (MECE) and also must be in a logical order of precedence and dependence.

Think this through step-by-step.

Formatting

Output the result in JSON format. The sequence number, step name and the description should be separate nodes

Scoping

The following constraints are to be used to provide specific boundaries to the Job Map. Follow them carefully.

• The first step will generally be about {{start point}}. Give the step an appropriate name and format as previously described. Do not begin with anything that would logically precede this.
• The last step will generally be about {{end point}}. Give the step an appropriate name and format as previously described. Do not include any steps that come after this.

• Please follow all instructions carefully.

Reinforce Execution

There must ALWAYS be a step for the EXECUTE phase and it should reflect the core objective of {{job}} {{context}}.

• There could more than one step involved with execution.

EXAMPLE: if the Job is “driving to a destination in a car” then there should be a step like “Drive to the destination”

Test Fit

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}} {{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.

Final Instructions

It is EXTREMELY important that you follow these instructions closely:

1. Output as a single, ordered list in markdown format
2. Do not repeat the list
3. Do not generate an opening statement summarizing what your are about to output
4. Do not output anything after the single list
5. Do not use the word Manage as a verb for a job step, or any other word that does not have a discrete output
6. Do not use the phase name in the step name
7. Do not output a test-fit structure example

job: context: end user: start point: end point: fidelity: low | med | high temp: 0.1