<aside> 🧭

FLOW WORK SYSTEMS GLOBAL NAVIGATION

⌂ CEO Operating System

OPERATE 🎛 CEO Dashboard ☀ Daily Action 🗓 Weekly Review ⚡ Quick Create

• Business portfolio
• Build & maintain
• Records & resources </aside>

<aside> 🛠️

FLOW WORK SYSTEMS · WORKSPACE NAVIGATION & MAINTENANCE

Use this guide to navigate the workspace, create records correctly, and keep dashboards and master databases accurate over time.

</aside>

<aside> ⚡

CREATE RECORDS

Open Quick Create Center · Open Template Center

Use a form for normal record creation. Use a reusable template only when the new record requires a structured page body, checklist, or operating brief.

</aside>

01 · Where to work

02 · Where information belongs

<aside> 🔒

Create each item once in the master database for that type of information. Dashboards display filtered views of those records; they are not separate copies that need to be updated independently.

</aside>

• Businesses & Operating Units stores the purpose, customer or user, value-delivery path, current focus, main obstacle, review rhythm, and consolidated executive condition for each company, brand, division, client operating area, or internal unit.
• Strategic Goals & Outcomes stores the material business result, accountable owner, time horizon, target date, success criteria, connected initiatives, execution, governance items, and executive-review scope.
• KPI Scorecards stores the evidence used to judge performance: current and target values, trend, accountable owner, source, cadence, and next review.
• Projects & Initiatives stores coordinated outcomes requiring several steps, milestones, health, completion or approval requirements, next handoffs, known exceptions, Project Lead, and explicit Strategic Goal or KPI linkage. The Business relation remains the authoritative portfolio connection.
• Tasks stores individual actions, the expected result, conditions for completion, due date, Responsible Person, structured waiting and blocking sources, proof of progress or completion, next handoff, and the canonical Business and Project relations. Responsible Person is the person accountable for moving the task forward.
• Meetings & Outcomes stores participants, context, formal Decision Records, unresolved issues, and executable Follow-Up Tasks. Meeting notes provide evidence; linked records carry the work and governance lifecycle.
• Content Operations stores strategy-connected content planning, production, approval, publication, accountable Content and Approval Owners, related tasks, decisions, assets, calls to action, and performance notes.
• Launches & Releases stores release readiness, Operating Owner, related tasks, decisions, vendor dependencies, content approvals, supporting SOPs and knowledge, launch date, and calculated delivery exceptions.
• Vendors & External Partners stores outside contacts, commitments, Relationship Owner, waiting tasks, decisions and risks, affected launches, files, and follow-up dates.
• Operating Processes & Workflow Maps stores repeatable value-delivery architecture, stages, owners, decisions, handoffs, quality gates, bottlenecks, improvement tasks, risks, SOPs, knowledge, and AI support.
• SOPs & Playbooks stores approved recurring procedures, Process Owner, related workflow maps, supporting knowledge, quality criteria, review condition, and evidence that the procedure is used.
• Knowledge Library stores approved guidance, policies, research conclusions, limitations, owner, review condition, related SOPs, and AI-assisted workflows that rely on it.
• AI-Assisted Workflow Registry stores governed AI procedure specifications, source knowledge, SOPs, process maps, implementation work, decisions and risks, testing evidence, human-approval requirements, and responsible owner.
• CEO Operating Reviews stores the executive review and connects operating units, Strategic Goals, KPI Scorecards, initiatives, decision records, and follow-up tasks reviewed during that period.