<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chris Rosenbaum on Medium]]></title>
        <description><![CDATA[Stories by Chris Rosenbaum on Medium]]></description>
        <link>https://medium.com/@chrisrosenbaum?source=rss-921871c106a2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*maTxna5d_q_Y5gLLHlCD6g.png</url>
            <title>Stories by Chris Rosenbaum on Medium</title>
            <link>https://medium.com/@chrisrosenbaum?source=rss-921871c106a2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:08:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisrosenbaum/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Forget VCs & Founders: Do Product Managers Have an Obligation to a Greater Good?]]></title>
            <link>https://medium.com/productmaven/forget-vcs-founders-do-product-managers-have-an-obligation-to-a-greater-good-20de1b36591c?source=rss-921871c106a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/20de1b36591c</guid>
            <category><![CDATA[social-justice]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[accountability]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Chris Rosenbaum]]></dc:creator>
            <pubDate>Thu, 12 Oct 2017 15:51:14 GMT</pubDate>
            <atom:updated>2017-10-12T15:51:14.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lMwhXf01CRwXhT_ZpjEyWA.png" /><figcaption>“Pratice two things in your dealing with disease: either help or do not harm the patient”</figcaption></figure><p>Defining the product manager has become its own genre of tech content.</p><p><a href="https://www.aha.io/roadmapping/guide/product-management/what-is-the-role-of-a-product-manager">According to Aha!</a>, the role of the PM “spans many activities from strategic to tactical and at its best provides cross-functional leadership… [includes] the strategy, roadmap, and feature definition for that product or product line… [and] may also include marketing, forecasting, and profit and loss (P&amp;L) responsibilities.”</p><p><a href="https://svpg.com/inspired-how-to-create-products-customers-love/">Marty Cagan says the product manager’s job</a> is “to discover a product that is valuable, usable and feasible.” <a href="https://www.mindtheproduct.com/2011/10/what-exactly-is-a-product-manager/">Mind the Product</a> and <a href="https://a16z.com/2012/06/15/good-product-managerbad-product-manager/">Ben Horowitz</a> have offered much-read views on the matter.</p><p>These articles always talk about things like strategy and communication. Lots of focus on users and their needs. Phrases such as “deep sense of passion”, “delivering superior value to the market place”, and “CEO of the product.”</p><p>But what is conspicuously absent from every discussion that I could find is any responsibility to a greater good, any sense of head-checking (let alone designing for) any social, moral, ethical imperative. Is this a problem?</p><h3>The buck stops… where?</h3><p>There is nothing new about pushing back on Silicon Valley. As a vision of the future, it’s always been a lightning rod for controversy, both deserved and undeserved. It’s hard to tell if the recent fever pitch in the mass media (<a href="https://www.economist.com/news/leaders/21720621-venture-capitalists-are-bright-clannish-and-almost-exclusively-male-silicon-valleys-sexism">Economist on sexism</a>, <a href="https://www.salon.com/2017/05/20/silicon-valleys-ceo-worship-problem/">Salon on CEO worship</a>, <a href="https://www.newyorker.com/business/currency/why-cant-silicon-valley-solve-its-diversity-problem">The New Yorker on diversity</a>, the <a href="https://www.nytimes.com/2014/03/16/magazine/silicon-valleys-youth-problem.html">New York Times on youth</a>, etc.) is yet another indication of the 24-hour news cycle, or is really a new stage in the bubble.</p><p>The Times calls out a blunt question: “Why do these smart, quantitatively trained engineers, who could help cure cancer or fix healthcare.gov, want to work for a sexting app?”</p><p>It’s easy to jump on board the bash-wagon and point a finger at the Bodegas and Juiceros, so I won’t bother. There are many truly impactful ventures in the tech world that have delivered exceptional and meaningful improvements to many living, breathing humans. It’s also ludacris to think we can’t have some toys and apps that exist purely for fun and enjoyment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*4fbb5hJ3OH6XB0xln2Sprg.jpeg" /><figcaption>It’s his fault.</figcaption></figure><p>The debates on these topics above usually focus on the core concept (the founders, board, etc.) or on the aggregate decisions of the talent pool. But I’d like to take a look at this from the product level, from the perspective and influence of product leaders and managers. A PM might not have any control over the very existance of a particular product or service, but they do certainly impact its definition.</p><h3>Existing efforts</h3><p>There have been some poking around this space, such as Pragmatic Marketing’s <a href="https://pragmaticmarketing.com/blog/post/the-product-launch-pledge">Product Launch Pledge</a> in 2009, but even this is myopically focused on existing stakeholders. There have been other nods to the Hippocratic Oath for ________ (<a href="http://mitsloan.mit.edu/newsroom/articles/in-era-of-ethical-crisis-time-for-a-venture-capital-hippocratic-oath/">venture capitalists</a>/<a href="https://www.washingtonpost.com/news/on-leadership/wp/2014/07/30/a-hippocratic-oath-for-bankers/?utm_term=.50f9c563f135">bankers</a>/etc.)</p><p>In particular, in product design and the slipperly slope of attention-grabbing app behaviors, Tristan Harris has cultivated his <a href="http://www.tristanharris.com/">Ethics for Designers</a> and <a href="http://www.timewellspent.io/">Time Well Spent</a> initiatives (also discussed in this <a href="https://vimeo.com/193155921">25-min Vimeo</a>).</p><p>There are obviously many angles from which to approach this, but today we focus on product management. Should product management include a pillar of consideration for social impact? The current dogmas around user-centricity, data-driven decisions, and knowing the numbers are closely held. But in the discussions of industry surveying and skillset building and career pathing, I see little to no thought of intentionally considering any semblance of a bigger picture, of human obligations.</p><h3>It’s not all or nothing</h3><p>I am not advocating a double bottom line for all companies. Every business does not need to be a charity. But the devil is in the details, and if we expect issues such as economic inequality, racial tensions, workplace diversity, and others to be solved purely with a top-down approach, we’re sadly mistaken.</p><p>There is no all-or-nothing dicotomy here. Small, intentional behaviors can lead to increasingly better decisions at all levels. The product lifecycle is ripe with oppportunities to ask simple questions and infuse critical perspective in the process. Simply asking questions around impact can lead to new and progressive debates:</p><ul><li>If this feature is successful, are there any negative side effects for our users that we might not have anticipated?</li><li>Are there any groups of people that our current product may be unintentionally marginalizing or forsaking?</li><li>Is there a way this concept can provide a greater good at the same price?</li><li>Does our roadmap consider social value when prioritizing?</li></ul><p>It feels like the current assumption is that these sorts of issues are handled subconsciously, that we all like to think we act with both our personal and company values, and thus we’re already set. But that’s baloney. These topics are important enough to be explicit, to be debated, to be measured.</p><h3>RPM FTW?</h3><p>The New Yorker recently opined about a <a href="https://www.newyorker.com/business/currency/silicon-valley-has-an-empathy-vacuum">lack of empathy</a> in tech and the Valley, so the question is how do we inject that? And not as a checkbox on a mission statement exercise, but in the daily behaviors of an organization.</p><p>Product management is known to be a critical role. Clearly the senior leadership has an outsized role in setting the vision and mission of the entire organization, but making a difference doesn’t need to wait for the CEO. Because product is the intersection of so many critical processes, it provides a unique opportunity to compel these discussions.</p><blockquote><strong>Responsible product management</strong> can be embraced at all levels to help make products that both wow existing target customers <em>and</em> better meet our collective goals as a society.</blockquote><p>That doesn’t mean any of this is easy. I don’t have the answer on what questions, metrics and processes would be the best foot forward here. As an example, I’m sure the Facebook team had some discussion on the pros and cons of the Safety Check feature. Yet like many Facebook decisions that increase ‘user engagement’, there have been<a href="https://techcrunch.com/2017/06/14/facebooks-safety-check-is-a-stress-inducing-flip-of-social-norms/"> externalities and controversies</a>.</p><p>But this is important enough to work through the difficulties. Marketing doesn’t guarantee revenue and profits, but that doesn’t mean we don’t spend a lot of time and effort on it. Likewise, we won’t change the world with an extra sentence in the next <a href="https://medium.com/search?q=what%20do%20product%20managers%20do">‘what do product managers do’ article on Medium</a>, but damned if we shouldn’t try.</p><p><strong>What do you think?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20de1b36591c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productmaven/forget-vcs-founders-do-product-managers-have-an-obligation-to-a-greater-good-20de1b36591c">Forget VCs &amp; Founders: Do Product Managers Have an Obligation to a Greater Good?</a> was originally published in <a href="https://medium.com/productmaven">ProductMaven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Target Your Product Resources in 4 Steps: How to Run a Blueprint Session]]></title>
            <link>https://medium.com/productmaven/target-your-product-resources-in-4-steps-how-to-run-a-blueprint-session-7723c357092b?source=rss-921871c106a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7723c357092b</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Chris Rosenbaum]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 18:40:36 GMT</pubDate>
            <atom:updated>2017-09-27T20:44:20.353Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xl_d7v2MQ13ENexf-jgdAw.jpeg" /></figure><p>Theory is all well and good, but sometimes you just need action. You don’t want to have to chart the stars to get yourself to the grocery store, so you pull up Google Maps. Directions on demand, mission accomplished.</p><p>In that vein, we often get questions about our work in product operations along the line of: “okay, maybe this sounds reasonable, but now what?”</p><p>So here I’ll share with you the abridged playbook of what we do when we’re working with a new team and we’re trying to unearth the hidden potential (what I’ve previously called the <a href="https://daks2k3a4ib2z.cloudfront.net/59abec8c7ba7940001073f1e/59b297d6acb83800019e48b6_Product%20Blueprint%20intro.pdf">points of maximum leverage</a>).</p><h3>60-second overview</h3><p>The deck below walks you through the entire process, but in a nutshell there are four steps:</p><ol><li>Understand the playing field</li><li>Assess the conditions</li><li>Project the opportunity</li><li>Act</li></ol><p>Again, our key thesis in product operations, and the very point of the Product Blueprint, is that often the forest is lost through the trees. An over-emphasis on tactics and frequent shifts in focus are a chronic distraction from root causes and bigger needs.</p><p>Therefore, the ‘playing field’ zooms out. It is a holistic view of everything that can impact our ability to ship awesome products. We built the Blueprint for this purpose because the other frameworks we’ve used fail to give full credence to both technical <em>and</em> human factors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlJ0PNwd6YdUK8XkZpkTeA.png" /></figure><p>From there, the engagement happens. You’ll want as many team inputs as possible from diverse points of view. To facilitate this, our deck includes both 1) twenty question prompts to guide a rich discussion of the playing field and 2) a link to an online survey tool that can kick start the process in just ten minutes.</p><p>Next is the prioritization of topics that your team agrees have potential for improvement. We recommend an impact / effort matrix. For each deficient discipline, you compare the impact that significant improvement would have on your product capability against the effort that this improvement would require in time, cost and difficulty (likelihood of success). We provide a template tool for that in the deck as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*QQ3fv2H6s35n-_-Zd2Pp0Q.png" /><figcaption>An example of our impact/effort matrix in process</figcaption></figure><p>Finally, armed with a fresh view of your soup-to-nuts product ecosystem, you can address the high ROI topics with new confidence.</p><h3>Who’s this for?</h3><p>We’ve used this process with product influencers of all sorts: directors, CEOs, tech folks. Getting the dialog going is half the battle. Some tips:</p><p><strong>If you’re a business leader at the top of the org chart</strong> and you know your product isn’t hitting on all cylinders, this process will use the hive mind to give you the benefit of many brains and viewpoints in a candid appraisal of what’s working and what isn’t. That information can be powerful.</p><p><strong>If you’re a product or technology leader</strong>, this process can help identify ways in which you can better use those scarce resources or restructure processes and roles.</p><p><strong>If you’re in the midst of the product organization</strong>, you can use this tool yourself to develop your big-picture mindset and get a better idea of the challenges at the top of the org. Knowing the landscape can help you better position your requests successfully, or perhaps you can recommend this process as part of a grassroots effort.</p><p>Now get to work.</p><p><em>Download:</em> <a href="https://daks2k3a4ib2z.cloudfront.net/59abec8c7ba7940001073f1e/59cba9cad7d51800012f23e9_Product%20Blueprint%20session.pdf">How to Run a Product Blueprint Session deck</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*UN_OjFxRq81SOHAqzrrE9Q.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7723c357092b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productmaven/target-your-product-resources-in-4-steps-how-to-run-a-blueprint-session-7723c357092b">Target Your Product Resources in 4 Steps: How to Run a Blueprint Session</a> was originally published in <a href="https://medium.com/productmaven">ProductMaven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Job Posts Are Literally Preventing Great Hires]]></title>
            <link>https://medium.com/productmaven/why-your-job-posts-are-literally-preventing-great-hires-9d655bacee10?source=rss-921871c106a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d655bacee10</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[talent]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[job-posting]]></category>
            <dc:creator><![CDATA[Chris Rosenbaum]]></dc:creator>
            <pubDate>Tue, 19 Sep 2017 21:12:07 GMT</pubDate>
            <atom:updated>2017-09-19T21:25:35.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8C9-EYFSA3t2RSFNe13csw.jpeg" /></figure><p>My unscientific observation: <em>more than half of the time I see an employee underperform, I believe the match was doomed from the beginning.</em></p><p>It often comes down to two key issues: poor role design (a topic for another day) and/or an inferior candidate pool. That inferior pool is often the result of a fundamental misunderstanding of the role of the ‘job post’. Let’s rip apart the status quo, and then give you three tips to fix it.</p><h3>Good ‘nuff</h3><p>Hiring decisions are often (incorrectly) made on a relative rather than absolute basis. This means they pick from the best of the applicants at hand, and move on: similar concepts to ‘<a href="http://www.economist.com/node/13350892">satisficing</a>’ in economics and ‘local maxima’ in mathematics. If amazing candidates don’t even enter the view, the choice is inherently limited. Small teams and organizations are particularly susceptible to this as they’re often hiring the first, second or third instances of a role — as opposed to large orgs with dozens or hundreds — and lack the expertise and pattern matching to measure fit on a more absolute scale.</p><p>Therefore, even if the pool doesn’t include high-potential candidates, the role often gets filled anyway, and the hiring manager may never be the wiser. A particular candidate stood out from the rest, and we have the illusion of fit.</p><p>So what role do job posts play in the substance of that talent pool? They are a key part of the marketing funnel through which that pool is filled. There are obviously <em>many</em> ways to impact that pool: passive recruiting, adding sourcing channels, network node tapping, etc. But for today, let’s focus on the post.</p><h3>Who’s marketing to whom?</h3><p>Let’s think about the job seeker’s user experience for a second. Any look at a job board or job aggregator will show an endless stream of ‘opportunities’ (I use that world loosely). None of the major platforms have ever been able to significantly improve the searching process for a job seeker, so there’s still a lot of hunting. And reading. And clicking. It’s a low signal-to-noise ratio.</p><p>Additionally, in most markets, openings outnumber good candidates (let alone great candidates). Unless you have a clear hiring advantage — an amazing brand, world-class colleagues, huge pay premiums — then this supply/demand imbalance poses a disadvantage for you as the employer. But too often this critical realization doesn’t manifest in the recruiting effort.</p><p>A job post is a marketing piece in every sense of the word. The job of marketing is to sell, not dictate a dry list of tasks, requirements and other red flags of micromanagement. The obstacle here is that most businesses have the sale conceptually backwards: the job opening is a gift to the labor market, and great workers should run forth to pitch their goods. Lou Adler calls this mismatch a ‘talent surplus strategy’ for a <a href="http://www.greenhouse.io/blog/from-lou-adler-how-implementing-a-talent-scarcity-strategy-can-solve-your-common-hiring-problems">‘talent scarcity’ world</a>.</p><p>Here’s the reality:</p><p><strong>You are <em>selling</em> a role and you want great candidates to <em>buy</em>.</strong></p><p>Ignore this at your own peril. The key here is to really believe this (we’re not talking about the famous Dead Sea tupperware in Aladdin), and bake that mindset into the recruiting process from the get-go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/0*Cg6ql_P5PyQ2kNXR.jpg" /></figure><h3>‍Information Asymmetry</h3><p>When the PC market was first making the push into mainstream houses across the country, the selling criteria were a mish-mash of mHz and kilobytes. (I still remember the CircuitCity rep graciously down-selling us to the 129MB harddrive IBM PS2, because we “couldn’t possibly ever need 179MB of hard disk space”). The difference between the many components were often opaque to most consumers, who couldn’t really balance the trade-offs of RAM or GPU with the extra cost.</p><p><em>Intel Inside</em> was a brilliant marketing campaign for many well-documented reasons, rocketing a supplier of a tiny component of the overall system to a position of superior value capture in the PC supply chain, but a key reason was that it offered consumers a way to cut through the noise. <em>Intel Inside </em>became a signal of quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ly4YLhV8h9SFuJ3O.jpeg" /></figure><p>Let’s assume for a second that your role is already well-designed and presents a solid opportunity. The reality is that all the great things about your company, your team, the role and its potential that <em>you</em> know — the whole kit-n-kaboodle — is largely invisible to the job seeker. You have a few seconds to capture their interest, to motivate them to read deeper, and to earn consideration in their eyes. And the better the candidate, the higher that threshold of interest is.</p><p>In design and product management work, there is a great deal of emphasis on the user. Understanding the user journey, her pain points, her context, her feelings. Everything that falls in the bucket of ‘customer experience’ and ‘empathy’.</p><p>To reduce that information asymmetry, you need to signal quality in a way that matches the user’s needs. Job seekers aren’t out looking for a laundry list of qualifications. They don’t get jazzed reading a dozen daily tasks. Your internal acronyms and pleadings for ‘self-starters’ and ‘fast-learners’ are better at getting eye rolls than quality applications.</p><h3>‍Job posts to upgrade that candidate pool</h3><p>Let’s bring this full circle with how you can quickly improve your job posts.</p><h4>‍Step 1: Flip your marketing mindset</h4><p>Internalize who’s selling to whom in the recruiting process. Again: <em>You are selling a role and you want great candidates to buy.</em> This mental shift means you won’t take candidate quality and volume for granted anymore. If you don’t believe this, the rest is doomed.</p><h4>Step 2: Become your user</h4><p>Go through the exercise of pretending to be a qualified candidate. No, aim higher: a great candidate, already happily employed elsewhere. What would that person need to see in a role to classify it as a career opportunity? This will have one of two results:</p><p>1) You’ll realize it’s not a career opportunity for quality folks, and you’ll need to rethink the role design. This means a lot more work, but it’s better now than later.</p><p>2) You’ll see specific growth opportunities and challenges that would excite that candidate, and this will be the start of your job post.</p><h4>Step 3: Focus on outcomes</h4><p>Good performers are goal-driven (and great ones are systems-focused to get to those goals). Rather than micromanage in advance with a mundane list of tasks, your job post should focus on the outcomes of excellence in the role. What does the successful product launch look like? After a year what does great division growth look like? It’s the framing of the work and the allowance for the candidate’s own expertise creativity that will stand out from the crowd.</p><p><em>(Bonus: When posts focus on outcomes and not on tactics, the interviews can be engaging dialogs of co-creation of how to approach these problems, rather than assuming you know the answers and are waiting for the right candidate to validate your existing thinking.)</em></p><p>‍There are many moving parts and tough work in hiring great people. But with these three concepts, you’ll hopefully be able to write job posts in a new, empowered way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d655bacee10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productmaven/why-your-job-posts-are-literally-preventing-great-hires-9d655bacee10">Why Your Job Posts Are Literally Preventing Great Hires</a> was originally published in <a href="https://medium.com/productmaven">ProductMaven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Cooking Dinner Can Teach Us About Great Product Leadership]]></title>
            <link>https://medium.com/productmaven/what-cooking-dinner-can-teach-us-about-great-product-leadership-9d0941cd692c?source=rss-921871c106a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d0941cd692c</guid>
            <category><![CDATA[product-team]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cooking]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-blueprint]]></category>
            <dc:creator><![CDATA[Chris Rosenbaum]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 21:51:00 GMT</pubDate>
            <atom:updated>2017-09-12T12:51:04.347Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Cooking Dinner Can Teach Us About Great Product Leadership</h3><p>A delicious introduction to the notion of product operations and how it can focus your resources.</p><p><em>Joint post by </em><a href="https://medium.com/u/ad4c770478ec"><em>Ryan Troll</em></a><em> &amp; </em><a href="https://medium.com/u/921871c106a2"><em>Chris Rosenbaum</em></a><em>, ProductMaven founders, part 1 of 2</em></p><p><strong>Let’s Eat</strong></p><p>Half the reason I picked my new apartment is the killer kitchen it has. Cooking = yes please. What some people find to be tedious extra work brings me energy and creativity. Over the last fifteen years I’ve worked my way from lowly microwave jockey to a middling captain of the kitchen, even entrusted last year with our wedding registry (much to my wife’s delight).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*hxfWgfn1Ed2AvwDU." /><figcaption>In the heat of battle a kitchen may look like chaos, but it’s often carefully orchestrated</figcaption></figure><p>Cooking easily lends itself to analogy, invoked to explain everything from <a href="https://www.eaglegenomics.com/how-successful-bioinformatics-is-just-like-cooking-review-of-eagles-4th-annual-symposium/">bioinformatics</a> to the Boston Celtics (by Kevin Garnett, not <a href="https://deadspin.com/5867805/kevin-garnett-made-one-hell-of-a-cooking-metaphor-today">once</a> but <a href="https://nesn.com/2013/02/kevin-garnett-uses-cooking-analogy-to-explain-how-celtics-need-to-be-less-lackadaisical-without-rajon-rondo/">twice</a>). Over the chopping board or the stovetop, the mind can wander. While this sometimes leads to a botched plate of food, it can also lead to interesting insights. My most recent recipe? How to use the concept of the kitchen to serve up awesome products.</p><p>In organizations from start-ups all the way through large corporations, we often hear concern about what we call surface issues: insufficient resources, lack of customer data, inefficient development efforts, and so forth. These are indeed real problems, but are often symptomatic of something deeper. While a good doctor will certainly try to provide immediate relief, her greater attention turns to treating the underlying cause.</p><p>When we get down to brass tacks, more often than not, one of two issues comes to light: 1) improperly focused resources or 2) lack of broader organizational buy-in for more resources. These are not sexy topics when compared to exciting new roadmap platforms or customer insight panels, but this is where the gold is mined. Let’s head back to the kitchen to understand.</p><p>Many diners may think that a top-notch meal is the result of superior skill, from a chef who commands a wide array of techniques from poach to sear, from flambé to sous vide. But a litany of cooking tactics alone will produce nothing: preparation, context, quality ingredients, measurement and emotion all work together to yield tasty dishes. Which skill, why, and when, matters. And so it is in product management, the value of of the big picture and explicit broad coordination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u1uqoTVt4qCvFgB-." /></figure><p>One of the most critical principles for any chef is that of <em>mise en place</em>. This French culinary concept means “putting in place” or “everything in its place” and is completed before any cooking begins. Tools, ingredients, and layout are all reviewed and organized in advance, so that once the heat is turned on the difficult work can be as efficient and focused as possible. In a restaurant kitchen with many staff, this means everyone involved has full view of what, why and when things will be done so that they can collectively run like a finely oiled machine.</p><p>So what’s the punchline here? Product management is a complex organism that is often running at a thousand miles per hour to keep up with business goals. This leads to an understandable but problematic over-focus on execution and tactics at the expense of deliberate review of what tactics are truly worthy of such focus. You can whip up an amazing sauce for a meal or put together a beautiful plating, but if you didn’t season the meat or thaw it out in time, the result will be unfortunately mediocre.</p><p><strong>Product Management is a Hungry Beast</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*ZJlCyH0zMfgWGV3R2dDOYg.gif" /></figure><p><em>Do our processes improve our products or do they hinder them? Is the product team collaborating effectively with other parts of the business? Is our organization really embracing and enabling our product strategy?</em></p><p>These and many other questions have kept Ryan and countless other product leaders up late at night over the years. They are all riffs on the same theme: <strong>what’s next?</strong> (or an even more exasperated <em>where do I begin??</em>)</p><p>There is a tool, platform, API, blog or opinion available for every concept under the sun, yet these questions persist. This breadth and volume can itself be a distraction from paradox of choice. Either way, the prevailing feeling is a lack of fulfilling progress. According to product managers surveyed in Alpha’s annual<a href="http://insights.alphahq.com/hubfs/Content/2017%20PM%20Insights.pdf"> product management insights report</a>:</p><ul><li>58% believe they don’t spend enough time on their product roadmap,</li><li>76% believe they don’t spend enough time talking to customers, and</li><li>80% believe they don’t spend enough time running product experiments.</li></ul><p>This product FOMO likely drives the desire for more support:</p><ul><li>67% cite either lack of resources or internal politics as their biggest internal challenge</li><li>1 in 3 product leaders cite ‘additional resources’ as their #1 wish</li></ul><p>That’s a lot of grasping for more. How do we address this?</p><p><strong>The Internal Ecosystem of Product Operations</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*WC02tBQ3Th5CqUiakYIB5Q.jpeg" /></figure><p>As we mentioned before, we believe these circumstances to be endemic of a deeper ailment. Since the C-suite isn’t likely to start doubling budgets for fun any time soon, let’s hold constant the overall organizational allotment of resources. In this world, there is only one way for product leaders to drive progess on the current strategy: reallocate. This reallocation can take place within the product team, moving time and attention from lower- to higher-ROI activities, or at the organizational level, convincing leadership to shift resources from other corners of the company into product-related endeavors.</p><p>This need to look holistically at product from both a siloed and organization-wide view, and from both a process and a human view, has led us to the notion of <em>product operations</em>. Pondering dozens of phrases to communicate our thesis, we found nothing else that can, as simply and succinctly, capture the aggregated conditions that lead to the output of your goods &amp; services. Fundamentally different from frameworks like Pragmatic Marketing or SiriusDecisions PMM, product operations represents the critically connected network of human and technical processes.</p><p>Much like in traditional operations, we take the view that the identification and alleviation of bottlenecks is a core goal of a product leader. When product managers are sometimes (controversially) depicted as mini-CEOs of their products, the attempt is to recognize the competing needs a PM juggles: many stakeholders, customer-facing, profitability, etc. When we move beyond <em>management</em> and look at product <em>leadership</em> in a company, we believe these individuals must also utilize the mindset of a COO. Resource-focused and portfolio-minded, the in-the-weeds COO-like product leader will ruthlessly uncover any process or environmental variable that blocks the creation of incredible products. So what’s the blueprint for this approach?</p><p><strong>In Search of Product’s Lingua Franca</strong></p><p>Our question of obsession has been how to better equip product teams to align stakeholders and focus their resources on important product development activities. Coalescing our thoughts under the umbrella of product operations has given us an operating model that our customers use to 1) educate stakeholders about product, 2) improve the focus and utilization of product resources, and 3) drive greater collaboration across the product function.</p><p>Product does not exist in a vacuum, and the two-way interplay between the broader organization and the product team is of massive importance. Having a unifying conversation on common terms sounds overly simple but is of astounding value. It’s looking at your charts before you set sail. Admittedly, there are a million ways to slice &amp; dice this, but half the battle is simply having a common touchstone for team conversation and collaboration.</p><p>We’ve recently created the Product Blueprint to serve this purpose. Our goal is specifically not to provide a monolithic approach, a “this is how you manage product” dictum. We believe there is no one-size-fits-all tactical approach. What works for one team will almost certainly not work for the next team, and thus in the aggregate we are tactic-agnostic. Rather, we see the value in providing the ‘rails’ in which the review and adoption of product management practices can take place inside an organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*HGlOSkKvNpqQy3Ru_sTcRg.png" /></figure><blockquote>Product is like a train, and product operations are the rails.</blockquote><blockquote>Your product can only go places your organization is ready to take it.</blockquote><p><strong>The Product Blueprint</strong></p><p>When we work with a new product team, we always begin with triage. Over time, we have given that process more structure, seeking evidence of particular principles and methods in play. We will go into detail in our next article, but as an overview the Product Blueprint organizes our practices (currently 66 of them) into disciplines (19), which are then bundled into five core areas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*m3g46DriXLU3JVJwOzxK-A.png" /></figure><ul><li><strong>Environment</strong>: The human factors and interactions that define the organization and determine its potential</li><li><strong>Organization</strong>: The ways in which the organization structures, coordinates and enables its people and resources</li><li><strong>Discovery</strong>: Practices that reveal market opportunities and drive the direction of the product</li><li><strong>Execution</strong>: Core processes to design, deliver and maintain the product</li><li><strong>Go To Market</strong>: The preparations and tactics that launch and support successful adoption of products</li></ul><p>We term the lower two areas (Environment &amp; Organization) ‘foundational’, indicating their broad and critical impact on the conditions that allow for the work of great product to come forth. The other three areas (Discovery, Execution and Go To Market) loosely represent the full ‘lifecycle’ of product and the many tools and techniques used throughout. In tandem, these complementary perspectives provide a structure that can reveal the right mix of people, practice and technology for a winning product strategy.</p><p><strong>The dinner bell ringeth</strong></p><p>We’ll share more in the days and weeks ahead, including details on the model, a free assessment tool to benchmark your product operations, and a guide to running Product Blueprint sessions. Our initial goal is to share our work and begin a conversation.</p><p>With a meal, there can be debates over the use of a particular spice or the time and temperature of the heat, but the value is in getting everyone to the table for a wholesome meal and good conversation. We know our view on product operations and the Product Blueprint approach is not the final word on anything, but we hope it provides something interesting to chew on and starts a conversation in your product kitchen.</p><p>Bon appétit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*kJ-kQPwWZjIne2BkP76jkw.jpeg" /></figure><p><em>Check out </em><a href="http://www.productmaven.co/"><em>productmaven.co</em></a><em> if you want more details right away…</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d0941cd692c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productmaven/what-cooking-dinner-can-teach-us-about-great-product-leadership-9d0941cd692c">What Cooking Dinner Can Teach Us About Great Product Leadership</a> was originally published in <a href="https://medium.com/productmaven">ProductMaven</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>