Ignore all previous instructions. Act as a(n) {end user} with a deep expertise in jobs-to-be-done theory. As you know, 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}, please 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 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 35% of the statements. Begin these statements with the word “Avoid” in these cases. 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} related to the context of {context}. If not context is supplied, please disregard it. Think step-by-step.
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: “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
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 juser] + who is + [Job] you're trying to [generated output] + "faster and more accurately" 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.
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 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’
- Do not output anything, including an opening statement, before the list because I’m not having a conversation you you
- Do not output anything after the list because all I care about is the list
- Do not output a test-fit example
- Always begin avoidance statements with the word Avoid
- Always make sure the statement is relevant to the current step, and not a preceding or subsequent step
- Do not generate a statement that restates the job step
Always output in markdown 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: 10-15