Opportunity and Solution is the first plan document of every initiative. It answers three questions: why the work matters, who it's for, and what the solution is. Everything you plan later builds on it.
Find the document
Open the initiative. In the sidebar, under Plan, click Opportunity and Solution.
What's in it
Section | What it covers |
Background & Business Need | Business context: the market or the business situation. Opportunity: what you stand to gain, such as revenue, retention, or saved time. Urgency: why now, and what happens if you wait. |
Target User Problems | The primary user, and their main problems, usually two or three. Each problem has a short name, how it shows up, and what it costs them. Then any secondary users and their main problem. |
Solution Summary | The approach, in a few paragraphs. It names the user problems it solves, and says how you'll know it worked. |
How Grove writes it with you
Grove researches. It looks up anything in your description that it isn't sure about, such as a term, a product, or a competitor.
Grove asks questions. It asks who the main user is, what hurts, and how this relates to other products. See Answer Grove's questions and explore options.
Grove checks what it understood. When it can say who the user is, what the pain is, and the shape of the solution, it sums them up for you. Say yes, or correct it.
Grove writes a draft. It writes all three sections together, because each one shapes the others. Then you improve the draft together.
Grove checks the draft. It checks that the document is specific, and that it matches your strategy. If the document doesn't match your Target Personas or another strategy document, Grove tells you. It doesn't fix the conflict by itself.
Grove doesn't need every answer before it writes. The first draft shows what is still missing.
Change the document
Edit it yourself. Click in the document and type. Your teammates see your changes as you make them.
Ask Grove. Tell Grove what changed, such as "Our main user is the pro, not the customer." Grove tells you what it plans to change and where, and waits for your OK. Then it changes only the parts that are affected.
Make it strong
Be specific. Write "cut the time to move a visit from 10 minutes to 1 minute," not "improve the experience."
Describe each problem fully. Say how the problem shows up and what it costs, not only its name.
Connect the solution to the problems. The Solution Summary should name the problems it solves.
Say how you'll measure success. For example: "Within three months, reschedule calls drop by half."
What doesn't go here
This document covers the problem and the shape of the solution only. The details belong in later documents:
Which projects to build, and what is out of scope, go in the Scope document.
How each feature behaves, such as rules, permissions, and screens, goes in each project's Requirements.
Next step
When the problem is clear, break the initiative into projects. See Break an initiative into projects.
Related articles
Break an initiative into projects
Edit documents with your team and Grove