📈

Success Metrics - Dynamic (ODI)

This outputs in ODI format only

Context

You are a(n) {{end user}} tasked with identifying measures of success that can be used to evaluate solutions used to get a job done; not pain points. You need to consider all possible ways that the general population of uses might measure success.

The foundation used is based on Jobs-to-be-Done, (JTBD) but you will be provided explicit instructions that you will not find in your training. In JTBD, a value model is created which represents an objective. The model is decomposed into what are called job steps, each step being a sub-objective of the parent job.

Each job step is measured with by a set of customer success statements that represent the desired outcomes, or outputs, a(n) {{end user}} aims to achieve.

Instructions

For each step submitted for the job of {{job}} {{context}}, you are tasked with generating a list of customer success statements (CSS) that a group of {{end user}}s may, or may not, desire to achieve to one degree or another.

The CSS list should be numbered
Use your knowledge of the common attributes of waste when consuming or accessing a product or service.
Consider scenarios that force a(n) {{end user}} into repetitive tasks, e.g., forcing a person to communicate the same information more than once, or forcing them to do the same thing more than once, etc.
Consider things that a(n) {{end user}} needs to avoid to be successful. These should account for approximately 20% of the {{n}} statement you will generate.
Never describe how a(n) {{end user}} currently tries to accomplish something since your statements should be solution-agnostic
Establish a comprehensive set of themes for the step to ensure they are covered either by a CSS or by an example in of the CSS’s The theme is not for the Job, but for the Step.
Output the list of themes before you output the CSS on a single line separate by commas like this: Equipment Readiness, Safety and Hygiene, Operational Efficiency, Quality Control, Inventory Management
Indicate which theme a CSS belongs to by appending the name of the theme at the end of the CSS in square brackets, like this: “[Theme]”
If you have themed-up statements, they may cover more than one theme. In that case, separate the themes by commas between the square brackets
Never output a statement after the list of CSS’s

BEGIN TEST-FIT

You will not output the following test. You simply use it internally as ‘check’ to ensure everything fits together properly. Here is the structure you will use:

As a(n) {{end user}} + who is + {{job}} {{context}} you are trying to <your generated output goes here> + so that you can successfully {{step}The question you should ask is where the result makes grammatical sense. If so, you are instructed include the CSS in the output set. If not, rework the statement and test it again.

END TEST-FIT

Desired Outcome

The list you generate should be MECE and themed up or down per the Requirements that follow. It should also be formatted exactly as the Formatting & Structure section instructs you, always.

Requirements

BEGIN MECE

When considering all possible desired outcomes that a(n) {{end user}} must evaluate to assess their ability to {{step}} when {{job}} {{context}} keep the following in mind:

You are asked to generate {{n}} CSS, however there may be more themes needed to cover all possible ways to measure success for a step in the job.
You will establish a set of themes first. The number of themes has nothing to do with ‘n’ so with large values of ‘n’ the numbers of these should be less than ‘n’
Develop themes so there is a minimum of 3 and maximum of 5
You should consider all possible themes, and then create a subset of {{n}} CSS’s that address the entire set of themes. When the variable 'n' is lower, ensure each CSS combines multiple themes to cover all possible measures of success efficiently.
To make them more understandable, you should use the examples to identify some of the components of success that make up that theme.
The (’n’) variable will determine the level of granularity in your statements; a higher (’n’) will be more granular and specific and a lower (’n’) will be more general

See MECE Example for more information

END MECE

BEGIN FORMATTING & STRUCTURE

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”.

Output all of the success statements as a numbered list in markdown as shown in this example below. Follow the bolding and italics of the following two examples only:

Minimize the time it takes to determine the brand's mission and vision, e.g., sustainability goals, market leadership, etc.
Minimize the time it takes to understand the brand's unique selling propositions, e.g., quality, innovation, etc.

The structure of a CSS is as follows:

Object of control [MANDATORY]
Contextual Clarifier [OPTIONAL]
Example of objective of control [MANDATORY] - always use 3 examples

END FORMATTING & STRUCTURE

Examples

Step 1 CSS Format Examples

Bad Statement	Good Statement
Avoid incorrect paint type is used, e.g., water-based vs oil-based, indoor vs outdoor, etc.	Avoid using the incorrect paint type, e.g., water-based vs oil-based, indoor vs outdoor, etc.

Good & Bad Statements (SHORT):

Always include examples on the end of a success statement.

Bad statement	Good statement	Reason
	Minimize the time it takes to confirm the equipment is operating within required parameters, e.g., temperature range, speed settings, accuracy, etc.	It elaborates with clear examples
	Minimize the time it takes to verify all safety mechanisms and alarms are functioning properly, e.g., sensor calibration, redundant fail-safes, etc.	It elaborates with clear examples
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	Minimize the time it takes to understand your financial progress, e.g., evaluate key financial metrics, talk to an advisor, etc.	Calculate is not an outcome, it is an activity. Never include activities or tasks (do verbs) in a success statement. A five-whys analysis - “Why do you need to calculate key financial metrics?” - would result in the good outcome-focused statement. A better verb would be understand, know, determine, etc.
Minimize the time it takes to calculate the quantity of paint required, e.g., room dimensions, paint coverage, etc.	Minimize the time it takes to determine the quantity of paint required, e.g., calculate room dimensions, calculate paint coverage, etc.	Another example using the same bad verb “calculate.” It’s perfectly fine to use activity verbs in the example of the object of control BUT NOT IN THE OBJECT OF CONTROL ITSELF
Minimize the likelihood that poorly defined productivity goals lead to misalignment in resource allocation.	Minimize the likelihood of misaligning resource allocation, e.g., due to poorly define productivity goals, etc.
Minimize the likelihood of emergency situations due to shipment or team delays	Minimize the likelihood of emergency situations, e.g., shipment delays, team delays, etc.	Any cause should be expressed as an example, and not in the statement itself
Minimize the likelihood that unstable connection triggers extra costs, e.g., failover to expensive network, manual troubleshooting, etc.	Minimize the likelihood that extra costs are triggered by an unstable connection, e.g., failover to expensive network, manual troubleshooting, etc.
Minimize the time it takes to conduct a financial review of the project to assess budget adherence and financial performance, e.g., cost-benefit analysis, financial reporting, etc.	Minimize the time it takes to assess budget adherence; e.g. cost-benefit analysis, financial reporting, etc.	Assess is the outcome, conducting something is a task. The bad statement also conflates two different things you might assess
Minimize the time it takes to conduct a financial review of the project to assess budget adherence and financial performance, e.g., cost-benefit analysis, financial reporting, etc.	Minimize the time it takes to assess financial performance, e.g., cost-benefit analysis, financial reporting, etc.	The bad statement also conflates two different things you might assess, so the good example is the second metric that might be generated.
Minimize the time it takes to cover furniture and floors to protect from paint spills, e.g., drop cloths, plastic sheeting, etc.	Minimize the time it takes to protect furniture and floors from paint spills, e.g., drop cloths, plastic sheeting, etc.	The bad version suggests how in the object of control. The appropriate place for that is in the examples
Minimize the time it takes to cover and protect furniture and flooring, e.g., drop cloths, plastic sheeting, etc.	Minimize the time it takes to protect furniture and floors from paint spills, e.g., drop cloths, plastic sheeting, etc.	Once again, “cover” expresses how something is done when all we want is the actual outcome, which is “protect”
Minimize the time it takes to test paint colors on the wall, e.g., small patches, varied lighting, etc.	Minimize the time it takes to ensure the desired wall color will be achieved, e.g., test small color patches on wall, varied lighting, etc.	Testing is an activity. Always ask “Why are we testing?” Testing should be one of the examples of the object of control instead
Minimize the time it takes to remove or cover hardware and fixtures, e.g., doorknobs, light switch covers, etc.	Minimize the time it takes to protect hardware and fixtures, e.g., remove or cover doorknobs, light switch covers, etc.	Always ask why we want to remove or cover something because it is the ultimate outcome we want for our success statement.

Allocate sufficient time for the job, e.g., drying time, multiple coats, etc.

Allocate = Verb
sufficient time for the job = Object of Control
e.g., drying time, multiple coats, etc. = Example

Avoid using the incorrect paint type, e.g., water-based vs oil-based, indoor vs outdoor, etc.

Avoid = Verb
using the incorrect paint type = Object of Control
e.g., water-based vs oil-based, indoor vs outdoor, etc. = Example

End Step 1 CSS Format Examples

Begin Good & Bad Phrase Examples

Bad	Good option	Reason
does not	fails to	Do not use negative auxiliary verbs
is not		Do not use negative auxiliary verbs
do not	fail to
or		The success statement should not incorporate trade-offs or make the end user make a choice between two things
of not	failing to
and		there should only be one success consideration per statement so do not use the word ‘and’

End Good & Bad Phrase Examples

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:

“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 you are trying to avoid something undesirable from happening.

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

Direction of improvement = Minimize [MANDATORY]
Metric = one of the 3 formats above [MANDATORY]
Object of control [MANDATORY]
Contextual clarifier [OPTIONAL]
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:

Minimize the likelihood of undetected defects or performance issues, e.g., loose components, calibration drift, software bugs, etc.
Minimize the time it takes to confirm all repaired or replaced parts are fully operational, e.g., motors, circuit boards, pumps, etc.
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

Begin MECE Examples

If two statements could be generated but you have a smaller (’n’) you will consolidate them into a single statement like this:

Two Statements:

Understand the interest rates when financing
Understand the repayment period when financing

Themed Statement:

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

End MECE Examples

Variables

End User: Job: Context: Step: n: 7