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 #407 Your Goal Depends on Another Team — Now What? PUBLISHED May 7, 2026 READ ON HERBIG.CO Dear Reader, Your Key Result says to "Improve Conversion Rate by 7%," but you only control on-site search. You want to drive customer retention, but the marketing team is focused on new acquisition. Most teams respond in one of two ways: they water down the goal until it fits their scope (and lose the ambition), or they keep the big goal and quietly accept they can't move it. Both lead...
Product Practice #406 Why your Company's POV on OKRs matters more than Processes PUBLISHED Apr 30, 2026 READ ON HERBIG.CO Dear Reader, Before I talk with companies about OKR cadences, templates, or tools, I ask them: "What do you expect to change by using OKRs?" The answers take a bit of time. Not because they don't exist, but because OKRs have been treated as a solution without a problem to solve. OKRs haven't been treated as a product, but as a process without purpose. They've chosen a...
Product Practice #405 How to treat Prototypes as Decision-Making Tools PUBLISHED Apr 23, 2026 READ ON HERBIG.CO From Strategy Choice to Planned Experiments in One Workshop In my upcoming live remote workshop From Strategy to Discovery, I take you from sharpening your Product Strategy, to defining leading indicators for measuring progress, all the way to prioritized assumptions you need to derisk end-to-end. Three 4h Live Sessions - Lifetime Material and Recording Access - Real Results Join...