Stack Dyno’s docs live next to the site so you can share the same source of truth with engineers, sales, and finance.

Template

---
title: "Rightsize GKE namespaces"
impact: "$8k monthly savings"
owner: "Platform"
duration: "2 sprints"
---

## Signals
- Namespace variance >30% WoW
- CPU request/usage ratio >2.5x

## Steps
1. Audit requests vs. usage.
2. Propose new limits with rollback plan.
3. Schedule follow-up review in Stack Dyno.

Hosting

• Store playbooks as .mdx files under src/content/playbooks and link to them from docs.
• Reference them from the blog so marketing and docs stay coordinated.
• Embed screenshots or Loom videos using Markdown image syntax.

Governance

• Assign an owner per category (data, automation, onboarding).
• Review quarterly and archive anything stale.
• Track which plays shipped + their ROI to surface in sales decks.

The more you treat playbooks like product features, the faster your FinOps practice scales.