Survey Version

• Act as a(n) {{end user}} with a deep expertise in Jobs-to-be-done theory.
• 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}}, 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 information more than once, or do the same thing more than once.
• Also consider statements that are focused on what needs to be avoided in order to be successful. These should only account for approximately 20% 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.

Good & Bad Statements (LONG):

Always include examples on the end of a success statement.

## 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:

1. Understand the interest rates when financing
2. Understand the repayment period when financing

You could combine them (theme up) to something like this…

1. Understand the terms and conditions associated with each financing option, e.g., interest rates, repayment period, etc.

The opposite is true when you have room for more statements.

## END MECE

Structure Rules:

• Statements should not include the quality of the outcome. For example, never use adverbs like ‘accurately’, ‘effortlessly’, ‘quickly’’, efficiently’, ‘easily’ anywhere in a success 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 use verbs that reflect that ultimate outcome
• Do not use verbs that could be interpreted as how to reach the ultimate outcome
• IMPORTANT: Never use verbs that are activities or tasks in the object of control. Examples: schedule, calculate, cover, test, etc. The verbs you select should be related to outcomes a(n) {{end user}} is trying to accomplish, not HOW they are trying to accomplish them. Think through the 5-Whys step-by-step.
• Do not use connective words in a statement. Never use “and” to connect to things. Never use “or”. These would be better suited 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 include 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’
• Always use a single verb. Do not combine two verbs with “and” or “or”.

Formatting Rules (Long):

• 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 of precedence and dependence.
• Do not generate a statement that restates the job step

ODI Rules

Now that you have constructed the base statement I’m going to give you a very important further instruction. There are three (3) formats for the final 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:

1. “Minimize the time it takes to “…(do something) - this should be applied to all statements that are not about avoidance.
2. “Minimize the likelihood that “…(something causes an undesirable result) - this is one of formats used when you are trying to avoid an undesired result.
3. “Minimize the likelihood of “…(something undesirable happening) - this is one of the formats used when you are trying to avoid something undesirable from happening.

The following defines the required structure. Always use this structure.

1. Direction of improvement = Minimize [MANDATORY]
2. Metric = one of the 3 formats above [MANDATORY]
3. Object of control [MANDATORY]
4. Contextual clarifier [OPTIONAL]
5. Example of object of control [MANDATORY] - but never use more than 3 examples

Example structure: Minimize + the time it takes to + verify the accuracy of a desired outcome + with a customer + , e.g., its meaning, its completeness, its exactness, etc. Finished example: Minimize the time it takes to verify the accuracy of a desired outcome with a customer, e.g., its meaning, its completeness, its exactness, etc.

Additional examples:

1. Minimize the likelihood of undetected defects or performance issues, e.g., loose components, calibration drift, software bugs, etc.
2. Minimize the time it takes to confirm all repaired or replaced parts are fully operational, e.g., motors, circuit boards, pumps, etc.
3. Minimize the time it takes to verify all initially reported problems have been fully resolved, e.g., error messages, abnormal readings, fault codes, etc.

Only use a maximum of three (3) examples of the object of control

Format types 2 and 3 should only account for about 20% of all statements. Also, prioritize “Minimize the time it takes to” statements over the “Minimize the likelihood…” 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 RULES

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.

Convert verbs in the job step to the gerund form. For example, if the job step begins with the word “Implement” you should use the gerund form of the verb, which is “implementing” when you output the job step.

===begin survey format===

Convert verbs in the step to the gerund form.

Please output the the first success statement in the following format. The direction of improvement and metric portions of the statement should be in bold. The object of control should be in italics. The contextual clarifier and example of object of control should be regular text. Do NOT number the statement. Please include rating row as row two. Always output in markdown code in a markdown code window

===end survey format===

Always output in markdown code in a markdown code window 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: 20