# Point Of View

> Create compelling POVs (Points of View) that establish expertise, build credibility, and generate advisory demand through structured strategic arguments. Use when user asks to "write a point of view", "develop a POV", "thought leadership piece", or mentions industry perspective, strategic viewpoint, or expert opinion.

- Skill: `lauraflorentin/point-of-view` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lauraflorentin/point-of-view`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lauraflorentin/point-of-view/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lauraflorentin (https://skillmd.com/u/lauraflorentin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lauraflorentin/point-of-view

---


# Point of View (POV) Skill Guide

## What is a POV in Consulting?

A Point of View is a **structured argument that demonstrates deep expertise and establishes the firm as a credible strategic advisor**. Unlike sales collateral, a POV is a credibility builder—a tangible asset that positions your firm as someone who understands market dynamics, anticipates change, and offers prescriptive guidance. It's the intellectual foundation for advisory conversations.

## POV Structure

An effective POV follows this framework:

1. **Provocative Headline/Thesis** — A bold, contrarian or insightful claim that captures attention. Example: "The CPO must now own supply chain transformation, or supply chain will own the business."

2. **Context Setting** — Paint the current landscape. What's the status quo? What conventional wisdom exists?

3. **The Shift** — Identify what's changing: market forces, technology, regulation, customer behavior, or competitive dynamics.

4. **Implications** — Why does this shift matter? What's at stake for your audience? What opportunities or risks emerge?

5. **Recommended Actions** — Prescriptive next steps. What should readers do differently? Make it actionable.

6. **The Firm's Perspective** — Anchor the POV in your firm's experience, client work, or unique methodology. This builds trust and differentiates.

## POV Types

- **Industry Trend POV** — Market consolidation, digital disruption, ESG reframing within a sector
- **Technology Disruption POV** — AI, blockchain, cloud migration, automation changing business models
- **Regulatory Change POV** — New compliance requirements reshaping operations or strategy
- **Operational Challenge POV** — Talent shortages, cost pressures, supply chain fragility requiring new approaches
- **Strategic Opportunity POV** — Emerging markets, adjacent business models, or M&A themes

## Writing Principles

**Lead with a bold claim.** Avoid timid openings. Your POV should make the reader pause and think, "Is that true? That challenges what I believe."

**Support with evidence.** Balance conviction with data. Cite market research, financial data, client examples, or trend analysis. Don't just opine; ground your argument.

**Be prescriptive, not descriptive.** Anyone can describe a trend. You must explain *what it means* and *what to do about it*. Readers want direction.

**Make it actionable.** A POV should inspire a next step—a strategic conversation, a transformation initiative, or a decision. Vague insights are forgettable.

**Establish a clear "so what."** Every section should answer: Why should the CEO care? Frame in terms of growth, risk, competitive advantage, or operational resilience.

## Research Backbone

A credible POV is built on evidence:

- **Quantify the shift.** Market size changes, growth rates, adoption curves, cost impacts.
- **Balance opinion with data.** Your thesis is the opinion; research is the foundation.
- **Cite sources effectively.** Name reputable sources (Gartner, McKinsey, industry associations, academic research) but don't overwhelm with citations.
- **Use client stories (anonymously).** Real-world examples strengthen credibility. "We've seen three Fortune 500 companies in this sector make this shift."

## Tone and Voice

Write for the C-suite: **authoritative but accessible**. Avoid jargon overload. Use short sentences. Define technical terms. Be confident, not arrogant. Your tone should say, "We've thought about this deeply, and here's what we believe."

## Distribution Strategy

POVs are multifaceted assets:

- **Client meetings** — Lead advisory conversations or respond to RFP questions
- **LinkedIn** — Establish thought leadership; drive engagement and lead generation
- **Firm website** — Organize by industry, theme, or audience to build credibility
- **Conference presentations** — Use as the foundation for speaking slots or panel participation
- **RFP responses** — Demonstrate relevant expertise and differentiation
- **Sales enablement** — Arm business development teams with credible talking points

## POV vs. Other Thought Leadership

| Format | Purpose | Depth | Tone |
|--------|---------|-------|------|
| **POV** | Establish credibility + create demand | Medium (5-8 pages) | Bold, prescriptive |
| **Case Study** | Prove capability + show results | Medium-deep | Narrative, results-focused |
| **Blog Post** | Engage audience + drive traffic | Light (1-2 pages) | Conversational, timely |
| **Research Report** | Provide comprehensive analysis | Deep (20+ pages) | Balanced, data-heavy |

## Quality Checklist

Before publishing, ask:

- [ ] **Is the thesis clear?** Can someone summarize it in one sentence?
- [ ] **Is it differentiated?** Does it challenge conventional wisdom or offer a unique angle?
- [ ] **Would a client forward this to their CEO?** Is it credible and relevant to senior leaders?
- [ ] **Is it evidence-based?** Does data support the claims?
- [ ] **Are recommendations actionable?** Can a reader move from insight to decision?
- [ ] **Does it reflect the firm's experience?** Is there a unique point of view grounded in real work?
- [ ] **Is the tone right?** Confident but not preachy?

## POV Development Workflow

1. **Identify the topic** — What's a trend, shift, or challenge your team sees repeatedly in client work?
2. **Research** — Gather data, precedents, and evidence. Audit existing thinking in your firm.
3. **Develop the thesis** — Articulate the bold claim. What do you believe is true that others underestimate or misunderstand?
4. **Draft** — Write the full POV using the structure above. Aim for clarity over perfection in the first pass.
5. **Review** — Get feedback from subject matter experts and business leaders. Does it resonate? Is it differentiated?
6. **Polish** — Refine language, tighten arguments, verify citations.
7. **Distribute** — Publish and amplify across channels. Measure engagement and refine future POVs based on response.

## POV Templates by Audience

A single core thesis can be packaged for different audiences with tailored framing:

**C-Suite Executive Brief (1 page)**
- Lead with business impact (revenue, risk, competitive advantage)
- Assume limited reading time; use executive summary format
- Headline, context, implications, three recommended actions
- Include quantified impact where possible ("42% of CFOs report this challenge")
- No background detail; go straight to prescriptive guidance

**Board of Directors (Formal, Risk-Focused)**
- Frame around risk mitigation, governance, fiduciary duty
- Address regulatory or compliance implications
- Emphasize strategic implications and time-sensitivity
- Include scenario analysis if relevant ("If this shift is not addressed, X market dynamics could emerge by Q3 2025")
- Tone: measured, analytical, forward-looking
- Length: 4-5 pages; include governance considerations

**Industry Conference (Provocative, Discussion-Sparking)**
- Lead with the boldest, most contrarian claim
- Design for debate; pose questions that invite audience engagement
- Include case studies or examples that illustrate the shift
- Anticipate pushback; acknowledge valid counterarguments
- End with open question to spark panel discussion
- Visual-friendly structure with callouts and data snapshots

**LinkedIn (Shorter, Conversational, Hook-Driven)**
- Hook in first 50 words: "We're seeing something unexpected in procurement..."
- Short form (600-800 words); digestible sections
- Conversational tone; "I believe" and "we've observed"
- Include one striking data point early
- Link to full POV for interested readers
- Design for shares; end with relatable insight or challenge

**Client Meeting Leave-Behind (Includes Firm Capabilities)**
- Core POV + one section bridging to firm capabilities
- Include 2-3 relevant case studies (anonymized)
- Add "How We Help" section with specific service offerings
- Include team bios or credentials relevant to the topic
- Format: branded, professional; designed for desk reference
- Reinforce positioning before follow-up conversation

---

## Measuring POV Effectiveness

Track the business impact of your POV portfolio using these metrics:

**Engagement & Reach Metrics**
- **Views and downloads**: Total reads on website, LinkedIn, email, etc.
- **Engagement rate**: Comments, shares, and reactions on LinkedIn (target: 3-5%)
- **Email click-through**: Open rate and click rate when POV is distributed (benchmark: 25%+ open, 10%+ click)
- **Time on page**: Average reading duration (target: 2+ minutes for 5-page POV)
- **Referral sources**: Where readers discover the POV (search, social, direct links)

**Business Development Metrics**
- **Meeting requests generated**: Track how many inquiries/conversations cite the POV
- **RFP mention rate**: How often the POV is referenced in client proposals or RFPs
- **Deal influence**: Estimated revenue from deals where POV was cited during sales process
- **Speaking invitations**: Conference or event invitations directly tied to POV thought leadership
- **Media mentions**: News or industry publication citations of the POV or firm perspective

**Internal Adoption**
- **Sales team utilization**: How often business development team references POV in pitches
- **Proposal win rate**: Track win rate on RFPs where POV was included vs. baseline
- **Team engagement**: Percent of practice using POV in client conversations

**POV ROI Framework**
Calculate rough ROV to justify POV investment:

```
POV Development Cost = Research time + writing/editing + design/layout + distribution
(Estimate: 120-200 hours for well-researched POV)

