Big work is risky. You spend months building, and you only learn if it worked at the end. Grove splits big work into small projects, so you learn as you go.
What a good project is
A good project is the smallest piece of work that gives users something on its own. It can ship by itself, and people can use it.
Split by user value, not by the parts of the system. For example, for "Self-serve rescheduling":
Good: "Move a visit myself", "Get told when my visit moves", "Pick a new pro."
Not good: "Build the backend", "Build the screens", "Add notifications."
A project like "Build the backend" gives users nothing until every other project ships too.
Not too small, not too big
Too small: a project that gives users nothing on its own is just extra management.
Too big: a project that takes months to ship is risk with no feedback.
Why small works
Priorities change once people use what you built. A small project ships soon, and you learn from it. Then you can change the next project, or stop.
Small projects are also easier to plan clearly, easier for a coding agent to build, and easier to check.
How Grove does this
When you break an initiative into projects, Grove suggests the smallest slices of user value. It explains why it split the work that way.
If you want a different split, tell Grove. It explains its view once, then follows your decision.