Skip to content

Projects

A project is the container for one initiative: backlog, sprint cadence, board, calendar, and reports. Most teams create one project per major product surface rather than one giant project for everything.

/projects/new is a chooser, not a single wizard. Four cards: Start from an idea (Idea Lab), Plan with AI (Architect), Bring a shipping product, or Empty project. You can switch back to All create options from any mode.

Projects are also the access boundary for day-to-day execution. Org members need project access before they can see its board or tasks.

  • Create a project from Idea Lab, AI Architect, existing product, or a blank shell.
  • Review the project overview: tasks, board, sprint, calendar, reports, settings.
  • Invite collaborators from the organization to a specific project.
  • Archive a project once the initiative winds down.
  • Switch between projects from the Projects list.
  • Starting any initiative that needs its own backlog slice and sprint cadence.
  • Separating unrelated workstreams so boards stay readable.
  • Onboarding a new team or client engagement into GrowthOS.
  • A signed-in member account with product access.
  • A Planner seat to create a project; Members need project access to see its board or tasks.
  • Sidebar: Projects
  • Direct routes: /projects (list), /projects/new (create)
  1. Open Projects (/projects) to see the existing portfolio.
  2. Click New project (/projects/new) and pick Idea Lab, Architect, Bring product, or blank.
  3. Review the generated project overview and adjust the name, description, or dates.
  4. Open the tabs you need: tasks, board, sprint, calendar, reports, settings.
  5. Invite collaborators from org members who should have access to this project.
  6. Start planning inside the project with Idea Lab, PRD Studio, or the backlog.
  7. Archive the project or adjust settings once the initiative ends.
  • The project overview shows an accurate name, description, and current sprint status.
  • Everyone who needs to work in the project can see its board and tasks.
  • You can find the right project from the list without asking a teammate.
  • One project per major product surface keeps boards readable and reports meaningful.
  • Use the chooser even when you already know the structure; you can edit anything after create.
  • Archive rather than delete finished projects so their history stays available for reporting.
  • Creating one giant project for the whole company, which makes the board and backlog unmanageable.
  • Forgetting to grant project access to a new hire even though they were added to the organization.
  • Deleting instead of archiving a finished project, losing historical reporting data.