> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/become-a-tability-power-user/how-tos/how-to-choose-an-owner-for-your-goals.md). # How to Choose an Owner for Your Goals Don't give your senior leaders all of your OKRs and still expect good updates Every key result and initiative in Tability needs an[ owner](https://guides.tability.io/docs/become-a-tability-power-user/features/plans/owners-and-contributors) — the person responsible for keeping it updated. That part's usually clear. What trips teams up is deciding who that person should be, especially on cross-functional goals, or goals where the person best positioned to report on progress isn't the most senior person tied to the outcome. ### The core idea: ownership is about updates, not org charts The most common mistake is treating "owner" like a title on an org chart — the most senior or most ultimately-responsible person for the outcome. That's not what the role is for. In Tability, the owner is the person who is closest to the work and best positioned to say, week to week, "here's where this actually stands." Being an owner isn't a statement about who's in charge. It's a statement about who has the clearest, most current view of progress. So the question to ask isn't "who is responsible for this outcome at the highest level?" It's: * Who has the day-to-day visibility into this metric or project? * Who would know first if something changed? * Who can write an honest, specific check-in without having to go ask someone else? ### Example: Jane Smith vs. the CFO Say your company has a key result like "Reduce days sales outstanding (DSO) to 35 days." It's ultimately the CFO's responsibility in the sense that finance performance rolls up to them. But should the CFO be the owner in Tability? Probably not — and here's why: * Jane Smith in Accounting is the one actually running collections, tracking invoices, and watching the DSO number move week to week. * The CFO cares about the outcome, but relies on Jane's team to know why the number moved and what to do about it. * If the CFO is the owner, check-in reminders land on someone who doesn't have the granular update — which means the update either doesn't happen, or gets forwarded to Jane anyway to write. Making Jane the owner doesn't change who is ultimately accountable to the business for financial performance. It just puts the check-in responsibility on the person who can actually write it accurately. The CFO can still be added as a contributor to stay visible on the goal, get notified of updates, and step in on strategy — without being the one holding the pen. A useful reframe: ownership answers "who reports on this?" Accountability up the chain is a separate question that your org chart already answers. Tability doesn't need to re-answer it. ### Handling cross-functional goals Cross-functional goals feel harder because multiple people are genuinely doing the work. But the same rule still applies: pick one owner, and add everyone else as contributors. A few ways to decide who that one owner should be when several people are involved: * Pick the person who touches the metric most often. If three teams contribute to a goal but one team's work directly moves the number, their representative is usually the right owner. * Pick the person coordinating the work, not just doing a slice of it. On an initiative that spans teams, the project lead or coordinator often has the clearest end-to-end view, even if they're not the one executing every task. * When it's genuinely a coin flip, pick the person who's most consistent about updates. A goal with an owner who reliably checks in is more useful than one with a "correct" owner who never does. Remember that ownership can move. If Jane goes on leave, or the work shifts to a different team next quarter, reassign the owner. It's not a permanent title — it's a current point of contact. Need to hear both voices in equal measure? Since contributors are notified of updates, the other users can come and add comments onto the check-in to add context or give their own update. The metric only has one person making a change (no accidental double counting), and there’s one main person who will get the notification (no bystander syndrome where everyone expects someone else to do the update). ### A quick checklist Before assigning an owner, ask: 1. Does this person have first-hand visibility into the work or metric? 2. Could they write this week's check-in without needing to ask someone else first? 3. Are they still the right point of contact, or has the work shifted to someone else since the goal was set? 4. Is anyone else meaningfully involved who should be added as a contributor instead of left off entirely? If you can answer those, you've got your owner — regardless of where they sit on the org chart. ### Common mistakes to avoid * Defaulting to the most senior person tied to the goal. Seniority isn't the same as day-to-day visibility. * Leaving a goal without an owner because "it's a team effort." Every goal needs exactly one owner. Shared effort is what contributors are for. * Assigning ownership once and never revisiting it. Teams and responsibilities shift — so should ownership. * Confusing "owner" with "the person who benefits most from success." Plenty of stakeholders care about a goal's outcome without being the right person to report on it.