For Unformatted Output

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.

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’s
The themes will be outputted as a column in the same row as the CSS in a table structure that is explained in the “Final Output Format” section near the end
If you have themed-up statements, they may cover more than one theme. In that case, separate the themes with a comma within the same row of the output table, in the column indicated in the “Final Output Format”
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 than {{n}} 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 5 and maximum of 7
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 than the number of themes, ensure each CSS combines multiple themes to cover all possible measures of success efficiently.
To make them more understandable, you should use the examples on the end of the CSS 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
A theme should be no more than two words with possibly a third connective word such as ‘and’, e.g., security and compliance, etc.

See MECE Example for more information

END MECE

BEGIN FORMATTING & STRUCTURE

You will follow a 1-step formatting process.

Step 1:

CSS must not include the quality of the outcome. For example, never use adverbs like ‘accurately’, ‘effortlessly’, ‘quickly’, ‘efficiently’, ‘regularly’, or ‘easily’ anywhere within the CSS. Do not use them, or words like them, at all.
Do not being statements with the word ‘if’.
CSS should be stated in the affirmative.
Do not use the connective words ‘and’ or ‘or’ in a CSS. When faced with these, you should create a separate CSS.
Do not introduce suggestions about ‘how’ or ‘where’ in a CSS.
Do not begin or end a CSS with an adverb.
Begin each CSS with a verb
Use verbs that reflect the ultimate outcome
Do not use verbs that could be mis-interpreted what action could be taken to address the ultimate outcome
Never use verbs that describe an activity or task as the object of control. Examples of these are ‘schedule’, ‘calculate’, ‘cover’, ‘test’, etc. The verbs you select should be related to the desired outcomes of a(n) {{end user}} when {{job}} {{context}}. You should not describe how they might try to each them. Use the 5-Whys model and think through this step-by-step
Do not reference users in the CSS. Do not use words like ‘you’ or ‘your’. As well, do not begin a CSS with ‘You’ or ‘Your’.
When you include examples, instead of using ‘such as’ or ‘for example’ instead append the statement with a comma, then ‘e.g.’ and finish with a comma and ‘etc.’
For CSS about what must be avoided, begin the statement with the word “Avoid.’
Use a single verb only in a CSS. Do not combine two or more verbs with ‘and’ or ‘or.’
The entire statement should be in plain text

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

See ‘Step 1 Format Examples’ for more information

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.

Bad statement	Good statement	Reason
	Confirm the equipment is operating within required parameters, e.g., temperature range, speed settings, accuracy, etc.	It elaborates with clear examples
	Verify all safety mechanisms are functioning properly, e.g., sensor calibration, redundant fail-safes, functioning alarms, 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	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.
Calculate the quantity of paint required, e.g., room dimensions, paint coverage, etc.	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.	Avoid misaligning resource allocation, e.g., due to poorly define productivity goals, etc.
Minimize the likelihood of emergency situations due to shipment or team delays	Avoid 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.	Avoid extra costs that are triggered by an unstable connection, e.g., failover to expensive network, manual troubleshooting, etc.	Always place what you are trying to avoid first
conduct a financial review of the project to assess budget adherence and financial performance, e.g., cost-benefit analysis, financial reporting, etc.	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.	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.	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.	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.	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.	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, not how we did it

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

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

Final Output Format

Output a list of themes before outputting the table

Wrap themes in square brackets and separate the bracketed themes with a comma. There should be no punctuation inside the brackets

The final output should produce content for a simple markdown table. The content within the table should be in plain text.

Always Output {{n}} CSS
Do not output any summaries or explanations after the table

This is the format to follow. Leave the Root Causes column blank:

CSS	Theme	Root Causes
Ensure high-quality service is provided, e.g., attention to detail, thoroughness, adherence to standards, etc.	[Theme 1], [Theme 2]