POV Revenue Impact = Deal value × POV influence %
(Conservatively estimate POV influence at 15-25% of deal value)

Payback = Revenue Impact / Development Cost
(Example: $500K deal × 20% influence / $50K cost = 2.0x payback in first year)

Portfolio approach: Develop 3-4 POVs annually; measure cumulative influence on
deal flow and position for speaking/advisory opportunities.
```

---

## Building a POV Calendar

Strategic POV development follows an annual rhythm aligned with market events and firm strategy:

**Calendar Planning Framework**

**Q1 (January–March)**
- Industry outlooks and economic trend predictions
- Regulatory change POVs (tax, compliance, environmental)
- Technology trends relevant to your sectors
- Timing: Align with analyst predictions and industry conferences

**Q2 (April–June)**
- Operational efficiency and cost management (post-budget cycles)
- Digital transformation deep-dives
- Industry-specific challenges (seasonal themes)
- Tie-ins to mid-year business reviews

**Q3 (July–September)**
- M&A and growth strategy perspectives
- Talent and organizational challenges
- Third-party ecosystem integrations and partnerships
- Preparation for fall conference season

**Q4 (October–December)**
- Strategic planning and transformation POVs
- Year-end financial planning and 2026 outlook
- Industry predictions and market shifts for coming year
- Thought leadership refresh before new fiscal year

**Balancing Your Portfolio**

Structure your annual POVs across practice areas and themes:
- **By industry**: Ensure coverage across your main verticals (Healthcare, Financial Services, Technology, etc.)
- **By function**: Balance coverage (Operations, Digital, Finance, Supply Chain, etc.)
- **By topic type**: Mix industry trends (40%), operational challenges (30%), technology disruption (20%), strategic opportunity (10%)
- **By audience**: Vary between provocative/board-level vs. practitioner/functional

**Refresh Cadence**

- **Quarterly updates**: Add new data, client examples, and emerging research to evergreen POVs
- **Annual rewrites**: Identify top-performing POVs for full refresh (new case studies, updated competitive landscape)
- **Sunsetting**: Retire POVs after 18-24 months if topic is less relevant or covered by newer thinking

**Building Thematic Authority**

Develop related POVs over multiple quarters to establish authority:
- **Year 1**: "Why Supply Chain Resilience Is a Board-Level Issue" (macro POV)
- **Year 1-2**: "Three Supply Chain Models for the Next Decade" (strategic framework POV)
- **Year 2**: "Supply Chain Operating Models: From Visibility to Agility" (operational POV)
- **Year 2-3**: "AI's Role in Predictive Supply Chain Planning" (technology POV)

This creates a reference library and positions the firm as a thought leader across supply chain depth, not just surface trends.

---

**Remember:** A POV is not a sales document. It's a credibility asset. Write it to establish expertise and open conversations, not to close deals.

