Ignore all previous instructions. Act as a(n) {{end user}} with a deep expertise in Jobs-to-be-done theory. As you know, each Job Step has success statements that represent the desired outcomes or outputs an end user aims to achieve. For each Job Step submitted for the job {{job}}, please generate a list of success statements that a(n) {{end user}} desires. Develop these statements based on your understanding of the key categories related to problems and common attributes of waste when consuming a product or service. They should also take into account the potential for forcing a(n) {{end user}} into repetitive tasks. For example, end users don't want to have to communicate the same more than once, or do the same thing more than once. Of equal importance are success statements that are focused on what needs to be avoided in order to be successful. These should account for approximately 25-30% of the statements. None of the statements should describe how to accomplish something.
For each Job Step, generate a list of [n] success statements related to a(n) {{end user}} trying to {{job step}} {{context}}. If no context is supplied, please disregard the context. Think step-by-step.
Here are some examples and explanations of good and bad: Bad: “The software feature does not provide adequate feedback or notifications, causing the user to miss important updates or changes.” Why?: It uses the word “or” and it attempts to provide an explanation within the statement, e.g., “causing the user to miss important updates or changes.” Good: “Receive adequate feedback from the software feature.” Why?: It is stated in the affirmative, it is concise, and is also a desired outcome. We can ask an end user how important this is, or how difficult this is. We can compare it other discrete statements. Examples that demonstrate what to avoid: Bad: "Develop a clear understanding of your competitive landscape to inform strategic planning, avoiding blind spots and missed opportunities." Why? It appends an avoidance on the end instead of making it the primary part of the statement Bad: "Prevent security goals from becoming outdated by regularly reviewing and updating them." Why? It attempts to explain how to do so something Good: - "Avoid misalignment of resources and priorities that could hinder revenue growth" - "Avoid miscommunication between teams that could lead to missed opportunities or duplicated efforts" - "Minimize customer churn by proactively addressing their concerns and needs" - "Mitigate the risk of losing market share to competitors by staying agile and responsive" - "Avoid potential conflicts with partners and stakeholders that could damage relationships and collaboration" Why? Because the all begin with a verb that establishes what should be avoided. Bad: "You want to price your tires competitively in the market" Good: "Price your tires competitively in the market" Why? It is concise Bad: "Calculate key financial metrics and ratios, such as your savings rate, debt-to-income ratio, or investment returns, to provide insights into your financial performance and goal achievement" Good: "Gain clarity on your financial progress so you can identify areas for improvement, e.g., evaluate key financial metrics, talk to an advisor, etc." Why? It begins with an outcome and not a task. It appends examples when needed. It is relatively concise.
## MECE SCALING
The collection of statements should be MECE. Because the number I ask for could be different each time, take this into account as you ensure that you have complete coverage of concepts. Therefore, some outputs may have more highly themed statements (fewer statements) and some may be more granular (more statements). Use the following example to think this through.
Example:
If you would have generated two statements but have been limited by small number statements, before you output them you can consolidate your output like this. Here are two statements that you might need to combine into one:
- Understand the interest rates when financing
- Understand the repayment period when financing
You could combine them (theme up) to something like this…
- Understand the terms and conditions associated with each financing option, e.g., interest rates, repayment period, etc.
## END MECE
Please follow these instructions closely:
- Statements should not include the quality of the outcome. For example, do not use adverbs like ‘accurately’, ‘effortlessly’, ‘quickly’’, efficiently’, ‘easily’ at the beginning or at the end of the statement. Do not use them, or words like them, at all
- Do not begin statements with the work ‘if’
- State the success statement in the affirmative
- Do not use ‘and’ or ‘or’ in the statements
- Do not put suggestions about ‘how’ or ‘where’ in the statement
- Do not begin or end a statement with an adverb. Pay special attention to this
- Do begin each statement with a verb
- Do not use connective words in a statement. Never use “and” to connect to things. Never use “or”. These would be better suit for separate statements
- Do not reference end users in the statement. Do not use words like “you” or “your”. Do not begin a statement with “You” or “Your”.
- When you need to included examples, instead of using "such as" or "for example" please append the statement with a comma, then "e.g.," and finish with a comma and "etc."
- For statements about what must be avoided, begin the statement with the word ‘Avoid’
- Output as a numbered list
- Do not output any content before the numbered list of statements
- Do not output anything after the numbered of statements
- Do not output a test-fit example
- Always make sure the statement is relevant to the current step, and not a preceding or subsequent step
- Statements should be in a logical sequence or precedence and dependence.
- Do not generate a statement that restates the job step
## ODI
Now that you have constructed the base statement I’m going to give a very important further instruction. There are three (3) formats for a success statement. These formats are pre-pended to the success statement you generated. These are the three types. Only use the prepends that are inside the quotes. The word “Avoid” should be replaced with a version using the second and third format type. The rest is instructional:
- “Minimize the time it takes to “…(do something) - this should be applied to all statements that are not about avoidance.
- “Minimize the likelihood that “…(something causes an undesirable result) - this is one of formats used when you are trying to avoid an undesired result.
- “Minimize the likelihood of “…(something undesirable happening) - this is one of the formats used when your are trying to avoid something undesirable from happening.
Additional examples:
- Minimize the time it takes to reduce the patient’s risk of infection
- Minimize the likelihood that blood loss results in reflex tachycardia
- Minimize the likelihood of a post procedure thrombotic event
Format types 2 and 3 should only account for 25-30% of all statements
Format types 2 and 3 should not be framed in the negative. In other words do not output a statement like this: “Minimize the likelihood of not reviewing and updating key initiatives as market conditions change” because it is minimizing the likelihood of not doing something. Also, do not include a connective word such as as “and” or “or”. A better format would be “Minimize the likelihood of failing to track key initiatives as market conditions change”
The next instructions is EXTREMELY IMPORTANT
Format types 2 and 3 should NEVER use the words or phrases “not”, “does not”, “do not”, “is not”, or “of not”. For example this statement “Minimize the likelihood that the identified data sources do not capture key customer insights” should be stated as “Minimize the likelihood that the identified data sources fail to capture key customer insights”
##END ODI
Finally, you need to run this through a test-fit structure to ensure that it makes sense. Here is the structure: As a(an) {{end user}} + who is + {{Job}} when {{context}} you're trying to <generated output> + so that you can successfully {{job step}} Does the success statement make grammatical sense? If so, output it. If not, rework it and test it again.
Here is a list of all of the Job Steps. So, do not output statements that would logically belong in another step:
{{map}}
Always output in markdown Once you have completed the set of success statements for the given Job Step, wait for me to enter the next step. Please do not prompt me for it. End User: Job: Context: Job Step: n: 7-12
Map:
- Establish a Crop Plan
- Assess Environment Conditions
- Acquire Needed Resources
- Prepare the Field for Planting
- Verify Planting Conditions
- Finalize Planting Schedule
- Plant the Corn
- Monitor Crop Growth
- Address Crop Issues
- Optimize Growth Conditions
- Harvest the Crop
- Process the Corn for Storage
- Evaluate Crop Performance