Act as an expert in Jobs-to-be-Done, specifically Outcome-Driven Innovation. You must synthesize the following desired outcome statements so that they are mutually exclusive and collectively exhaustive. There are likely statements that are stated differently, but basically mean the same thing. Either select one of them, or rewrite the statement reflect a synthesis. Use the format of the statements as your receive them. The Job-to-be-Done is {{Job}} and the person performing the job is a {{end user}}. These desired outcome statements are for the Job Step {{job step}}.
Here are the original instructions that created the statements. Please consider them carefully:
Here are some examples and explanations of good and bad: ##BEGIN 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.
Always output in markdown ##END
The final output should be between 7-12 statements, just like the original instruction. Here is the list to synthesize: {{list}}
End User:
Job:
Job Step:
List:
Minimize the time it takes to gather data on soil nutrient levels, e.g., nitrogen, phosphorus, potassium, etc. Minimize the time it takes to understand the pH level of the soil. Minimize the time it takes to identify the soil type, e.g., clay, sandy, loamy, etc. Minimize the likelihood of overlooking an impending significant weather event. Minimize the time it takes to determine local rainfall patterns. Minimize the time it takes to understand temperature patterns, e.g., average highs, lows, etc. Minimize the likelihood that inaccurate soil and weather data lead to poor crop yields. Minimize the likelihood of not accounting for future weather predictions in the planning process. Minimize the likelihood of failing to detect soil contaminants. Minimize the likelihood of ignoring extreme weather events, e.g., drought, frost, etc. Minimize the time it takes to decide the optimal time for planting based on soil and weather conditions. Minimize the likelihood of neglecting the effects of climate change on local weather patterns. Minimize the time it takes to gather information on local soil composition Minimize the time it takes to monitor the local weather patterns Minimize the likelihood of failing to identify local pests and diseases that might affect the crop Minimize the time it takes to assess local water availability, e.g., rainfall, irrigation systems, etc. Minimize the time it takes to evaluate local crop yield data Minimize the likelihood of overlooking relevant local agricultural regulations, e.g., usage of certain pesticides, crop rotation rules, etc. Minimize the likelihood of missing changes in local farming technology trends Minimize the time it takes to understand local market demands for corn crops Minimize the likelihood of failing to consider local labor availability and cost, e.g., for planting, maintenance, harvesting, etc. Minimize the likelihood of failing to keep abreast of local farming community's best practices.