FRAMEWORK_TITLE

Replace FRAMEWORK_TITLE, FRAMEWORK_SHORT, and the hero image references before publishing.

1. What It Is (definition + quick signal)

1. Give one clear definition of the framework (avoid jargon-first sentences).
2. Introduce the Build (why the model exists, what axis/variables it maps).
3. Mention the classic origin story (eg, “BCG coined the growth/share matrix…”).

2. Wit & Analogy (a quick metaphor, ideally surprising)

• Deliver one short, memorable comparison or world analogy so the concept “sticks” (e.g., comparing the BCG four quadrants to a team of improv performers).
• Pull in a subtle one-line nod to human+AI or value narratives in the analogy.

3. Framework Walkthrough

• Break this into the visual quadrants/steps (use bullet or table; match the image).
• Each quadrant/step should briefly explain:
  • What it represents
  • Typical behaviors or KPIs to monitor
  • A micro-story about how the team would spot it during a ValuationOps sprint

4. Real-world Examples

• Offer 2–3 crisp examples (internal handle optional). Include:
  1. How a RevenueOps team would map a product line to the matrix/quadrant.
  2. A Marketing or Sales scenario from GrowthFlowEngineering’s experience.
  3. Optional mention of a counter-example or cautionary tale.

5. Limitations & Pitfalls

• Call out where the framework under-indexes nuance (time horizons, pricing signal, technology debt, etc.).
• Flag when it tends to mislead (e.g., “star” obsession or ignoring internal capability readiness).

6. GFE Playbook Mapping

• Explicitly align the framework to:
  • ValuationOps – which KPI cells or reports it feeds, what dashboards change.
  • AAA – which stage (Audit, Align, Automate) leverages it and why.
• You can use a short bullet list or two-column table for clarity.

7. Takeaways / Call to Action

• Sum up the 2–3 decisions leaders can make with this frame.
• Invite readers to try a quick experiment (share a prompt for gemini-proxy or a KPI/metric check).

8. Publication & Automation Notes

1. Update blog-data.js with the path, sections, and tags, and add the hero image reference so the section filters surface the post.
2. Drop the hero image into docs/public/images/blog/, optimize it (WebP, <200 KB), and embed it inside the article via a <figure> block.
3. If a supporting YouTube explainer exists, embed it with a responsive iframe (replace VIDEO_ID) and tie the caption back to the framework’s ValuationOps or AAA narrative.
4. Commit the markdown to docs/en/blog/posts/ and add a matching entry in the blog-data.js array so npm run sort:blogs can keep everything ordered.
5. Agents should be able to duplicate this template, adjust placeholders, and run npm run sort:blogs + npm run generate:blog-sitemap before release.