1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com
From Product Jargon to Plain English
From Product Jargon
|
Dear Reader,
I often feel that, somewhere along the way, we, as an industry, started optimizing for sounding like product people instead of speaking like humans in plain English (or any other language).
What would happen if we dropped the product lingo and used plain English to describe what's needed? I find it increasingly liberating for product teams to describe their work in plain language rather than throwing fancy terms at team members and stakeholders.
Here are some of my favorite examples I come across in my work, along with how to simplify them using plain English.
"Product Operating Model" → How would teams work when we put measurable business and customer value before feature completion and requirement correctness?
"Strategic Playing Field" → For whom are we trying to solve what problem, and who else tries to do that?
"Outcome OKRs" → How can we measure if we changed our customers' behavior?
"Opportunity Solution Trees" → How do features drive business goals by solving customer problems?
"Leading Indicators" → What would tell us early if what we're doing works, before it's too late to adjust?
"Experiments" → How can we find out if we can and should build this, before building it?
The jargon isn't the problem. It's when the jargon replaces the thinking. But reducing the jargon helps create space for the thinking.
Next time you try to talk about a practice, pause and think about what it really is that should be achieved. Then, say it like it is. Without the jargon labels.
(and, yes, I'm sometimes part of choosing the lingo of the value behind words as well 🤷♂️)
Thank you for Practicing Product,
Tim
Get my Book
As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.
I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.
Product Practice Newsletter
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com
Product Practice #397 3 Things to Put into YourNext Strategy Document PUBLISHED Feb 27, 2026 READ ON HERBIG.CO Dear Reader, The most effective strategy document I've seen doesn't worry about the looks or format. Whether it's a scrappy Google Doc or a fancy Miro template, what matters is the quality and cohesiveness of the information it contains. Make sure what you cover aligns with your company's expected standards to ensure stakeholder understanding and, consequently, buy-in. But make sure...
Hallo liebe:r Leser:in, English Translation below for internal forwarding to your German colleagues Du lieferst Features aus und wirst nach KPIs gefragt – ohne Verbindung zu Erfolg für Nutzer:innen und Geschäft. Die Strategie deines Unternehmens ist entweder zu vage oder fehlt ganz. Das Ergebnis: Alibi Progress statt echter Wirkung.In meinem Workshop "Strategische Umsetzung statt KPIs abarbeiten – Entwicklung & Messung von Produktstrategie am 4. Mai im Rahmen der Product Owner Days 2026...
Product Practice #396 MECE: Double the Usefulnessof Your Metrics Trees PUBLISHED Feb 19, 2026 READ ON HERBIG.CO Dear Reader, Many resources say your metrics trees need to be "MECE." But how do you do it? MECE stands for: Mutually Exclusive Collectively Exhaustive In the context of metrics trees, this means mapping the individual drivers of an overarching goal in a way that allows us to identify and improve domain-specific levers through selective focus, while creating holistic...