OKRs live or die on visibility. The OKRs Tool Microsoft Teams integration puts your objectives where your team already works - lightweight, read-first, and built to create awareness without adding noise.
_______________________________________________________________________________________________________
We've heard the same thing from teams at every stage:
The OKRs are set, the quarter is live, and within three weeks nobody is looking at them. Not because they stopped mattering - but because checking them requires leaving the tool everyone is already in.
Starting today, that changes.
Your OKRs can now live inside Microsoft Teams - not as a notification you'll mute or a bot you'll ignore, but as a lightweight, always-visible presence in the environment your team already works in every day.
What's Included In V1
The design principle behind V1 is simple: Teams is not the place to manage OKRs. It's the place where awareness lives. Every feature in this release was built around that distinction.
1. Sidebar App - Read-Only By Design
The sidebar app puts your OKRs and your team's OKRs - with live progress bars and status badges - visible the moment you open Teams. It's read-only by design, which matters for two reasons.
First, it removes any risk for admins nervous about shadow edits or permission creep.
Second, it keeps the experience clean - you're here to see where things stand, not to open a workflow. Click any OKR and it deep-links directly to OKRs Tool, where the work of updating and managing happens.
2. Weekly Digest - The Habit-Forming Feature
The weekly digest is the feature that quietly does the most work. Every Monday morning, a clean summary lands in your DMs - what moved since last week, which key results are slipping, and one tap to update.
It doesn't require a meeting. It doesn't require anyone to remember to check. It shows up in the rhythm of the week, which is exactly when it needs to. Delivered weekly or bi-weekly depending on your team's cadence.
3. Channel Tab - OKRs Where The Work Happens
The channel tab brings OKRs into the conversations where strategy actually gets discussed.
Add it to any Teams channel and it auto-binds to that team's objectives, showing a live read-only snapshot alongside the work.
Optional notifications fire only on status changes - nothing posts to the channel unless you explicitly enable it. The goal is ambient visibility, not a feed of updates nobody asked for.
4. Slash Commands - The Fastest Way In
Slash commands exist for the moments when someone needs an answer fast and doesn't want to switch context to get it. Three commands, nothing more:
/okr my - your OKRs and progress, right in the conversation /checkin - see any OKRs you own that haven't moved in over 7 days /okr status - a clean summary of where things stand today
Each returns a clean adaptive card with visual progress indicators and click-through links back to OKRs Tool. No forms, no workflows, no searching. The answer in the moment you need it.
5. Notifications - Carefully Scoped By Design
Teams is already noisy, so notifications in V1 are deliberately limited to three:
- Your weekly personal OKR digest
- An opt-in alert when an objective status changes
- An opt-in alert when an objective is achieved.
Every notification requires either a schedule or an explicit opt-in - nothing fires without your say-so. No real-time pings, no org-wide broadcasts, no updates nobody asked for.
Permissions You Can Trust
Teams visibility mirrors OKRs Tool exactly.
If you can't see something there, you can't see it in Teams. The install is admin-approved only, with OAuth scopes limited strictly to reading OKRs and sending bot messages. No shadow access, no data written back to OKRs Tool from Teams, no surprises in the audit log.
Teams admins at growing companies are protective of what gets installed - and they should be. This integration was built to pass that scrutiny without requiring a conversation to do it.
What We Deliberately Left Out
V1 does not include editing OKRs in Teams, creating OKRs via chat, AI coaching, meeting-based prompts, org-wide broadcast posts, or real-time collaboration. Not because those things aren't valuable - but because they're wrong for V1.
Teams is already noisy. The average knowledge worker receives dozens of notifications a day inside it, most of which interrupt more than they inform.
Adding more surfaces to manage OKRs doesn't solve the awareness problem - it compounds the complexity problem that kills OKR adoption in the first place.
We chose a narrower scope deliberately, so the integration earns trust before it asks for attention.
There will be a V2. It will do more. But V1 needed to prove that OKRs could live in Teams without making Teams worse - and we think it does.
The Rhythm This Creates
What this integration really builds is a cadence - a natural loop between the place where goals are managed and the place where work happens.
OKRs Tool remains the source of truth. The Teams sidebar creates daily awareness.
The weekly digest drives accountability. Status changes become alignment moments rather than surprises in the next all-hands.
Each layer plays a distinct role without duplicating the others. Together, they turn OKRs from something people check when they remember into something they notice because it's always there - in the right place, at the right moment, without asking for more attention than it earns.
That's when OKRs stop being a planning artefact and start being part of how the team thinks about the week.
The integration is available now for all OKRs Tool Expand customers using Teams. Admin approval required for install. Set it up in under five minutes.
