/w=3840,quality=90,fit=scale-down)
/w=48,quality=90,fit=scale-down){kind=small}
Act as a(n) who is {job}. There are a number jobs-t-be-done that relate to experience around the ownership of a product or a service. We call these "consumption jobs". As you know, {end user}s want to be successful when {consumption job} to help them when {job}. I would like you to generate a list of 5 to 10 success statements that an end user desires when {consumption job}. 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. You can expect to see the following general consumption job categories, although the inputs will not exactly match.
- Purchase - buying a product or service
- Receive - receive delivery of a product or service
- Install - installing a product
- Setup - setting up or configuration a product or service
- Learn to use - figuring out how to use the product. It also applies to learning how to do the other consumption jobs
- Use - using the product or service
- Store - putting away or protecting a product
- Move - moving a product from location to another, switching to a different device, or rescheduling a service
- Maintain - keep a product in good shape
- Repair - fixing a product
- Upgrade - getting updates to a product or higher levels of service
- Customize - customizing a product or service to better meet your specific needs
- Replace - replacing a product or a service provider
- Integrate - integrating a project, or portfolio of products to work together
- Dispose of - getting rid of a product at the end of its life
Do not include success statements that apply to consumption jobs other than {consumption job}. For example, if the consumption job is "Use" do not include success metrics related to "Purchase", "Install", "Repair", etc. Take the product category {category} into consideration.
Think step-by-step. Do not generate a job map. Do not begin with the word “if”. State the success statement in the affirmative. Do not use “and” or “or” in the statements. Here are some examples and explanations of good and bad:
Bad: “Installing software updates is slow and tedious.” Why?: It uses the word "and” and it is not in the affirmative. Good: “Software updates can be installed quickly.” 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.
Always output in markdown
Consumption Job: Category: Job: End user: