LoginSign Up
← Back to all sparks
T

Tability

PM
Velocity7.5

OKR and goal-tracking platform for teams to set, track, and align objectives with metrics and weekly check-ins.

www.tability.io ↗

Tability is building the org graph its AI agents will need to act on.

okr-managementstrategy-graphai-agentsorg-hierarchyreportingenterprise-scale
◆Current state
Tability is an OKR and strategy platform that has spent 2026 turning a plan hierarchy into a queryable graph. The Strategy Map now organises by people as well as plans, the Dependencies Map traverses up to parent context and down through downstream work from any object, and a workspace-wide filtering layer with saved segments sits over goals and initiatives. Running alongside is an agent track: an AI Importer that reads OKR and KPI spreadsheets into reviewable proposals, and AI managers that can be assigned to a goal and must route decisions back through an approval flow.
◆Where it's heading
The two tracks are converging, and the sequencing tells the story. Delegating goals to AI agents shipped first; the releases since have been building the structure those agents need to reason over — who reports to whom, what depends on what, which slice of a busy workspace a question is actually about. Overflow controls on large maps and a refreshed Initiatives view point at customers with enough plans and people for readability to become the constraint, which is a different buyer than the small-team OKR tool this category started as. Import friction is being attacked from the same direction: an AI-assisted path out of spreadsheets, with review gates before anything is created.
◆Prediction
Expect the agent features to start consuming the graph the recent releases exposed — dependency-aware and reporting-line-aware agent actions rather than per-goal delegation — and the scheduled-prompt mechanism behind executive summaries to widen into other recurring outputs.

◆Recent moves

  1. 2d ago

    Keep large Strategy Maps readable with overflow controls

    Layer-level overflow controls let users cap how many children appear at once and pick which to show. It reads as a scale fix rather than a feature: once the Strategy Map spans a whole organisation's plans and people, legibility becomes the limiting factor, and this is the second release in a row addressing large-workspace density.

  2. 2d ago

    Review initiatives faster from the refreshed Initiatives view

    The Initiatives view is rebuilt on the new filtering layer, so managers can cut execution work by owner, team, plan, status, timeline, or completion and save the segment. Notable for what it assumes about the customer: the stated problem is no longer collecting updates but finding which of many initiatives needs attention.

  3. 2d ago

    Build custom views with the new filters

    A workspace-wide filtering layer across goals and initiatives — ownership, teams, timelines, status, progress, confidence, tags, overdue check-ins — with quick views and saved segments so a review does not start by rebuilding the query. This is the substrate the refreshed Initiatives view sits on, and it is what makes the rest of the graph work navigable at size.

  4. 2d ago

    Import OKRs faster with the AI Importer

    The AI Importer, introduced weeks earlier, is now reachable from the Plans workflow and detects plans, objectives, key results, initiatives, owners, teams, and timelines into a proposal the user confirms. Steady iteration on the migration path — the review-before-create gate is consistent with how Tability handles every AI action in the product.

  5. 2d ago

    Trace complete dependencies from any objective, key result, or initiative

    The Dependencies Map can now start from any object — plan, objective, key result, or initiative — and traverse both to parent context and through downstream dependencies, with noisy branches collapsible. Traversal in both directions is what turns a dependency feature into something usable for diagnosis when progress has stalled for reasons no single goal card explains.

  6. 2d ago

    Organise the Strategy Map by people, not just plans

    ⚡ SPARK

    Strategy Map gains a People view, letting the same strategy be explored through reporting lines and ownership instead of plan hierarchy. It adds a second organising axis to the product's central artifact, and lands alongside a People directory that expands each profile into the OKRs, initiatives, and direct reports beneath it.