BIGGER PROJECTS

Connect tasks to outcomes and cycles

Track an outcome and plan a bounded period of delivery.

Give an outcome an owner

A goal describes an outcome and its owner. Link relevant tasks so the work has a clear connection to the result you want.

Goal progress can be binary, weighted, or entered manually. Review the chosen method before comparing goals. A manually entered value and a calculated task rollup mean different things.

Plan a delivery cycle

Keep work in a backlog until you are ready to include it in a delivery cycle. Use a defined period and an intentional scope so the cycle represents a real commitment.

When tasks enter or leave a cycle, the scope changes. Cycle analytics keep that context visible so progress is not reduced to a percentage with an unexplained denominator.

Read progress in context

Check the included tasks, weighting, completion definition, and dates behind a result. Missing inputs can produce an unknown value.

Use Insights and reports to inspect the calculation and relevant task data before writing your own explanation of the project.

KEEP EXPLORING

Look across plans and report on progressUse plan sets, roadmaps, Insights, and saved reports with the right context.
Add fields that fit your workUse typed fields, numeric rollups, formulas, and conditional formatting.
Give a project its own planCreate a private plan, choose a setup, and organize the work inside it.

Need a hand with this?

Check common questionsGet support

Search the handbook

Search stays in this browser.esc to close