8 parts, all on one data model

The screen

All 8 of them on one rail

The blocks

What each part of the platform does

• WorkTasks, lists, boards, 17 views.
• PlannerCalendar, timesheets.
• AIAsk AI on every page, reading the workspace. Not a chatbot on every button.
• TalkChannels, calls, threads.
• TeamsDirectory, org chart, roles, reviews, kudos, candor, surveys.
• DocsDocs, wikis, SOPs, policies, contracts, canvases, files.
• TablesSheets and forms.
• GoalsOKRs, KRAs, KPIs, the on track verdict.

In detail

One page for every capability

Each one describes a capability against the product today, including the parts that do not exist yet.

• Taskslists, boards and every view, with custom fields.
• SOPsfour kinds of process doc, with acknowledgement.
• KRAswhat a role owns, not what a person remembers.
• KPIstargets, readings and the weight each one carries.
• Goals and OKRscascade, rollup and the on track verdict.
• Reviewscycles with the KPI and SOP scores already on them.
• Peopledirectory, org chart, roles and history.
• Kudosrecognition against the company's own values.
• Access and roleswho can see what, at every level.
• AIone Ask, reading the workspace it is in.
• Reportingwhat the numbers are, and where they are not.
• Integrationswhat connects today, which is very little.

The argument

A feature list is not the point

Every block above does exactly one thing to one task on one Tuesday.

1. Work: the task was born at 9:04 and finished at 4:45.
2. Planner: the 15 minute call at 2:15 is what unblocked it.
3. AI: at 6:02 it answered from the workspace it reads.
4. Talk: the decision was recorded on the task at 10:30.
5. Teams: the role carries the KRA, and the SOP names its owner.
6. Docs: step 3 of the SOP is where the task came from.
7. Tables: row 41 was written by the signed form at 9:02.
8. Goals: the task lands on the goal's Effort card, and the ring moves with the KPI reading.

Read the whole Tuesday

Open it on your own work.