Teams
Every role, and what each one owns
Teams: the role carries the KRA, and the SOP names its owner.
The screen
This is the real product surface
One Tuesday
What happened from 9:03.
The same day the home page tells, read from this block.
9:03
Every role knows its process.
The SOP names its owner and the Role page carries the KRA: owned by Sam, Onboarding lead.
With Docs.
6:02
Ask anything. It knows because it's connected.
Ask reads the workspace it is in. Naming the records behind an answer is in build, and so is filing the kudos as review evidence.
With AI.
The wires
What Teams connects to
A block is a neighbour here because one stop of Tuesday puts the two of them on the ends of the same wire.
- Teams and DocsOwned by: Sam, Onboarding lead
- Teams and AISources from the linked work
The whole map, with every node and every edge, is on how it connects.
Inside it
What is inside Teams
- Directory
- org chart
- roles
- reviews
- kudos
- candor
- surveys
- Reviewscycles with the KPI and SOP scores already on them.
- Peopledirectory, org chart, roles and history.
- Kudosrecognition against the company's own values.
Not built yet
Listed because the story above describes the day they will make possible, and the narration you have read is the version that is true today.
Role page with KRA and KPI, SOP owned by a role, step attached to a KPI. Role definition page built, SOP centre shipped, SOP to KPI link not confirmed
On every tier, including the free Starter plan.
The point is what it connects to
Teams is one of eight, and the whole day is at one Tuesday.