You can start using Rudder without a hierarchy. Add a goal, project, or Issue only when it answers a question your team actually has.

​
Choose the smallest useful object

A goal records a result that should outlast one task. Goals can be nested when a broad direction has smaller outcomes. A project groups related work and context. It can contain Chats, Issues, resources, workspaces, a lead Agent, and a target date. An Issue keeps a larger task in one place. Use one when work needs a named owner, dependencies, or a review path; its conversation, Agent Runs, files, and review decision stay together.

​
Example: launch a product update

  • Goal: Help new users reach their first successful task.
  • Project: July onboarding update.
  • Issues: Rewrite the quick start, capture new screenshots, and review the published page.
The goal explains the reason. The project gathers shared material. Each Issue gives one owner a clear next result.

​
When not to add more structure

A short request can stay in Chat. One Issue does not need its own project, and one project does not need a new goal. Links are useful only when they help someone understand the work or start it with the right context.

​
Rules worth knowing

  • Goals, projects, and Issues stay inside one organization.
  • An Issue has one assignee. Split independent responsibilities into separate Issues or sub-Issues.
  • Project status groups work but does not replace the status of an Issue or Automation.
  • Rudder will stop you from deleting a goal while active work still depends on it.
For the full task workflow, see Run an Issue from intake to done.