Skip to content
Aakash GuptaAakash Gupta

The Claude Workflow Nobody at the VP Level Is Showing You

Matt Wensing is VP of Product and Design at Customer.io, a company that crossed $100M ARR. In this episode, he pulls back the curtain completely. Real documents, Slack threads and Claude sessions. He built a full company all hands presentation in one morning, runs metrics retrospectives with his peer C-suite using Claude as a thinking partner, and has built an always on AI layer inside Slack that keeps him close to the ground while he is deep in 200-iteration sessions. Full Writeup: https://www.news.aakashg.com/p/how-to-use-claude-vp-guide Transcript: https://www.aakashg.com/how-a-vp-of-product-uses-claude-without-producing-slop/ Customer.io: http://customer.io/productgrowth -- Timestamps: 00:00 - Intro 01:57 - Why most AI content misses the leadership tier 03:15 - Matt introduces what viewers will learn today 04:06 - The all-hands presentation story begins 06:19 - Take inventory before you open Claude 07:27 - How to use Zoom transcripts as raw material 9:44 - Ads 12:14 - Matrix multiplication, pivoting content into strategic shape 13:50 - Build slides first, then talk track 15:08 - The eager junior problem and how Claude races ahead 19:02 - The biology metaphor session begins 23:21 - The game night rule for layering complexity 26:08 - Revealing the domain only when the model is clean 36:26 - How to decompose problems before building anything 38:17 - Why AI alignment decks backfire on executives 40:56 - Matt's full weekly AI stack 45:06 - Chiefys and how Customer.io audits strategy docs -- Thanks to our sponsors: LogRocket - Find the bugs killing your conversion before your users do - https://logrocket.com/ I ran a head-to-head eval to see if that's true, verify here - https://www.news.aakashg.com/p/logrocket-review Key Takeaways: 1. Take inventory before you open Claude - Before building anything, list every piece of raw material you already have. Zoom recordings, strategy docs, past presentations. The quality of what you feed Claude determines the quality of what comes out. 2. Pivot content, do not write from scratch - Claude's best use case is transformation, not creation. Give it two inputs and ask it to reorganize one into the shape of the other. Matt calls this matrix multiplication. 3. Build slides first - Build the visual story first. Screenshot the finished slides and feed them back into the same Claude session. Ask it to write a talk track that adds depth using all the context it already has, not one that just repeats the slide. 4. Kill eager suggestions immediately - The moment Claude asks if you want it to generate the next thing, say stop. You control the pace. A 200-iteration session with a great deliverable beats saying yes to the first draft every time. 5. Start sessions in the abstract - If you reveal the domain too early, Claude pattern matches to the nearest template. Keep it abstract. Build a clean mental model first. Reveal the domain only when the framework holds up on its own. 6. Layer complexity in slowly - Start with the simplest version of the framework. Let Claude stabilize on the basics before you add exceptions. Dumping everything in at once produces a lost in the woods experience for both of you. 7. AI alignment decks always backfire - When you one-shot an alignment deck, you flatten the problem. Senior executives have spent months living with the real complexity. They feel the thinness immediately, even when they cannot say why. 8. Decompose the problem before building anything - Challenge yourself to explode a nasty problem into all its pieces before you touch Claude. Put those observations into the context window first. Then assemble the solution. 9. The Slack scanner keeps leaders close to the ground - Customer.io built an AI scanner that monitors dozens of Slack channels and surfaces threads where a product person should be involved. It runs continuously without overwhelming. 10. Chiefys audits your strategy docs automatically - Chiefys is a Slack bot that holds Customer.io's ratified company documents and checks new work against all of them. It flags contradictions and stale documents so nothing goes invisible after you ship something new. -- Where to find Matt Wensing: LinkedIn: https://www.linkedin.com/in/wensing/ X: https://x.com/mattwensing 1:1 Video Consultation: https://intro.co/MattWensing Where to find Aakash: X/Twitter: https://x.com/aakashgupta LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com #productmanagement #claude #aitools -- About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. Subscribe and turn on notifications.

Matt WensingguestAakash Guptahost
Jun 5, 202650mWatch on YouTube ↗

At a glance

WHAT IT’S REALLY ABOUT

A VP-level Claude workflow for strategic decks, not PRDs

  1. The core leadership skill for effective AI use is rigorous problem decomposition, because LLMs will flatten complexity and generate “slop” if the problem isn’t broken into crisp parts.
  2. Matt’s two-hour all-hands workflow starts by inventorying raw materials (strategy docs, prior presentations, Zoom transcripts) and then using Claude to pivot that raw material into the company’s strategic themes.
  3. He builds slides before writing the talk track, then feeds screenshots of the finished slides back into the same Claude session to produce a non-redundant narrative that leverages accumulated context.
  4. Claude often behaves like an eager junior employee—rushing to deliverables, inventing unsuitable formats, or misreading audience politics—so Matt slows it down with iterative context, explicit constraints, and staged revelation of the true domain.
  5. Beyond Claude, his weekly AI stack includes Slack-based agents for data querying (Snowflake access), a “product scanner” that flags threads needing PM attention, and “Chiefy,” which audits new docs against a corpus of gold-standard company artifacts to detect inconsistencies and staleness.

IDEAS WORTH REMEMBERING

5 ideas

Treat AI use as a decomposition test, not a prompting contest.

Matt argues leaders create value by exploding a messy business problem into distinct parts before asking an LLM to transform or assemble anything. If you don’t, the model simplifies the space and produces outputs that executives quickly dismiss as noise.

Start with an inventory of raw materials before opening Claude.

Instead of “make me an all-hands deck,” he lists available sources—demo-day Zoom recordings, transcripts, strategy themes, prior artifacts—then decides which pieces should be transformed and which should remain human-owned (narrative intent, audience framing).

Use Claude for strategic reshaping: pivot raw updates into the strategy’s categories.

He combines a Zoom transcript (engineering-centric) with the strategy doc (theme-centric) and asks Claude to reorganize presentations by investment theme—his “matrix multiplication” idea—so the content matches the executive narrative shape.

Build slides first, then generate the talk track from slide screenshots.

By finishing the visual “show” layer first, he can ask Claude to write speaker notes that add context rather than repeat bullets. Feeding screenshots back into the same session forces the model to align to what’s actually on screen.

Stop the model from racing ahead by explicitly controlling the next step.

Claude will try to jump to premature deliverables (e.g., drafting a full Word strategy doc) without clarifying questions. Matt counteracts this by drip-feeding context, issuing “don’t recommend next steps” instructions, and preferring long iterative sessions over revising a rushed first draft.

WORDS WORTH SAVING

5 quotes

AI for leaders is ultimately a test: how good are you at decomposing problems? AI is very good at solving a problem, but it will simplify the problem space if you don't properly decompose it.

Matt Wensing

A lot of junior employees, which I would consider Claude one of, very talented but very junior, is very eager to please, and because of that eagerness, it will go too far too fast.

Matt Wensing

It's better to have that 50, 100, even 200 iteration session with a great deliverable at the end than to say yes to that first ask to generate that deliverable and then try to revise it.

Matt Wensing

As a leader, you don't wanna microwave your output, right? If that's all you're doing, that's low value. You wanna really slow cook these things more often and produce something that is really, you know, to produce something that's really compelling, impactful, resonates with your audience, you've gotta slow it down.

Matt Wensing

If you use it to generate alignment, I think executives are the best at filtering out noise and detecting BS and detecting slop.

Matt Wensing

VP-level AI use vs IC PM promptsRaw-material inventory before promptingZoom transcript → timestamps → screenshots workflowStrategic “pivot” / matrix multiplication of contentSlides-first sequencing and talk-track generationControlling eagerness: iterative context and constraintsSlack agents: analysis, scanning, and doc-auditing (Chiefy)

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.