Grapefruits · Projects
A project is clearer when you can see what surrounds it.
A Grapefruit is a project: a defined body of work intended to reach an outcome. It lives inside a Grove, so the project remains connected to the larger area or responsibility it serves.
Separate temporary projects from enduring areas
“Run the business” is an ongoing responsibility. “Launch the autumn collection” is a project within it.
Pamplemousse keeps that distinction explicit. The Grove remains stable while Grapefruits begin, develop, and eventually move into the past. This makes it easier to see both the current work and the responsibility that continues after delivery.
Divide complexity into useful phases
Segments let you divide a Grapefruit into phases such as Discovery, Design, Delivery, and Review. Each Segment can hold the Seeds required for that stage of the project.
Segments are there to make a project easier to understand, not to impose process for its own sake. A straightforward project may need only a Grapefruit and a few Seeds. They are optional phases — not milestones, automated stage gates, or dependencies.
Keep the working context attached
Project decisions often live in one place, files in another, and stakeholders in a third. Pamplemousse lets related context remain connected to the Grapefruit.
Attach Pulp for notes, documents, and links. Connect Branches for people involved in the outcome. Organize Seeds beneath the relevant project or Segment, so the action list retains its meaning.
See progress without losing the details
Project views connect the outcome to its phases and actions. Filters can narrow reporting by Grove or Grapefruit, while search can locate work across the hierarchy.
When individual Seeds are completed, they move to Harvest without erasing the record of what contributed to the project.
Illustrative example
Launch a new website
- Grove: Brand and Communications
- Grapefruit: Launch the new company website
- Segments: Strategy, Content, Build, Quality assurance, Launch
- Seed: Approve homepage copy
- Sprouts: Review positioning, verify product claims, collect legal approval
- Branches: Designer, developer, legal reviewer
- Pulp: Sitemap, content brief, design files, launch checklist
The project has a clear outcome, but each phase, action, person, and source document remains connected to it.
Progress and reporting reflect recorded Seed status and other workspace data. They should not be treated as independent verification of delivery, and search covers supported Pamplemousse fields rather than the contents of every linked file or external service.
Bring your next project into focus.
Request access to the private beta. Features and project views may change while Pamplemousse is in beta.