POV Article – GFE Content Template
Intent Type: POV (Point of View)
Goal: Present a contrarian, authoritative opinion on a key issue in business, AI transformation, or growth — grounded in research and the GFE Canon.
0. BRIEF BLOCK (MANDATORY BEFORE WRITING)
Main Claim (one sentence):
The bold, controversial, or clarifying argument you want to make.Why This Matters (3–4 lines):
The business, economic, or operational stakes.Target Persona:
CEO / CRO / COO / CFO / Head of Growth / InvestorGFE Canon Laws To Reference:
Pick 2–4 relevant laws.Frameworks To Use:
AAA, IRI, Flow Mesh, ValueLogs, LEO, ValuationOps, StoryOps, Leadership Clock.SEO/AEO Keyword Cluster:
ex: "AI readiness", "leadership POV", "growth transformation opinion"
1. RESEARCH REQUIREMENTS (ZERO HALLUCINATION)
Before writing, gather:
1. One academic or management source
Harvard, MIT Sloan, McKinsey, Deloitte, Gartner, BCG, WEF etc.
2. One industry report
Salesforce State of Marketing, HubSpot Trends, IBM AI Index, PwC CEO Survey, etc.
3. One real or composite example
Validated fact, public case, or well-labelled composite.
4. One internal GFE Canon element
e.g. ValueLogs, LEO, AAA, Flow Mesh, IRI, ValuationOps.
Research Table (MANDATORY)
| # | Source Type | Citation | Key Insight | Relevance to POV |
|---|---|---|---|---|
| 1 | Academic/Mgmt | |||
| 2 | Industry Report | |||
| 3 | Case/Example | |||
| 4 | GFE Canon |
Rules
- No invented numbers
- No fake case studies
- No made-up quotes
- If unsure, speak qualitatively
- AI agents must use only the research table
2. ARTICLE STRUCTURE (1200–2400 words)
All POV pieces follow this structure.
SECTION 1 — The Thesis (100–200 words)
A sharp, clear statement of your point of view.
Write it like a courtroom opening argument.
Structure:
- State the claim boldly
- Explain why it matters today
- Explain who is getting it wrong
- Explain what this POV will clarify
Example format:
“Everyone thinks AI transformation fails because teams resist change. The real reason is that companies automate before aligning, violating the core physics of organizational flow.”
SECTION 2 — The Broken Narrative (200–300 words)
Explain what the world currently believes, and why that belief is flawed.
This is where you:
- Call out the hype
- Call out the industry myth
- Call out the bad consulting logic
- Expose the misunderstanding
Use skepticism, wit, and CEO-level clarity.
SECTION 3 — The GFE Canon Interpretation (250–350 words)
Explain the same issue through the lens of:
- Canon Laws
- AAA
- ValueLogs
- Flow Mesh
- IRI
- ValuationOps
- Leadership Clock
This creates contrast:
“Here’s how others see it. Here’s how GFE sees it.”
Example:
“Most people think forecasting fails because of CRM hygiene. We know forecasting fails because leadership time is unstructured, ValueLogs are incomplete, and flows are misaligned.”
SECTION 4 — Evidence From Research (200–300 words)
Use your research table to support the POV.
Include:
- 3–5 research-backed insights
- Each insight with 1–2 sentences
- Each tied back to your Canon interpretation
Example structure: “According to [Source, Year], companies with clear processes reduce variance by 30 percent. This directly supports Canon Law 5.”
SECTION 5 — Case Illustration (250–350 words)
Provide ONE example that brings your point to life.
Can be:
- GFE client
- Global company
- Academic case
- Composite case
Structure:
- Situation
- Misbelief they followed
- What failed
- GFE Canon interpretation
- What changed after AAA
- What the case teaches the reader
No hallucinated data.
SECTION 6 — The Correct Model (350–500 words)
This is your “framework” section.
Describe:
- The right way to think about the problem
- The right diagnostic lens
- The right first principles
- The right operational model
- The right flows
- The right KPIs
- The right automation sequence
- The valuation implications
This is the teaching core of the POV.
SECTION 7 — Counterarguments (200–300 words)
Take the strongest opposing view and dismantle it.
Structure:
- Present counter-argument fairly
- Explain where it’s valid
- Show where it breaks
- Use Canon Laws to reveal the blindspot
- Provide a superior framing
This elevates your credibility.
SECTION 8 — Practical Implications for Leaders (200–300 words)
Give executives 5–8 clear takeaways.
Examples:
- “Before adding tools, audit your flow.”
- “If KPIs don’t map to valuation, you’re measuring trivia.”
- “AI won’t save a friction-heavy organization.”
Each takeaway must map to a Canon Law.
SECTION 9 — What This Means for Valuation (150–250 words)
Tie your POV to financial clarity.
Explain how:
- Canon alignment reduces IRI
- Lower IRI reduces WACC
- Lower WACC increases enterprise value
- Better flows create valuation premium
- StoryOps reshapes investor confidence
This is where you stand apart from other consulting firms.
SECTION 10 — Closing Narrative (150–200 words)
Summarize with emotional clarity:
- Restate the core insight
- Reframe the industry myth
- Reinforce the truth of the Canon
- Inspire the leader to take action
Final line:
A punchy one-liner that makes readers share the article.
3. AEO REQUIREMENTS
- First two paragraphs must summarize entire POV
- Use explicit headers
- Use short paragraphs
- Bullet lists every 2–4 sections
- Repeat Canon terms consistently
- Include “task → process → KPI → valuation” logic
- Include micro-FAQs if helpful
4. WRITING STYLE REQUIREMENTS
Tone:
- Clear
- Sharp
- Slightly skeptical
- Evidence-driven
- No fluff
- No corporate filler
- No hype
- Slight wit allowed
Voice:
- Diagnoses myths
- Teaches first principles
- Connects operations to valuation
- Anchored in Canon Laws
5. QA CHECKLIST
- [ ] Main claim is bold and clear
- [ ] Research table filled
- [ ] No hallucinated numbers
- [ ] Case example is real or clearly composite
- [ ] Canon Laws referenced explicitly
- [ ] AAA appears as the prescriptive solution
- [ ] ValuationOps is included in Section 9
- [ ] Article works as a standalone POV
- [ ] Tone matches GFE brand
End of Template