Tability (@tabilityio) header
Tability (@tabilityio) profile picture

Modern goals for modern teams. A complete platform to stay on top of your OKRs, KPIs, and initiatives as a team. Try it for free today!

Sydney, New South Wales
Joined December 2018
Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)Photo by Tability (@tabilityio)
Focus, alignment, transparency, and accoun*tability*. Helping you keep a pulse on what matters most is what we do best 💪🎯
1
1
7
482
We wrote a QBR template you don't fill in. Paste the prompt into Claude or ChatGPT. It interviews you 2-4 questions at a time. If it's connected to our MCP server, it pulls the quarter's KRs, check-ins and blocked initiatives (read-only), asks before using any of them, and hands back a filled QBR plus an agenda sized to your meeting length. It won't invent a number. Unknowns stay as visible TBCs.
2
20
Recency bias is the silent killer of quarterly planning. The last 3 weeks of Q4 will feel like the whole quarter. So before anyone writes a Q1 OKR, we run a 50-minute retro: 15 min grading last quarter's objectives 10 min timeline of what actually happened 25 min start/stop/continue + votes Then we plan. Never the other way around.
1
7
Spinning up agents is easy now. Managing them isn't. Friday test: → how many agents ran this week? → which goal did each one serve? → which ones moved a number? → what did that cost? If you can't answer, you don't have an agent workforce. You have a token bill.
1
24
Gartner predicts 40%+ of agentic AI projects get cancelled by end of 2027. Reasons: escalating cost, unclear value, no risk controls. None of those are model problems. They're ownership problems. An agent with no owner, no goal and no reporting cadence is just a very expensive demo.
1
8
Hot take: the weekly leadership brief should be a cron job. Ours is a scheduled prompt that runs Monday 8am, reads live goals, KPIs, initiatives and check-ins, and returns six sections with source links. The chief of staff edits. They don't assemble. Tip: keep cadence and recipients out of the prompt. That's what the schedule is for.
1
1
29
Build log: our social agent files its own OKR check-ins. It runs on a schedule in Claude Cowork, pulls follower and post data, then posts a scored check-in to its key result in Tability through our MCP server. Most useful thing it's done so far: showed us our link posts got up to 10x less reach than link-free tips. So this post has no link.
2
30
Our Monday business review writes itself now. One scheduled prompt over our goals, KPIs and check-ins. Out comes a scorecard, the 3 biggest changes, at-risk goals, stale check-ins, and decisions needed with owners. Every claim links to its source. The line in the prompt that matters most: "If evidence is missing or stale, say so." No hallucinated progress.
1
10
Prompt engineering is overrated. Try three words. Paste our playbook link into Claude, ChatGPT or Grok, say "Run this playbook", and it: → reads your site + connected tools → drafts a 90-day plan (themes, goals, 5 KPIs) → saves it as a .md file → sets up weekly reviews through MCP
1
18
How are you tracking what your agents actually do? Not "it ran." Did it move a number anyone cares about? Our rule: every agent gets a goal, an owner, and a weekly check-in. Same as a human. If it can't report progress against a key result, it's a demo, not a teammate.
1
9
Why most agent pilots stall right here: tability.io/odt/articles/ent…
3
Q4 started a week ago. Quick gut check: are your goals just Q3's with bigger numbers? We keep one page of links for exactly this moment. Retros, writing OKRs in 30 min, align don't cascade, check-in rituals, and free AI goal + metric generators.
1
16