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 #425 What Part of YouIs Making the Decision? PUBLISHED Sep 11, 2026 READ ON HERBIG.CO Dear Reader, For much of my career, I’ve helped product teams work through uncertainty. Chilling with my buddy King Arthur at Tintagel Castle I challenged assumptions, introduced frameworks, and helped people make better decisions when there was no obvious answer. While I still love doing that work, I’ve become increasingly interested in a deeper question over the past six years: From where...
Product Practice #424 Linked Better Practices over Stacked Best Practices PUBLISHED Sep 4, 2026 READ ON HERBIG.CO Dear Reader, “Let’s prioritize by value.” Value for whom? That was the question I explored in last week's essay Business Value, Customer Value, and Team Value Are Different Arguments. Today, let's demystify the term value even further. Nothing is inherently valuable. The same opportunity can have different value under different strategies. For that narrative to check out, we need...
Product Practice #423 Business Value, Customer Value, and Team Value Are Different Arguments PUBLISHED Aug 27, 2026 READ ON HERBIG.CO Dear Reader, As long as everyone focused on Value you can't do the wrong work, right? RIGHT? Well, as lovely as that sounds, I believe there's a tremendous amount of misdirected focus on value going on in teams. Let's dive into it. Three questions hide behind "value" in most conversations: Did this move a number the business gets paid on. Did customers change...