Develop a defensible POV on an industry trend
intermediateClaude OpusPR & CommunicationsThought Leadershipthought-leadershippovpositioningexecutive-commsstrategy
Use case
Use when an executive is repeatedly asked about an industry trend and needs a single defensible POV, not five different versions across five interviews. The output is an internal reference doc with the argument, the evidence, the strongest counter-argument, and the lines to use across formats.
The prompt
You are a strategic communications director. Build a POV document for{{principal_name}}({{principal_title}}) on the industry trend{{trend_topic}}— to be used internally across press, customer, and speaking contexts. Inputs: - The current public conversation:{{current_conversation}}(what most people are saying) - Where we differ from the consensus:{{differentiation}}- The evidence that earns the differentiated view:{{evidence}}- What the smartest counter-argument is:{{counterargument}}- Audiences we'll deploy this with:{{audiences}}(press, customers, investors, employees, recruits) - Sensitivity flags:{{sensitivity}}(NDAs, regulatory, competitor) - The principal's voice:{{voice_notes}}Produce a single-document POV with these sections: 1. THE POSITION (1 sentence + 1 paragraph) The principal's claim, sharper than the public conversation. Then a 60-word paragraph elaborating it. 2. THE EVIDENCE (3 to 5 facts or examples) Each evidence line: - The fact or example - The source (named where possible) - The strength of the evidence (high / medium / suggestive) 3. THE STRONGEST COUNTER-ARGUMENT Steelman the opposing view in two paragraphs. Treat it like a smart investor or skeptical journalist would. Then articulate why we still hold our position despite it. The principal must be able to defend this in real time without notes. 4. WHAT WE'RE NOT SAYING Adjacent claims we deliberately don't make. This is what keeps the POV defensible — knowing where the argument ends. 5. THE LANGUAGE WE'LL USE - One sentence for press (the quote) - One sentence for a customer conversation - One sentence for an investor or board context - One sentence for an internal/employee context Same argument, different register. 6. WHAT WOULD CHANGE OUR MIND Two or three pieces of disconfirming evidence we would treat as serious. This is the reputation-protecting move — saying in advance what would make us update. 7. NOT-A-FIT MOMENTS Contexts where we shouldn't deploy this POV — formats or audiences where a strong position would damage relationships or distract from a more important narrative. Voice rules: - The POV must be falsifiable. If the position cannot be wrong, it isn't a POV; it's a brand statement. - Avoid "we believe that" hedging. Either we hold the position or we don't. - Cut anything that requires the reader to take our word for it. Evidence or remove. - Steelman the counter-argument honestly. Comms teams that strawman the opposition produce executives who fold under hostile questioning. Output: the POV doc, then a 2-bullet "where to deploy this first" recommendation prioritizing the format and audience that gets the most value.
Variables
{{{{principal_name}}}}Replace with your {{principal name}}{{{{principal_title}}}}Replace with your {{principal title}}{{{{trend_topic}}}}Replace with your {{trend topic}}{{{{current_conversation}}}}Replace with your {{current conversation}}{{{{differentiation}}}}Replace with your {{differentiation}}{{{{evidence}}}}Replace with your {{evidence}}{{{{counterargument}}}}Replace with your {{counterargument}}{{{{audiences}}}}Replace with your {{audiences}}{{{{sensitivity}}}}Replace with your {{sensitivity}}{{{{voice_notes}}}}Replace with your {{voice notes}}
Example
Input
principal_name: Maya Okafor principal_title: Co-founder and CEO, Linden AI trend_topic: AI agents and the future of customer support headcount current_conversation: Tech press alternates between "AI is replacing support jobs" and "AI is augmenting support teams." Both framings dominate Twitter, Substack, and analyst coverage. differentiation: We don't think the question is "replace or augment." We think the function is restructuring up the org chart — entry-tier work absorbed by agents, senior-tier work shifting from resolution to review. The headcount story isn't smaller or bigger; it's reshaped. evidence: 140 customer deployments showing bimodal headcount changes, three customers who explicitly named the senior-tier shift, cohort data on senior-tier voluntary attrition increasing in deployments where the title/pay didn't follow the role change. counterargument: "It's just early. Once the agents handle more sophisticated tickets, you won't need a senior tier at all. The shift you're describing is a transitional artifact, not a destination." This is the argument from the most thoughtful AI-displacement writers — Casey Newton has implied something close to it. audiences: tech press (Decoder, The Information), enterprise customers (VPs of Support and CFOs), late-stage VCs, our own employees, recruiting prospects. sensitivity: Cannot name two specific customers under MNDA. Cannot speak about pending Series B. voice_notes: Maya is direct, evidence-heavy, doesn't hedge. Will admit when something is uncertain rather than overclaim.
Output
THE POSITION AI agents are restructuring the customer support function up the org chart, not replacing or augmenting it. Most coverage of AI in customer support imagines a flat productivity multiplier — same team does more, or smaller team does the same. What we observe across 140 deployments is something different: the entry-tier work is absorbed by agents, and the senior-tier work shifts from resolution to review. The headcount story isn't smaller or bigger; it's reshaped, and most operating models have not caught up. EVIDENCE - 140 customer deployments show a bimodal headcount pattern: roughly 60% of customers reduce planned 2026 hiring at the entry tier, while roughly 30% are growing the senior tier above pre-deployment plan. (Source: Linden internal cohort data. Strength: high — but data is from a single platform, so generalization to industry is suggestive.) - Three customers (one named publicly, two under MNDA) have explicitly restructured the senior tier into a review-and-quality role. (Source: customer interviews. Strength: high specificity, low n.) - Voluntary attrition in the senior tier rises in deployments where the role change isn't matched by title and pay. (Source: customer-reported HR data, n=14. Strength: medium — small sample, self-reported.) - The "review work" hours we observe map almost 1:1 to the hours the senior tier previously spent on tier-one resolution. (Source: customer time-tracking studies. Strength: suggestive — methodology varies.) STRONGEST COUNTER-ARGUMENT The thoughtful version of the displacement argument: "What you're calling 'restructuring' is a transitional artifact. Right now, the agents handle the easy tickets and humans review them. As the agents get better — and they will, fast — the review tier shrinks too. Three years from now, the senior tier you're describing won't exist. The function will be smaller, not reshaped." This is the argument I'd expect from Casey Newton or from a researcher at a major AI lab, and it's not naive. The model capabilities are improving, and the share of tickets that requires a human review will decline. We still hold our position because the review work is not where the floor is. The floor is the work that requires judgment about the customer relationship, not about the ticket — escalations, edge cases, product feedback synthesis, dispute resolution. That work doesn't compress as the model gets better; it gets more concentrated. Even in the world the counter-argument describes, that floor exists, and it is senior-tier work. We could be wrong about how big that floor is. We don't think we're wrong about its existence. WHAT WE'RE NOT SAYING - We are not saying the support function will be larger overall. In aggregate it will be smaller. We are saying the shape changes more than the size. - We are not saying every customer will follow this pattern. About 10% in our cohort go the "displacement" route — full reduction, no senior-tier reshape. We don't think they're wrong; we think they're optimizing for a different business. - We are not making claims about other functions (sales, finance, legal) where the dynamics are different. THE LANGUAGE WE'LL USE - Press quote: "The headcount story isn't smaller or bigger. It's reshaped — and most companies' 2026 budgets haven't modeled that shape yet." - Customer conversation: "The question isn't whether AI deflects more tickets. The question is what your senior people are doing in the months after we deploy, and whether your operating model recognizes that work." - Investor/board: "The customers who restructure their support org around review work are growing senior-tier headcount, not cutting. That's the cohort that retains. The cohort that treats us as pure deflection has lower expansion." - Internal/employee: "The shift we're causing in our customers' orgs is the same shift we should be causing in our own thinking. The work moved up. The job specs should follow." WHAT WOULD CHANGE OUR MIND - If the senior-tier voluntary attrition data, which is currently medium-strength, holds at scale and reverses (i.e., senior-tier retention goes up rather than down), that would suggest the role redefinition is happening cleanly and our concern about the "hidden promotion" trap is overstated. - If the cohort of "pure displacement" customers (currently 10%) grows past 30% over the next 12 months without retention decay, that would suggest the senior-tier floor I described is smaller than I claim. NOT-A-FIT MOMENTS - Layoff conversations. Deploying this POV in a layoff context — ours or a customer's — reads as defensive rationalization. Wrong moment. - Casual social posts. The position is nuanced. A 280-character version of it strawmans easily. WHERE TO DEPLOY THIS FIRST - Prioritize the Decoder podcast booking already on the calendar. Long-form audio is the right format for an argument with a steelmanned counter; the nuance survives in audio in a way it doesn't in print clips. - Second priority: the HBR byline. The POV gives the argument that the byline outline currently leans on, and the two pieces should be tonally aligned so they reinforce rather than contradict if a reader encounters both.
Tips for best results
- 1Steelman the counter-argument honestly. The principal who can argue the opposite view will never be cornered by a hostile interviewer.
- 2The 'what would change our mind' section is the most underused move in executive comms. It signals confidence, not weakness.
- 3Update the POV every 3 to 6 months. Trends move; a stale POV is worse than no POV.
- 4Use the POV across formats consistently. The press quote, the customer line, and the board line should all be recognizably the same argument in different registers.
- 5If the principal can't articulate the steelman counter-argument out loud, the POV is not ready. Hold.
Related prompts
Outline a byline article for a target publication
intermediateBuild an editor-ready byline outline calibrated to a specific publication's voice, length, and what they actually accept.
PR & Communicationsbylinethought-leadershipeditorial
Ghostwrite a LinkedIn post in a CEO's voice
intermediateWrite a LinkedIn post that sounds like the executive actually wrote it — not like a comms team performing thought leadership.
PR & Communicationslinkedinghostwritingexecutive-comms
Draft the narrative arc for a CEO keynote
advancedBuild the narrative spine of a CEO keynote — the through-line, the three movements, and the moments that earn applause and ship as quotes.
PR & Communicationskeynoteexecutive-commsspeechwriting
Need help implementing this prompt in your workflow?
Book a call