Brainforge Knowledge

company-okrs-in-platform.plan

7 min read

Document Company OKRs and Goals in the Platform

Phased plan

PhaseScopeOutcome
Phase 1Document the plan and get it in the repo.This phased plan and the full Company OKRs plan are versioned (e.g. in vault); PR merged. No implementation.
Phase 2Option A implementation.Company Goals page at /internal/company-goals; API reads from GTM Review sheet (and optionally Management Operations, Notion, vault); nav added. Single source of truth remains sheets/Notion.
Phase 3Option B / Extended plan.DB-backed company objectives, OKRs, AOR; sync from sheets/Notion; platform-only fields (e.g. Linear links, status history). See Extended plan section.

Implementation work (Phases 2 and 3) is tracked in the Linear project Company Objectives in Platform.

Current state

  • GTM Review sheet (Google): Brainforge Objectives, BAU OKRs, Aspirational OKRs, Q2 OKRs — see original plan for structure.
  • Brainforge Management Operations (xlsx / second sheet): You provided Brainforge Management Operations (1).xlsx. It is a separate operations workbook with the following goal-relevant content:

Brainforge Management Operations – sheets to document

SheetWhat to document in platform
GTM OKRs Q1 2026Department, Objective, KPI, Owner, Status (LAGGING/ON TRACK/POOR/KICKOFF), Value, Key Update, Next Step. Marketing + Sales focus.
Active OKRs Q4 2025Same structure; includes Delivery, Marketing, Sales, AI, Recruiting. Source (e.g. Finance Dashboard, Sales Dashboard).
Q3 2025 OKRsFull quarter OKRs with weekly status columns and End of Quarter Synthesis (historical reference).
Q126 AORAreas of Responsibility: Department (Executive, Sales, …), AOR Description, Q1’26 Importance, DRI, Backup, DRI Status. Critical for “who owns what” at company level.
12.22.25 / 12.15.25 / Sales OKRs Q4 2025Weekly snapshots of Sales OKRs; can be used to show status history or folded into “current” Q4 view.

Operational but secondary for “goals” page: Client Staffing Tracker, Operating Updates, CSO-SL-EPs Tasks Log, Role-based Skills, EP Tasks Daily/Weekly Log (useful for internal tools or a separate “Operations” view). Salary Ranges: keep internal; do not expose in a general Company Goals page.

  • Notion (past objectives and OKRs): Notion holds additional OKR and objective content that should be included as sources for the platform:
    • OKRs (page) → OKRs 2025 - Objectives (database): OKRs 2025 - Objectives. Schema: Objective (title), Key Result (relation to linked DB), Dates, Formula. View “Jan - April 25”. Use for 2025 historical objectives and key results.
    • OKRs (parent page): OKRs – hub for the 2025 Objectives database.
    • Q3 Marketing OKRs (page), Q4 OKR Planning (page) – quarter-specific OKR planning and marketing OKRs.
    • Recruiting AORs and OKRs – Referenced in RECRUITMENT_HANDOFF as living in Notion (“Details and owners: Recruiting AORs and OKRs doc (in Notion)”). Use for Recruiting/PeopleOps OKRs and AORs.
    • Employee Goal Setting Framework – Includes “Alignment with Company Objectives”; useful for how individual goals tie to company objectives.
  • Vault (already in repo): Recruiting-AORs-and-OKRs.md – Company-Level Objectives (3: hiring/org engine, operational integrity, performance-based incentives), Recruiting AORs, Recruiting BAU/Aspirational OKRs, Operations BAU/Aspirational OKRs. Format aligned with “Brainforge Objectives spreadsheet.” Either use this file as a source for the platform or sync from Notion if that is the single source of truth.
  • Platform today: No company-level goals/OKRs surface. Client-scoped weekly goals exist (weekly_goals table); operating decks have hardcoded OKR bullets.

What to document (combined sources)

  1. Company objectives – From GTM Review: Brainforge Objectives + Why + Exec Focus.
  2. OKRs by period and type – From GTM Review: BAU OKRs, Aspirational OKRs, Q2 OKRs (department, objective, key results, owner, workspace link, commentary, status).
  3. Management Operations OKRs – From Brainforge Management Operations: GTM OKRs Q1 2026, Active OKRs Q4 2025 (and optionally Q3 2025 for history), with Status, Value, Key Update, Next Step. Either merge with GTM Review Q1 view or show as “Operations view” of the same goals.
  4. Areas of Responsibility (AOR) – From Brainforge Management Operations “Q126 AOR”: Department, AOR Description, Importance, DRI, Backup, Status. Enables “who is responsible for what” alongside “what are our goals.”
  5. Notion: past OKRs and Recruiting/Operations – From Notion: OKRs 2025 - Objectives database (Objective, Key Result, Dates) for 2025 history; Q3 Marketing OKRs, Q4 OKR Planning pages; Recruiting AORs and OKRs (doc in Notion). Optionally Employee Goal Setting Framework for alignment wording.
  6. Vault: Recruiting-AORs-and-OKRs.md – Company-Level Objectives (3), Recruiting and Operations BAU/Aspirational OKRs and AORs. Use as source or ensure parity with Notion.

