post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

How to build a companion product and win user trust

mission statement

Deep dive: Crafting your product vision and mission

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

5 ways to invent and simplify as an AI/ML product manager

<a href="http://www.linkedin.com/in/jmburke/en">Jason Burke</a> is VP, Product for <a href="http://www.clypd.com">clypd</a>, a Boston-based startup building an advertising technology platform exclusively for the TV industry and designed to empower media companies with programmatic sales tools and deliver integrations with systems that translate, simplify and automate how advertising campaigns are packaged and sold.

Prior to clypd, Burke spent six years building ad technology products for online video at ScanScout and Tremor Video where he had responsibility for product management, technical strategy and operations efforts.

Jason is a leader with the unique experience of working with executive customer teams and internal product development/engineering groups to drive business while also solving software and implementation challenges with internal and external technical teams. He is also a frequent contributor to industry publications and participant on advertising technology and media conference presentations and panels.

Jason is based in Boston and has degrees in Computer Science and Engineering Psychology from Tufts University.

Jason Burke

Warren Buffett, a slightly successful investor, once said, “The difference between successful people and very successful people is that very successful people say ‘no’ to almost everything.” Swap person for company and qualify company with technology startup, and not only is it an informed statement, it’s an absolute fact.
At the start of the year, product management organizations work with their colleagues across the business to determine the game plan for the coming annum, not only for the product roadmap, sales strategy and marketing calendar, but for the business as a whole. A common artifact of this activity is often an endless list of features and products, then immediately followed by a gasp of “How the hell are we going to do this?!?”
So, how are we going to do all that? Easy: We’re not going to do all of it.
Of course, that’s easier said than done. Features are on these lists, because someone has identified some value with each item. However, whether a company is Google-sized or is an early-stage startup, resources are always finite and tomorrow always comes quicker than expected, making proper prioritization imperative.
<a href="https://www.mindtheproduct.com/wp-content/uploads/2015/02/feature-prioritisation.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-6409" src="https://www.mindtheproduct.com/wp-content/uploads/2015/02/feature-prioritisation.png" alt="feature prioritisation" width="555" height="343" srcset="https://www.mindtheproduct.com/wp-content/uploads/2015/02/feature-prioritisation.png 555w, https://www.mindtheproduct.com/wp-content/uploads/2015/02/feature-prioritisation-300x185.png 300w" sizes="(max-width: 555px) 100vw, 555px" /></a>
Prioritization within the world of product development is not a matter rank-ordering features by some single measurement and choosing the top X features that the team can bite off, but rather involves weighing many attributes of the feature (benefit to the business, cost to build, complexity, dependencies on other features, etc) against each other; this process of conjoint analysis allows all stakeholders to participate in the process to surface the products and features that are of highest value when compared against others under consideration.
Some questions to ask yourself when prioritizing include:
<ul>
<li>What do we want to do? Identify high-level business themes. Each major project should help achieve success against one or more of the themes for the year. A theme-based approach also helps to avoid a focus on potentially non-impactful projects.</li>
<li>How will this feature benefit the business? Of course, benefit may have different meanings, including objective, measurable impacts on the business, such as revenue, or something softer like generating buzz in the industry. But if the positive impact of having a feature as part of a product cannot be clearly identified, then ask yourself: is it worth the investment required to build?</li>
<li>What is the cost to build? Cost can be monetary, but generally with software development, cost is calculated by the man hours required to build. In addition to being a parameter for prioritization, the development cost will drive the relative prioritization and timing of other projects.</li>
</ul>
The output of a solid prioritization plan may surprise stakeholders when features that initially seemed to be must-haves end up on the cutting room floor. An effective plan for product development includes prioritization as its most important facet and creating that plan requires the discipline to use data and analysis to strategically say no and to say it often.
A “hell, no!” should be used on the seemingly must-have feature that might generate immediate but short lived value (whether that’s revenue, short-term industry buzz or the like). Effective product management requires looking beyond the horizon with a full 360-degree view. Figuring out what’s important and ask whether your limited resources are laser-focused on moving forward on the top themes.
Even with a flawless prioritization strategy, there is one item that any startup product guy would kill for. Engineering team please note: please build a day with 36 hours – all other feature requests will be no’d.

core/freeform

Product Management

It’s the Strategy, stupid – Andrew Martinez-Fonts (VP Product, Honeysales)

LLM workflows for product managers: 3 key takeaways (Niloufar Salehi, Assistant Professor at UC Berkeley) – ProductTank SF

How to survive the next phase of tech – Jonty Sharples (Product and Strategy Consultant)

Transformed: Moving to the product model by Marty Cagan

Product teams in flux – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Berlin’s leading companies – Pendomonium+#mtpcon roadshow: Berlin

Product teams in flux – Pendomonium+#mtpcon roadshow: Amsterdam

Product teams in flux – Pendomonium+#mtpcon roadshow: London

What’s next for product management in 2024? Nichole Mace (SVP Product and User Experience, Pendo)

“You’re not as competent as you think” 5 lessons from Ken Chin on navigating a product career (CPO, Spark Networks)

Just Say No: Hard Decisions in Product Management

Jason Burke

Read more

Comments