Goals

A goal is an outcome you are aiming at, with key results that say how you will know, and a progress figure that comes from the work rather than from someone's optimism. Goals are workspace-level, so one goal can draw on several projects.

Goals need the Pro plan. Guests do not see them at all.

What a goal holds

  • A name and a period, from a preset or your own start and target dates.
  • A parent, which is optional. A goal can sit under another one, so a team goal rolls into a company goal. The list has a tree view for reading them that way.
  • Owners. The person who creates a goal owns it unless they name someone else.
  • Key results, and links to real work.
  • A status: On track, At risk, Off track, Achieved, Missed or Cancelled. New goals start On track.

The list shows each goal with its status, progress, period, owners and the time since its last check-in.

Key results

A key result is a number you are moving. Each one has a starting value, a target, a current value and a unit, and is measured as a percentage, a plain number, a currency amount or a yes/no.

Progress on a key result is how far the current value has travelled from the start toward the target, capped at nothing below zero and nothing above a hundred. A yes/no key result is all or nothing: it counts fully once it reaches its target, and not at all before.

A key result whose target equals its start contributes nothing, because there is no distance to measure.

How progress is computed

A goal can compute its own progress, which is on by default. You can switch it off and set the figure by hand instead.

When it computes, every source counts equally:

  • All the key results together are one source, averaged among themselves. Ten key results do not outvote one linked project.
  • Each linked piece of work is another source: a project, a sprint, a module or a single task. Its contribution is its done tasks against its total, where done means completed or cancelled.

So a goal with key results and two linked projects has three sources, each worth a third. A goal with no sources at all sits at zero.

When it recomputes is worth knowing. It recomputes when you change a key result, add or remove a link, turn auto-compute on, post a check-in, or open the goal itself. It does not recompute when a task changes state, and the list page does not recompute as you read it. So the figure on the list can lag behind the work, and opening the goal brings it up to date. A daily job keeps the history moving even if nobody visits.

Check-ins

Check in records where a goal stands in words: a note, optionally a status change, and optionally a progress figure when you are setting progress by hand.

The note is the part that matters. A progress bar tells you the number moved; it does not tell you that the number moved because a dependency landed early, which is what the next person reading needs.

Check-ins are kept as the goal's history. Deleting a goal deletes them with it, which the confirmation says plainly.

When a goal goes quiet

A goal nobody has checked in on is the normal failure mode, so Ithura surfaces it in two places:

  • Home lists goals that have gone more than a week without a check-in, so it is in front of you when you start the day.
  • The goal's own row and page mark the gap, more insistently as it grows: one shade at a fortnight, another at a month.

Nobody is emailed and no notification is sent. It is a visible nudge where you already look, not an alert. Archived goals, and goals that are already Achieved, Missed or Cancelled, are left out of it.

Who can do what

ActionNeeds
Read goalsAny workspace member. Guests cannot see them
Create a goalMember or above, and the Pro plan
Edit a goal, its owners, key results and links, and post check-insA workspace admin, or an owner of that goal
Delete a goalA workspace admin

Deleting a goal is permanent and takes its check-in history with it. Archiving is the reversible option.

Troubleshooting

What you seeWhat it means
"Goals and OKRs require the Pro plan or higher."Goals are part of Pro.
"Workspace member access required"Guests cannot create goals.
"Workspace admin or goal owner required"Editing a goal is for its owners and workspace admins. Being a workspace member is not enough.
"Workspace not found" on the Goals pageYou are a guest. Guests have no access to goals.
Progress is zero with key results setCheck that each key result's target differs from its start. A target equal to the start has no distance to measure.
Progress looks out of date in the listThe list does not recompute. Open the goal to refresh it.
Progress did not move when work finishedA task changing state does not trigger a recompute. Open the goal.
Progress ignores most of your key resultsAll key results together are one source. Linked projects and sprints each count for as much as the whole set.
  • Home: where stale goals surface.
  • Analytics: how the underlying work is tracking.