Template Overview

Weekly executive staff meetings determine operational cadence and ensure cross-functional alignment across product, engineering, revenue, and operations. Without structured meeting records, executive alignment dissolves into conflicting interpretations of cross-departmental priorities.

This template structures your leadership sessions around business impact: high-level KPI tracking, cross-team roadblock triage, strategic decisions, and clear executive accountability.

By capturing leadership discussions in plain Markdown, executives can review past agreements, verify milestone dates, and track historical commitments directly within their personal vaults.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Leadership Team Weekly Alignment"
date: [YYYY-MM-DD]
facilitator: "[[Chief Operating Officer]]"
attendees:
  - "[[CEO]]"
  - "[[VP Engineering]]"
  - "[[VP Product]]"
  - "[[VP Revenue]]"
  - "[[Head of People]]"
tags: [leadership, executive, weekly-alignment]
---

# Leadership Team Weekly Alignment — [YYYY-MM-DD]

## 1. Scorecard & KPI Review (10 mins)
| Metric | Target | Actual | Trend | Notes |
| :--- | :--- | :--- | :--- | :--- |
| Monthly Recurring Revenue | $500k | $518k | 🟢 Up | Enterprise deal expansion |
| Sprint Velocity | 90 pts | 88 pts | 🟡 Stable | Refactoring audio pipeline |
| Customer Satisfaction (CSAT) | 95% | 97.2% | 🟢 Up | Fast turnaround on bugfixes |
| 30-Day Churn Rate | < 1.0% | 0.8% | 🟢 Down | High retention on local model |

## 2. Departmental Highlights & Watch Items (15 mins)
### Engineering ([[VP Engineering]])
- Deployed zero-latency local speech pipeline for M-series chips.
- Watch item: Memory ceiling on 8GB base hardware under intense load.

### Product & Design ([[VP Product]])
- Finalized user research on template discovery interface.
- Kicking off beta cohort for markdown table formatting shortcuts.

### Revenue & Customer Success ([[VP Revenue]])
- Closed three key pilot accounts in healthcare sector.
- High prospect demand for zero-telemetry software certifications.

## 3. High-Priority Blockers & Strategic Decisions (20 mins)
> [!IMPORTANT] Core Decision
> Approved reallocation of two backend infrastructure engineers to assist local inference optimization for the upcoming macOS release.

## 4. Action Commitments & Ownership (5 mins)
- [ ] [[VP Engineering]] Finalize 8GB memory envelope benchmarks by Thursday.
- [ ] [[VP Product]] Share user feedback synthesis on template repository.
- [ ] [[VP Revenue]] Deliver security architecture white paper to incoming enterprise leads.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Leadership Team Weekly Alignment"
date: 2026-10-05
facilitator: "[[Marcus Vance]]"
attendees:
  - "[[Robert Sterling]] (CEO)"
  - "[[Elena Rostova]] (VP Eng)"
  - "[[David Park]] (VP Product)"
  - "[[Rachel Adams]] (VP Revenue)"
tags: [leadership, executive, weekly-alignment]
---

# Leadership Team Weekly Alignment — October 5, 2026

## 1. Scorecard & KPI Review
- MRR tracking: Reached $522k against $500k target (+4.4%).
- Net retention rate: 114% across enterprise cohort.
- Engineering cycle time: Average PR time-to-merge reduced from 18h to 9h.

## 2. Key Departmental Updates
- **Elena (Engineering):** Shipped native CoreAudio capture module. Verified zero frame drops on M1, M2, and M3 Macs.
- **David (Product):** Usability research complete for 120 markdown templates. Users requested one-click download buttons.
- **Rachel (Revenue):** Signed 6 legal firms seeking sovereign notes.

## 3. Decisions Reached
> [!IMPORTANT] Decision Record
> Confirmed launch date for Template Gallery as October 9, 2026. Code freeze scheduled for 48 hours prior.

## 4. Accountable Actions
- [x] [[Elena Rostova]] Merge CoreAudio tap improvements to main.
- [ ] [[David Park]] Finalize category taxonomy for template hubs.
- [ ] [[Marcus Vance]] Audit vendor contracts ahead of quarterly renewal.

When to Use and When to Avoid

When to Use

  • Use for weekly operational check-ins between department heads and executive officers.
  • Use when tracking high-level OKR status and unblocking cross-functional bottlenecks.
  • Use when executive team members need an unambiguous record of shared resource allocations.

When to Avoid

  • Avoid using for granular software bug triages or code-level technical debates.
  • Avoid using for formal board of directors governance meetings.

On-Device AI Integration

Summarize the recorded executive alignment call with this Oyma local prompt:

Review the meeting transcript and produce a structured leadership brief:
1. Extract numerical performance indicators and match against quarterly goals.
2. Highlight key progress reports from Engineering, Product, and Sales.
3. Identify cross-functional blockers and document the agreed resolution.
4. List all action items with explicit individual owners and due dates.
Format with markdown callouts and tables.

Because processing happens locally on your Mac, confidential revenue metrics and product launch roadmaps remain secure.

Frequently Asked Questions

How does this template prevent executive meetings from running over time?

The agenda enforces strict time-boxing across metrics review (10m), departmental highlights (15m), deep-dive strategic blocker resolution (20m), and action assignments (5m).

Can executive blockers be linked directly to project folders in Obsidian?

Yes. The template utilizes [[WikiLinks]] to connect departmental deliverables directly to underlying project directories in your vault.

How does Oyma identify strategic decisions during leadership calls?

Oyma's on-device AI identifies affirmative decision phrases, policy changes, and deadline commitments from local meeting transcripts, inserting them into the decisions callout block.