Where in the platform

  • New internal page: Company Goals at /internal/company-goals (or /internal/okrs), linked from Internal hub and Sidebar.
  • Sections on the page:
    • Company objectives (from GTM Review)
    • OKRs by period: Q1 2026 (BAU + Aspirational from GTM Review; optional merge with Management Operations “GTM OKRs Q1 2026” and “Active OKRs Q4 2025”), Q2 2026 (from GTM Review as you fill it)
    • Areas of Responsibility (from Management Operations “Q126 AOR”)
    • Optional: Past OKRs (2025) section fed from Notion “OKRs 2025 - Objectives” (or vault) and links to Q3/Q4 planning pages.
    • Optional: link to “Edit in Sheet” (GTM Review), “Management Operations” (xlsx or Google), and Notion OKRs / Recruiting AORs and OKRs as single sources of truth.

Data approach

  • Option A (for initial implementation): Read from Google Sheets (and Notion/vault as needed). Single source of truth stays in sheets/Notion; platform reads on load or manual refresh. No DB for company goals yet.
  • Option B (preferred eventually, not implementing now): Store in DB (e.g. company_objectives, company_okrs, company_aor); “Refresh from sheet” or “Import from sheet/Notion” to sync. Enables faster load, offline/cached view, and platform-only fields (e.g. links to Linear initiatives, status over time). Captured in Extended plan below.

Extended plan for company objectives (future, not now)

No implementation required now; this section records where we want to take company objectives in the platform over time.

  • Option B data model – Supabase (internal) tables: company_objectives, company_okrs, company_aor. Sync from GTM Review sheet, Management Operations (xlsx or Google), and optionally Notion (OKRs 2025, Recruiting AORs/OKRs). “Refresh from sheet” button or scheduled job to keep platform in sync; sheets/Notion remain source of truth for editing.
  • Platform-only fields – Once in DB: link OKRs to Linear initiatives or projects; store weekly status history for bonus/retro; optional “last synced” and sync logs.
  • Other extensions (as needed) – Status updates in platform (vs only in sheet); API for agents/skills (meeting prep, standup deck, GTM skill); export for board/investor; optional “Past OKRs” archive by quarter. All deferred until Option B or explicit ask.

Implementation outline

  1. Decide where Management Operations lives – Keep as xlsx and add an import script, or migrate to Google Sheets (e.g. same spreadsheet as the second link) so the platform can read both sources via Sheets API.
  2. Define exact ranges – For GTM Review: tabs/ranges for Company Objectives, BAU OKRs, Aspirational, Q2. For Management Operations: tab names and ranges for “GTM OKRs Q1 2026”, “Active OKRs Q4 2025”, “Q126 AOR” (and optionally Q3 2025).
  3. Backend – GET /api/brainforge/company-goals (or internal API) that returns: { objectives, bauOkrs, aspirationalOkrs, q2Okrs, managementOpsOkrs?, aor?, notionOkrs2025?, vaultRecruitingOkrs? }. Include Notion API (or existing Notion sync) to read OKRs 2025 - Objectives database and optionally Recruiting AORs/OKRs page; optionally read Recruiting-AORs-and-OKRs.md from repo. If using Option B, add Supabase tables and sync/import.
  4. Frontend – New page at apps/platform/src/app/(main)/internal/company-goals/page.tsx: fetch from API, render Company objectives, OKRs by period (with status, key update, next step where available), and AOR section. Link to GTM Review and Management Operations as sources.
  5. Navigation – Add “Company Goals” to Internal tools list and Sidebar.
  6. Operating decks – When Q2 is live, align deck content with Company Goals (or link to this page).

Summary

  • Sources: (1) GTM Review Google Sheet – objectives, BAU/Aspirational/Q2 OKRs. (2) Brainforge Management Operations – Q1 GTM OKRs, Active Q4 OKRs, Q3 history, and Q126 AOR (who owns what). (3) Notion – OKRs 2025 - Objectives database, Q3 Marketing OKRs, Q4 OKR Planning, Recruiting AORs and OKRs doc. (4) Vault – Recruiting-AORs-and-OKRs.md (Company-Level Objectives, Recruiting/Operations OKRs and AORs).
  • Place: New internal page Company Goals at /internal/company-goals.
  • Data: Start with Option A (read from Sheets/Notion). Option B (DB + sync) is the preferred long-term approach; captured in Extended plan for company objectives (no implementation now).
  • Next steps: Decide where Management Operations lives (Google vs xlsx import); implement API + page; add nav; extend for Q2 2026.

Graph View

Backlinks