Skip to content

Setup flow

Goals: outcomes that fill in by themselves

Goals are the outcomes your team is after by a date: a launch, a number of
customers, a reply time. Each goal has one owner, and its progress fills in by
itself from what serves it, so nobody has to type a percentage. Check-ins say
where it stands, drafted for the owner from that same work.

Opening goals

Open Projects and choose Goals, next to Table, Timeline and Workload, or
press Ctrl/⌘ K and choose Go to Goals. Goals are listed with their
sub-goals under them. Switch between Open and Closed, and between
Everyone's and Mine.

Each row shows:

  • Progress, as a bar with a small tick where the goal would be by now if it
    moved evenly from its start to its due date. Behind the tick is behind.
  • The owner, and when the goal is due, in red once the date has passed.
  • Its last check-in: on track, at risk, off track or on hold. "Check-in
    due" means the last one is two weeks old.

Making a goal

Choose New goal and give it:

  • A title, an owner (anyone in the workspace) and a due date, which
    is the end of the current quarter unless you change it. A start date is
    optional: without one, the goal's time counts from the day it was made.
  • Where its progress comes from:
    • Its projects: how much of the work in the projects serving it is done.
      Each project counts the same, whatever its size, so a goal served by one
      project that's 75% done and one that's 25% done is at 50%. A project with
      no tasks yet, or an archived one, doesn't count.
    • Its sub-goals: the average of the goals under it. A dropped sub-goal
      doesn't count; one closed as achieved or missed counts where it ended.
    • A number: where it starts, its target and where it is now, with a unit
      such as teams, $, hours or %. The target can be below the start: "cut the
      first reply from 6 hours to 2" counts down.
  • Optionally, the goal it sits under. Goals nest up to four levels deep: a
    company's, a department's, a team's, a person's.
  • Optionally, why it matters, in a few lines.

You can add the projects serving it as you make it, or later from its page.
Only projects you're in are offered.

A goal's page

The page shows the goal's progress and how far ahead of or behind its time it
is, then what serves it:

  • Projects serving it, each with how much of its work is done, what's
    overdue, and where its last project update said it
    stood. Projects you aren't in still count towards the goal, but aren't named
    to you: the page says how many there are.
  • Sub-goals, each with its owner, progress and last check-in.
  • Check-ins, newest first.

A project's page names the goal it serves, beside its health, and links to it.

Checking in

Choose Check in. The note opens already drafted: how far the goal moved
since the last check-in, how much of its time has passed, how much of the work
in its projects is done and what's overdue, and a line for each sub-goal. The
draft sums the projects up without naming them, because everyone in the
workspace reads check-ins and a project's name belongs to its people; name them
yourself if you like. The health is suggested from the goal's pace: within ten
points of where it should be by now is on track, within twenty-five is at risk,
and further behind is off track. Change anything before you post.

  • For a number goal, set where the number is now, and the progress follows.
  • Also post in a channel puts the check-in in a channel as well, with a
    link back to the goal.
  • On the AI edition, Add an AI summary writes two or three sentences on top
    of the facts, using only the facts.
  • Moving a goal under another, or out from under it, takes the right to change
    that other goal too: it changes its progress.

Closing a goal

In a check-in, choose Achieved, Missed or Dropped after "or close
it", add a closing note if you like, and choose Close the goal. A closed
goal keeps the progress it ended at and moves to Closed. If it closed too
early, choose Reopen the goal from its menu.

Who can do what

  • Everyone in the workspace sees every goal. Guests and clients never do.
  • A goal's owner, whoever made it, and workspace admins edit it, add
    and remove its projects and sub-goals, check in, close it and delete it.
  • A check-in's author can edit it. They and the goal's editors can delete it.
  • Deleting a goal deletes its check-ins. Its projects stay as they are, and its
    sub-goals move up to its parent.

Good to know

  • Goals are in every edition, the free one included, from OneCamp v2.59.0
    (with AI) and v1.44.0 (without AI).
  • Days are counted in your own time zone.
  • Up to 20 projects can serve one goal.