Workflows
The product is organised around the control loops a PM actually lives through—not around a feature catalogue.
Request accessToday → Project → Action
Starting signal. A project, action, or gate is asking for attention.
Workbench action. Open Today, identify the dominant reason, and choose the next review move.
Resulting output. A ranked next move with owner, due date, and project context.
Explore this control loopMeeting → Action Tracker
Starting signal. A decision or selected meeting text needs to survive the room.
Workbench action. Capture it as a linked action with owner, due date, and project context.
Resulting output. An action that remains attached to the meeting and the project record.
Explore this control loopGate → Evidence → Report
Starting signal. A review is approaching and evidence may still be missing.
Workbench action. Inspect documents, data packs, and linked deliverables before the meeting.
Resulting output. A visible readiness picture and the gaps that still need an owner.
Explore this control loopDocuments → Export
Starting signal. A conversation needs the supporting files, notes, and outputs in one place.
Workbench action. Assemble the review material, then export a portable package.
Resulting output. An explicit local handoff, not a cloud sync.
Explore this control loopProject → Closure
Starting signal. Remaining work, final documents, and delivery packs still need confirmation.
Workbench action. Walk the closure path before the project is marked closed.
Resulting output. A durable record of what was finished and what was handed on.
Explore this control loopThe point of the loop
The workbench keeps context close enough that a discussion can become a decision, a decision can become an action, and an action can return to the project picture with its source still visible.
Read the documentation