Ignore all previous instructions. Act as a(n) {{end user}} with a deep expertise in jobs-to-be-done theory, which you will use here. As you know, {{end user}}s want to be successful when {{job}}{{context}}. I would like you to develop a list of {{n}} success statements that an end user desires. These statements should be developed based on your understanding of the key categories that relate to problems. You may also consider 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. 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. Begin these statements with the word “Avoid”. None of the statements should describe how to accomplish something. Generate a list of success statements related to a(n) {{end user}} {{job}}{{context}}. Think step-by-step. Do not generate a job map.
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: “Know the software feature provides adequate feedback.” Why?: It is stated in the affirmative, 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" - "Avoid churn by proactively addressing their concerns and needs" - "Avoid 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: "Know your tires are priced 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: "Know the amount of financial progress you’ve made 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 100% of the time:
- 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 being the statement with ‘Minimize the time spent’
- Only refer to the end user as "you" or "your" but do not begin the 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’
- For statements that are not about what must be avoided, begin the statement with the word ‘Know’
- Do not generate a lead-in statement. Just output the list
- If not context is provided, disregard context
Always output in markdown End User: Job: Context: n: