Future Solutions

Act as a futurist who uses data from Jobs-to-be-Done research to inform your thinking. You primary tenet is that disruptive solutions always get more of the job done on a single platform, and do so with fewer visible features. You also know that a current solution only gets part of the job done, which means people currently have to cobble solutions together to get the entire job done. Those solutions could be a combination of products, services and/or do-it-yourself.

Before I begin my example, please read this blog post: https://www.zdnet.com/article/the-crm-industry-a-new-science-for-customer-experience/

Decades ago people listened to music just like the do today. However, the solutions were complicated and only addressed a single context or situation. For example, many people purchase, installed, and configured component stereo systems in their home. That would have to source each component separately. They would also need to source the music, e.g., vinyl albums, cassettes, etc. They would have to determine how to store the music so it was easily accessible. If they wanted a custom playlist, they would need to record songs, song-by-song onto a cassette. And, they could only play the music in their home. If they wanted to go to the beach they needed an entirely different hardware setup.

Now let's consider the job map for "Listening to Music", it goes like this:

1. Identify the music that fits your mood
2. Gather the desired music
3. Organize the music
4. Make sure you're ready to listen
5. Listen to the music
6. Monitor the experience
7. Modify the music selection
8. Conclude listening to music
9. Share your experience

Component stereo systems could only manage step number 5. But over time, solutions emerged that got more of job done, and in more contexts and situations as well. For example, the iPod helped to gather the music and organize the music. It allowed you to listen to music and also modify the music selection. It got more of the job done on a single platform.

Fast forward in time to the present day, streaming music platforms get the entire job done, and they run on a multitude of devices. Those devices actually enable many jobs to done as well. As you look a streaming service, they have far fewer features than a component stereo system. What makes this possible is a new infrastructure that is essentially invisible, e.g., the internet, remote servers, artificial intelligence, etc. The user simply hits a button and the magic happens. None of the products that were used in the past are currently needed to listen to music, so they are absolutely replaced and industries are disrupted.

Now, here's what I'd like you to do. I want you to consider a(n) [product]. Also consider how it is used when {{end user}} are {{job}}. I'd like for you to envision a future solution that gets the entire job done, and it does so completely differently than before. The new solution has far fewer features than the {{product}}, it requires far fewer integrations with other products, less coordination between it and other products, processes and people, while also addressing more contexts, use cases and situations for end {{end user}}s. Make sure you consider the job map and how it gets every step done and how it makes things we used to see invisible though automation or new kinds of infrastructure. The new solution will be unrecognizable when compared to prior solutions. If this new product or service needs infrastructure or technology that is yet to be developed, I want you to outline what those capabilities would need to be. Then generate a comprehensive business case for the product or service that you believe could get the entire job done faster, more accurately, and less expensively. Explain the benefits of the new solution. Include a summary of the concept in your case. This new product or service will also need a business model so use the categories from The Business Model Canvas to organize that information. Please use bullets within the business model categories for readability.

Address each phase of the job map:

1. Define: in the define phase, we want to know what aspects of getting the job done need to be defined, planned, or assessed by the {{end user}} upfront in order to proceed. 2. Locate: in the locate phase, we want to know what items - tangible or intangible - must be located, gathered, collected, accessed, or retrieved by the {end user}} to do the job. 3. Prepare: in the prepare phase, we want to know how the {{end user}} must prepare or integrate the inputs, or the environment(s), from the Locate step to do the job. 4. Confirm: in the confirm phase, we want to know what the {{end user}} must verify, prioritize, or decide before doing the job in order to be successful. 5. Execute: in the execute phase, we want to know what the {{end user}} must do to execute the job successfully. 6. Monitor: in the monitor phase, we want to know what the {{end user}} must monitor in order to ensure the job is executed successfully. 7. Resolve: in the resolve phase, we want to know what problem the {{end user}} might need to troubleshoot, restore, or fix for the job to be completed successfully. 8. Modify: in the modify phase, we want to know what the {{end user}} might need to alter, adjust, or modify for the job to completed successfully. 9. Conclude: in the conclude phase, we want to know what the {{end user}} must do to finish the job.

The map provided will not be broken down into phases, but do your best to associate the steps provided into the appropriate phase. Explain how each phase will be improved, or automated away into obscurity

Always output in markdown

Product: Job: End User: Job Map: