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 #417 User Outcomes are Positively Flipped User Problems PUBLISHED Jul 17, 2026 READ ON HERBIG.CO Dear Reader, Last week, I mapped how OKRs connect to the layers of an Opportunity Solution Tree. But especially the Outcome layer deserves its own issue: turning a customer problem into a team-level Key Result. I first wrote about it in 2023, before I had a name for it. Since then, the positivity flip has become one of the most-used tools in my OKR and Discovery workshops, so...
Product Practice #416 How to Connect OKRs to OSTs PUBLISHED Jul 10, 2026 READ ON HERBIG.CO Dear Reader, OKRs (Objectives and Key Results) help you measure strategic progress. OSTs (Opportunity Solution Trees) are a visual structure for connecting solution and problem spaces to business goals. Let me break down how the layers of an OST connect to the practices of OKR drafting and execution: Layer 1: The Outcome Teresa differentiates between business outcomes, product outcomes, traction metrics...
Product Practice #415 Accelerated Context and the Validation Sparring Partner PUBLISHED Jul 3, 2026 READ ON HERBIG.CO Dear Reader, Most of the AI conversation in product management right now is either describing doomsday scenarios, exaggerated improvements, or warning about what might go wrong. But I am more interested in what changes for product teams doing real work. When a product team adopts an AI tool, what specifically changes about their day? What benefit do they keep coming back for,...