<?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[Colorado Product - Medium]]></title>
        <description><![CDATA[Establishing Colorado as the epicenter of exceptional product management practice and thought-leadership. - Medium]]></description>
        <link>https://medium.com/colorado-product?source=rss----25db5e98cbfd---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Colorado Product - Medium</title>
            <link>https://medium.com/colorado-product?source=rss----25db5e98cbfd---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:42:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/colorado-product" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Using Lean Canvas in (Agile) Epics]]></title>
            <link>https://medium.com/colorado-product/using-lean-canvas-in-agile-epics-3ed31718100c?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ed31718100c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[lean-canvas]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Michael Lynch]]></dc:creator>
            <pubDate>Tue, 01 Mar 2016 20:13:11 GMT</pubDate>
            <atom:updated>2016-03-03T05:54:42.441Z</atom:updated>
            <content:encoded><![CDATA[<h4>A novel approach to utilizing Lean Canvas within Epics in an Agile methodology</h4><p>Most of us in product / engineering organizations within software companies evolved into Agile development life-cycles over the past ten to fifteen years. Most of us started out pretty straightforward applying the basic Agile Manifesto probably combined with a Scrum foundation. Of course, many offshoots and variations emerged and even still younger compliments to Agile continue to emerge, such as Lean Canvas, Lean MVP and others.</p><p>I’ve been finding reasons to apply Lean Canvas and MVP approaches for the past five years and have had some interesting successes and failures. This blog post presents one recent success using Lean Canvas, but in what might be a unique and helpful variation for your organization.</p><p>At Envysion, Inc., we were exploring the Lean Canvas, er, <a href="http://leanstack.com/">canvases</a> approach, as well as following advice from the <a href="http://www.svpg.com/">Silicon Valley Product Group</a>. This meant we were filling out canvases for specific product lines or new product feature groups. We found Lean Canvas and Lean MVP are designed for smaller software projects and are ideal for the first generation (MVP) of a product. For a more mature product company (Envysion is a 100-person company with over a hundred enterprise clients and tens-of-thousands of enterprise end-users), the approach can be somewhat lacking.</p><p>Then one of our thoughtful and innovative product managers had an interesting idea: Use the Lean Canvas structure essentially as the “body” of Epics (and/or Initiatives). Here’s how it worked…</p><h4>Background</h4><p>Within our Agile methodology, we adhere to the approach that <strong>Themes</strong> beget one or more <strong>Initiatives</strong> which beget one or more <strong>Epics</strong> beget one or more <strong>Stories</strong> beget one or more <strong>Activities</strong>. There is always more work than we can possibly address within a quarter (our planning extends out six quarters at the moment). If we apply the Lean Canvas approach to feature groups, we’d be writing a lot of Lean Canvases. That’s not necessarily a bad thing, really, but combined with the fact we also have to write a lot of Initiatives and Epics, it adds up to a lot of time we don’t have.</p><p>When writing Initiatives and Epics, we were following the general approach that you might learn from an Agile coach or through your own experience of writing requirements and Stories and such over the years (As a… , I need… so that). We were consistently providing context and background, a description of what the problem is, how we might want to solve it and what benefit our customers might gain from the result. One of our product managers realized this approach encompassed most of the aspects of a Lean Canvas. In an effort keep our Initiatives/Epics short-and-sweet, we decided to migrate to the Lean Canvas approach, but still provide a consistent structure of information to the reader.</p><h4>Execution</h4><p>We now simply apply the Lean Canvas structure to every Initiative and Epic. There are a few slight variations of the Lean Canvas format out there (and no real standard, yet) but the one we adopted looks like this, which each of these bullets representing a section that is no more than one or two sentences or a short bullet list…</p><ul><li>Problem</li><li>Existing Alternatives</li><li>Solution</li><li>Key Metrics (of successful Solution)</li><li>Unique Value Proposition (of our Solution)</li><li>Unfair Advantage (of our Solution)</li><li>Channels to Market</li><li>Customer Segments (including Early Adopters identified)</li><li>Cost Structure / Considerations (which we measure in Points or “Organizational Dollars”)</li><li>Revenue Model / Potential</li></ul><h4>Results</h4><p>The results have been pretty impressive, substantive and immediate:</p><ul><li>These turns out to be <em>very fast to write</em>, once you get the hang of it. It takes a little training, which you can find online in a few blogs easily one good resource from starlit.rs is here: <a href="http://coloradoproduct.com/wp-content/uploads/2015/06/LeanCanvas.pdf">LeanCanvas</a>), your product managers will get it quickly.</li><li>Engineering and marketing seem to love it as well, so much so we’ve seen other organizations start to use the basic canvas template for their own department’s work.</li><li>It also seems to help the scoping of the child Stories within those Epics quite a lot, which Engineering also loves.</li><li>The learning curve of new product managers and engineers is shortened, and the transition time is shortened if we move a product manager to a different product.</li></ul><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/06/using-lean-canvas-in-agile-epics/"><em>coloradoproduct.com</em></a><em> on June 9, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ed31718100c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/using-lean-canvas-in-agile-epics-3ed31718100c">Using Lean Canvas in (Agile) Epics</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM Podcasts]]></title>
            <link>https://medium.com/colorado-product/pm-products-4553473b63de?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/4553473b63de</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Alex Haar]]></dc:creator>
            <pubDate>Tue, 01 Mar 2016 03:01:29 GMT</pubDate>
            <atom:updated>2016-02-27T16:42:53.682Z</atom:updated>
            <content:encoded><![CDATA[<p>Podcasts are here to stay, and here are a few podcasts that hit on the subject of product management and startups.</p><p><strong>Intercom</strong></p><p>Read their <a href="https://www.intercom.io/books/product-management">book</a>, read their <a href="https://blog.intercom.io/">blog</a>, listen to their <a href="https://blog.intercom.io/tag/podcast/">podcast</a>. These folks really get product management and they can articulate both the strategic and tactical aspects in a wonderfully clear and actionable manner.</p><p><strong>This is Product Management</strong></p><p>Alpha UX created this <a href="http://www.thisisproductmanagement.com/episodes/">podcast</a> to cover the many different disciplines relevant to today’s product managers. As described by them, they take a “deep dive into user experience, statistics, innovation, differentiation, design, development, metrics, and more.”</p><p><strong>Product Hunt Radio</strong></p><p>Product Hunt is a place to find new &amp; interesting products, curated by the people who are passionate about products &amp; technology. Product Hunt Radio is founder Ryan Hoover’s <a href="http://www.producthunt.com/radio">podcast</a> where he “geeks out” about products with the people who create them.</p><p><strong>Product People</strong></p><p>Justin Jackson stays quite busy. Don’t believe me? Check out his <a href="http://justinjackson.ca/about/">profile</a>. One of his newer projects is the <a href="http://productpeople.tv/">Product People podcast</a>. Justin has a wide variety of interesting guests, including Nir Eyal (author of <a href="http://www.amazon.com/Hooked-How-Build-Habit-Forming-Products-ebook/dp/B00HJ4A43S">Hooked</a>) and Samuel Hulick (creator of <a href="http://www.useronboard.com/">User Onboard</a>).</p><p><strong>The Rocketship Podcast</strong></p><p>While not strictly about product management, <a href="http://rocketship.fm/">this show about startups</a> covers many topics relevant to product managers. There are tons of great episodes to listen to with great topics ranging from “Your Strategy is Your Story” to “Customer Interviews Done Right”.</p><p>Did we miss any podcasts you love? Let us know in the comments. You can also find a much longer list of PM resource recommendations <a href="https://medium.com/art-marketing/a-living-list-of-product-management-resources-c5dddbff8b12">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4553473b63de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/pm-products-4553473b63de">PM Podcasts</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Path to PM: Michael Lynch]]></title>
            <link>https://medium.com/colorado-product/path-to-pm-michael-lynch-e168055492f4?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/e168055492f4</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Michael Lynch]]></dc:creator>
            <pubDate>Fri, 05 Feb 2016 17:52:28 GMT</pubDate>
            <atom:updated>2016-02-05T17:47:26.935Z</atom:updated>
            <content:encoded><![CDATA[<p>Breaking into a product management career can be a challenging endeavor and the “best” or most “straightforward” method to do so is largely undefined. Product Management is often referred to as a role that is learned through experience rather than taught in the classroom. “Path to PM” is a blog series highlighting the many diverse, interesting and unique paths the writers have taken to become a Product Manager.</p><p>Michael Lynch is Vice President of Product at Envysion and a member of the leadership team of <a href="http://www.coloradoproduct.com/">ColoradoProduct</a>. Michael’s product management career spans successful start-ups and large corporations in multiple countries including Switzerland, The Netherlands and Saudi Arabia. Michael holds a B.B.A. in International Economics and Management Information Systems from the University of Oklahoma and the Hochschule für Ökonomie in Berlin.</p><p>Like most, my path to product management was a surprising path, at least surprising to me. As a 16-year old, I was sure I would be making movies for a living. As a former 16-year old, I now realize I’m doing what I was meant to do.</p><p>There are four threads I can follow back through my early years:</p><ol><li>Innate fascination with products and technology</li><li>Entrepreneurial spirit</li><li>Wanting others to find value through my products</li><li>Maker mentality</li></ol><p>As a kid, I disassembled every ‘dead’ electronics device within hours of its demise. My family suggests this was my basis of wanting to understand ‘how things worked’, which is one central ingredient, I believe, in having a natural tendency toward being a product manager.</p><p>In Middle School I would buy large 50-count bags of <a href="http://en.wikipedia.org/wiki/Hubba_Bubba">Hubba Bubba </a>for a couple bucks and sell individual units to fellow students at $0.5o a pop. I was providing a valuable product at a reasonable price. The school, however, disagreed and my budding business was banned after only two short weeks.</p><p>The third thread is best summarized by an incredible engineer and friend — Vince — who I was trying to retain with additional money during one of our startup’s downturn during the first bubble-burst. Vince told me “<em>It’s not about the money. What I care about most is that the stuff I write gets used by real people…that it doesn’t end up on a shelf somewhere…and, that users get real value from using it.</em>” Knowing I am creating real value for customers is what keeps me interested and dedicated to an effort. It’s how I’m wired. I have to <em>know</em> the true value of my product.</p><p>A fourth element that drove me to product management is a need to <em>create</em> things. Whether it be art, music or software, the best product managers are creative and have a desire to build things.</p><p>So how did these four innate drivers influence my life in a way I couldn’t control?</p><p>First was college. What would a person with these interests study at university? Depends on who is paying. Since my parents, scholarships and the US government were all paying I decided a Fine Art degree with a major in Film Production was the obvious choice. My mother was on-board… with one caveat: I double-major in business and/or engineering. Seemed like a fair compromise. During my sophomore year I did an internship at McCaw Cellular (later acquired to become AT&amp;T Wireless). Seeing that their sales folks were still calculating commissions on paper, I found it fun to write a commissioning app. I did it for fun. It was a hit in the local office, then adopted regionally and then finally nationally. Two key takeaways for me: 1) that was a lot of fun!; and 2) I realized I created a lot of value — but just wasn’t compensated for it very well.</p><p>My first real job after college was working for Morris Information Systems. They needed someone young, unmarried and slightly crazy to open the first <a href="https://en.wikipedia.org/wiki/NeXT">NeXT VAR</a> in the Middle East. At the same time, M.I.S. was building custom client/server software for Saudi Aramco. Before I knew it, I was managing a dozen engineers in Saudi Arabia, representing Steve Jobs’ new company and convincing the COO of Saudi Aramco to build an oil trading app on the NeXTstep platform (at a time when Sun Microsystems was the only game in town). This experience gave way to a few key takeaways:</p><ol><li>This also was a lot of fun!</li><li>Understanding and guiding your customer is fundamental to success.</li><li>If you dream big, you can represent a small boutique custom software shop and get a deal with one of the largest, multi-billion dollar companies on the planet.</li></ol><p>While in Saudi Arabia, I met someone who would become my business partner (here in Boulder, Colorado) across two venture-funded startups and two corporate-funded autonomous organizations. He gave me the opportunity to be an equity shareholder on the ground floor of the two start-ups and the role of “owning the product.” From there, it was off to the races — building, making and trying my best to focus on providing value.</p><p>Over the next ten years we built the first organization dedicated to object-oriented client/server applications within SHL Systemhouse, partnered with NeXT Computers, Inc. to help bring client/server apps to the emerging World Wide Web, sold the company to MCI and then created the same exact thing all over again for Swiss Bank in Zürich. In 1995 we got the chance to build our very first, fully-owned start-up, Avolent, Inc. (after three name changes and one merger) and our first true “Internet application” product, an electronic bill presentment and payment platform we sold to MCI, Wells Fargo, OfficeMax and many others. Over this period, as we grew from seven founding members to over a hundred employs, I learned more about product management and building a business than I could have ever hoped. The key takeaways are too many to count, but all of them point back to those same key early drivers.</p><p>These forces are irresistible and highly rewarding emotionally. I would sum them up as…</p><p>1) a desire to understand ‘how things work’</p><p>2) a need to be creative and to ‘create things’</p><p>3) a desire to provide real value to customers (as affirmed by <em>them</em>)…</p><p>4) …and make money while doing it as a real business</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/09/path-to-pm-michael-lynch/"><em>coloradoproduct.com</em></a><em> on September 10, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e168055492f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/path-to-pm-michael-lynch-e168055492f4">Path to PM: Michael Lynch</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New locations, expanded mission, amazing impact — Announcing Colorado Product!]]></title>
            <link>https://medium.com/colorado-product/new-locations-expanded-mission-amazing-impact-announcing-colorado-product-e69e9eeb2e3f?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/e69e9eeb2e3f</guid>
            <dc:creator><![CDATA[Adam Tornes]]></dc:creator>
            <pubDate>Sun, 31 Jan 2016 17:47:50 GMT</pubDate>
            <atom:updated>2016-01-31T17:47:37.019Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we are incredibly excited to announce the launch of <a href="http://www.coloradoproduct.com/">Colorado Product</a>, a professional organization, founded with a goal of establishing Colorado as <em>the</em> hub of product management! Our vision, is to establish Colorado as the epicenter of exceptional product management practice and thought-leadership. Formerly the <a href="http://www.meetup.com/Colorado-Product/">Boulder Product Meetup</a>, <a href="http://www.coloradoproduct.com/">Colorado Product</a> was built to extend the reach and impact of that organization; founded with the goals of building a strong network of local product managers and facilitating their ongoing development through educational and professional development opportunities. <a href="http://www.coloradoproduct.com/">Colorado Product</a> seeks to do the same and more for the flourishing tech communities across Colorado by providing great content, networking, and professional development opportunities.</p><p>We’re also stoked to announce that the former <a href="http://www.meetup.com/Colorado-Product/">Boulder Product Meetup</a> is expanding to Denver as part of Colorado Product! We’re focused on bringing valuable educational and networking Product events to Denver and further developing and strengthening that community. We’ve learned in the past year that Denver is lacking these Product Management-oriented events and a tight-knit network of PMs; which were also lacking in Boulder when we started the <a href="http://www.meetup.com/Colorado-Product/">Boulder Product Meetup</a>. We’ve heard repeatedly the strong demand for product management support and we’re here to help!</p><p>The <a href="http://www.meetup.com/Colorado-Product/events/221179265/">first Colorado Product Meetup — Denver</a> will take place on April 2nd at the brand new Full Contact office, where <a href="http://www.meetup.com/Colorado-Product/events/221179265/">Adit Vaidya, PM of Facebook Groups</a>, will be sharing the lessons he’s learned when building software specifically for B2B Mobile, for Marketplaces, and what to consider when it’s time to take your software international. Prior to Facebook, Adit worked as a Product Manager at Eventbrite and PayPal where he built monetization features for small businesses.</p><p>Colorado is home to incredible product ideas and hugely successful product companies — factors evidenced in a <a href="http://www.builtincolorado.com/2015/01/28/report-colorado-tech-companies-raise-758m-and-exit-more-11b">recent report from BuiltInColoado</a>. Colorado tech just had its best year yet with $758MM in new funding and producing more than $10.9B in exits — and its just getting started. Colorado Product hopes to help continue this growth and these successes. We’re not consultants looking for our next opportunity, we’re not even Product Management <em>experts</em> -nor do we pretend to be — we’re Product professionals that are rooted in, invested in and are passionate about the Colorado tech community and the vision/mission of Colorado Product. While made in America may not mean what it used to, Built in Colorado sure does!</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/03/announcing-colorado-product/"><em>coloradoproduct.com</em></a><em> on March 16, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e69e9eeb2e3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/new-locations-expanded-mission-amazing-impact-announcing-colorado-product-e69e9eeb2e3f">New locations, expanded mission, amazing impact — Announcing Colorado Product!</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building solutions versus solving problems]]></title>
            <link>https://medium.com/colorado-product/building-solutions-versus-solving-problems-ceb8119aea13?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/ceb8119aea13</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kyle Weiss]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:30:04 GMT</pubDate>
            <atom:updated>2016-01-26T04:30:04.273Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a solution is the same thing as solving a problem right? You need to build a solution to solve the problem, there is no way to solve the problem without building a solution!?</p><p>Wrong.</p><p>At many organizations, product teams are branding themselves as the team who is focused, almost exclusively, on building a solution. They are focusing department goals around building solutions to problems the business has a core competency in solving. This sounds terrific in theory — we are solving a problem by building a solution in a market, we are experts in, while focusing on our competitive advantages. We have taken into consideration our competitors and we have a value prop that is unique differentiated. The real focus needs to be on solving the problem, not building the solution.</p><p>The problem comes from the idea that the only way to solve a problem is to “build” a solution. Perhaps you have heard of this example, NASA set out to solve the problem that current pens didn’t work in space. They spent millions to have a pen built that would function in a zero gravity, low temp environment. The Russian cosmonauts on the other hand simply brought pencils and avoided the millions in R&amp;D. Though this story is <a href="http://www.scientificamerican.com/article/fact-or-fiction-nasa-spen/">not</a> <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0CB4QFjAAahUKEwiEtvnvhKnHAhUGCpIKHYpnBBo&amp;url=http%3A%2F%2Fwww.snopes.com%2Fbusiness%2Fgenius%2Fspacepen.asp&amp;ei=Qh3OVYSNOIaUyASKz5HQAQ&amp;usg=AFQjCNF-WPAdGUbf2qk48UBFi9O_HSuvbg">actually</a> <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=4&amp;cad=rja&amp;uact=8&amp;ved=0CDUQFjADahUKEwiEtvnvhKnHAhUGCpIKHYpnBBo&amp;url=http%3A%2F%2Fwww.thespacereview.com%2Farticle%2F613%2F1&amp;ei=Qh3OVYSNOIaUyASKz5HQAQ&amp;usg=AFQjCNEdlQTG1EyJeBRd0M5Qo_5kRATyoQ">true</a>, the principle rings true and is very often lost among product managers.</p><p>There is a large pressure to find the next billion dollar idea and to build a solution which will solve or up-end a market or solve a problem the world didn’t even know it had! This is a noble feat to undertake, just make sure you are focused on solving the problem and not building a solution. Hulk Hogan endorsed a “<a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=10&amp;cad=rja&amp;uact=8&amp;ved=0CEcQtwIwCWoVChMIgqGrtIipxwIVin6SCh3c9AgW&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIheVRJkROxQ&amp;ei=9yDOVcLJJ4r9yQTc6aOwAQ&amp;usg=AFQjCNHwO9EMofMIweqOfSuA33iVVyb99Q&amp;bvm=bv.99804247,d.aWw">solution</a>“, while George Foreman endorsed a <a href="https://en.wikipedia.org/wiki/George_Foreman_Grill">product that solved a problem</a>. Homeland Housewares (and others) would later iterate on the Hogan endorsed product, and they actually were able to solve a problem with the new design. The point is, really evaluate a problem and make sure your solution solves the problem, don’t just build a solution — solve the problem.</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/08/building-solutions-versus-solving-problems/"><em>coloradoproduct.com</em></a><em> on August 14, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ceb8119aea13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/building-solutions-versus-solving-problems-ceb8119aea13">Building solutions versus solving problems</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role of a Director of Product Management]]></title>
            <link>https://medium.com/colorado-product/the-role-of-a-director-of-product-management-aaaefd43d2be?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/aaaefd43d2be</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kyle Weiss]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:28:48 GMT</pubDate>
            <atom:updated>2016-01-26T04:28:47.538Z</atom:updated>
            <content:encoded><![CDATA[<p>We continue our series on <em>Product Roles</em> and how each role varies, while focusing on the work each Product role can play in an organization. Please keep in mind, product team’s responsibilities can be highly varied. Some organizations have parsed these job functions to other roles, sometimes across departments. The success of that parsing will vary from company to company. In this series, we will focus on what we feel the roles entail in a “typical” product organization.</p><p>In this third post of the series, we dive into the<strong> Director of Product Management</strong> role.</p><p>From our first post in the series:</p><blockquote><strong><em>Directors of Product Management</em></strong><em> look after the business of product management. They usually help oversee the cohesion of multiple product/service verticals and they should be the guiding light on the process and tools used to report the product team’s direction. They are the stabilizing and negotiating hand that ensure teams are operating with synergy. They know when to step in to support a Product Manager and they, most importantly, know when to step back from the Product Manager to let her flourish.</em></blockquote><p>These people have two essential responsibilities. First, they must build a strong team of product managers. Second, they may be responsible for the company’s overall product strategy (if there is no VP) and more commonly, they oversee various products in the company’s portfolio.</p><p>The director of product management is really an enabler, mentor and one who often brings process. Their job is to guide, and remove roadblocks while establishing expectations and goals. Directors need to trust in their PM’s ability to execute and the director needs to be the uniting force that ensures their success. This role is one with influence, but often less “power” than the PM has on the product.</p><p>Establishing process, building mentor tracts, and championing learning are often some of the primary responsibilities a director will have. The key is to recognize the shift from a doer to enabler.</p><p>A typical job description for a Director of Product Manager often includes (with some added company specific, cultural fit type requirements):</p><ul><li>Providing product portfolio management, mentoring and training Product Managers in best practices, and managing products as needed to support the company’s strategic goals.</li><li>Owning the end-to-end Product and Solution portfolio and associated financial performance with a P&amp;L orientation.</li><li>Providing leadership for the product development process across Sales, Marketing, IT, and Operations.</li></ul><p>This role is one that works across the organization and negotiates up and down to keep a Product Portfolio on track. It is demanding and time consuming, but with a strong Product Management team, it is highly rewarding when thing go right. Conversely, this person can sink a company if they are not successful.</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/06/product-roles-the-role-of-a-director-of-product-management/"><em>coloradoproduct.com</em></a><em> on June 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaaefd43d2be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/the-role-of-a-director-of-product-management-aaaefd43d2be">The Role of a Director of Product Management</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role of a Product Manager]]></title>
            <link>https://medium.com/colorado-product/the-role-of-a-product-manager-a493c51b26b2?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/a493c51b26b2</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Kyle Weiss]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:27:36 GMT</pubDate>
            <atom:updated>2016-01-26T04:27:36.315Z</atom:updated>
            <content:encoded><![CDATA[<p>The <em>Product Roles</em> series focuses on the work each Product role can play in an organization. Please keep in mind, product team’s responsibilities can be highly varied. Some organizations have parsed these job functions to other roles, sometimes across departments. The success of that parsing will vary from company to company. In this series, we will focus on what we feel the roles entail in a “typical” product organization.</p><p>In this second post of the series, We are going to dive into the <strong>Product Management</strong> role a bit more. This description is one of the best over arching summaries we can offer. We will try to talk about day-to-day tasks and what it means to “<a href="http://coloradoproduct.com/2015/05/good-product-managerbad-product-manager/">Be the CEO of your Product.</a>” Some aspect of Product Management include Product Marketing, Product Strategy, or the delineation Agile sometimes put on roles (Product Owner, Business Analyst, etc.).</p><p>From our first post in the series:</p><blockquote><em>Starting with</em><strong><em> Product Managers</em></strong><em> — they fundamentally look after individual products/services: shepherding the short-term development efforts and long-term strategy. They work to keep a 3–12 month roadmap that’s coherent. There are </em><a href="http://www.allaboutproductmanagement.blogspot.com/"><em>many</em></a><em>, </em><a href="http://coloradoproduct.com/"><em>many</em></a><em>, </em><a href="http://www.svpg.com/articles/"><em>many</em></a><em> resources out there that describe the intricacies of this role. At the end of the day, you want to empower these people to own the vision, execution, and support of a product/service vertical. You want to ensure they are accountable for the results the product is delivering.</em></blockquote><p>At the core, The product manager is the person responsible for doing the market research, evaluating and prioritizing the features that will drive the largest benefit for the customer and then validating that feature selection hypothesis (without feedback it is important to know you only have a hypothesis on what will drive the most value). The validation process happens in lots of ways: some build an MVP, some build out the feature in it’s entirety and some merely shop ideas without dev effort at all.</p><p><a href="http://pragmaticmarketing.com/resources/sample-product-manager-job-description">A typical job description</a> for a Product Manager often looks like this (with some added company specific, cultural fit type requirements):</p><ul><li>Managing the product life cycle from start to end (strategic planning to tactical activities)</li><li>Specifying market requirements for current and future products by conducting market research</li><li>Delivering value by working with cross-functional teams (primarily Development/Engineering, and Marketing Communications) to clarify market requirements, product contract, and positioning.</li><li>Developing and implementing a company-wide go-to-market plan (often times called a roadmap), working with all departments to execute.</li></ul><p>These four things may sound easy, but if done well, they are incredibly time consuming and often require heavy context switching. Product Management is an exciting and challenging role; one which can afford you lots of freedom and responsibility. Get it right, and you’re off to the races. Get it wrong and the organization will languish and sputter to see any real success.</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/06/product-roles-the-role-of-a-product-manager/"><em>coloradoproduct.com</em></a><em> on June 2, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a493c51b26b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/the-role-of-a-product-manager-a493c51b26b2">The Role of a Product Manager</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Path to PM: Adam Tornes, Product Manager @ Twitter]]></title>
            <link>https://medium.com/colorado-product/path-to-pm-adam-tornes-product-manager-twitter-4464dbc78410?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/4464dbc78410</guid>
            <dc:creator><![CDATA[Adam Tornes]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:26:42 GMT</pubDate>
            <atom:updated>2016-01-26T04:29:09.853Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Breaking into a product management career can be a challenging endeavor and the “best” or most “straightforward” method to do so is largely undefined. Product Management is often referred to as a role that is learned through experience rather than taught in the classroom. “Path to PM” is a blog series highlighting the many diverse, interesting and unique paths the writers have taken to become a Product Manager.</em></p><p><a href="http://www.twitter.com/atornes"><em>Adam Tornes</em></a><em> currently serves as Product Manager at Twitter and Director, Co-founder of </em><a href="http://www.coloradoproduct.com/"><em>ColoradoProduct</em></a><em>. Prior to joining Twitter, Adam served in a core product management or development role at numerous successful startups. Adam holds a BS from Purdue University and a MBA from The Ohio State University.</em></p><p>Unbeknownst to me at the time, my path to becoming a PM started with my college and degree selection. Coming out of high school, I wanted to pursue either a business degree or a college program that would allow me to combine my passions for digital design and computer science. (Who knew that <a href="http://coloradoproduct.com/wp-content/uploads/2014/12/pm_diagram-e1420401203550.png">Product Management was the intersection of the three</a>?!?) I struggled to find a program that would effectively merge my interests in design and computer science. Ultimately, I chose the one university / program that would allow me to do so, but expected that in time, I’d eventually pursue my other interest; the management / business side.</p><p>After school, I relocated to Boston to take my first job as a Web Development Engineer at Compete. While at Compete, I developed a close relationship with the product team. Members of that team told me I had an “proclivity toward the business side and understanding the voice of the customer”. I took every opportunity to work on business and product-related projects in addition to my engineering responsibilities. After a few years, I was ready to move on and I wanted to pursue a new career elsewhere; a new role, at a new company, in a new city.</p><p>I chose to pursue a MBA to transition into Product Management by further developing my business acumen. Given my interest in non-traditional MBA fields of technology and product management, I knew I needed to do something unique. At OSU, I was able to develop my own “major” and tailor it to my goals. My tailored degree was a combination of courses primarily from the marketing, strategy, and entrepreneurship majors with minor coursework in leadership/management and the extremely limited technology and product management oriented offerings. Ultimately, I believe this course load prepared me for a career in product management the best an MBA could, especially one at a non-technology oriented school and non-Product Management program (which didn’t really exist). Beyond the university course load, I embedded myself in any and all extracurricular opportunities and experiences in the university as well as local technology and startup communities.</p><p>Though business school was part of the plan, getting a job in product management was the ultimate goal. Networking with existing tech industry connections, reaching out directly to connected alumni in the technology industry, and raw determination led me to both my first internship and subsequent jobs. The process was frustrating as my peers were applying and interviewing for positions that weren’t expecting them to start for months, at companies accustom to hiring MBAs right out of school. Unfortunately, the 2–3 interviews through the career services department and on-campus opportunities were not very fruitful (or interesting). Luckily, my engineering experience and MBA did a) make me an intriguing applicant, b) created a compelling reason for reaching out and connecting with industry professionals, and c) provided an excuse to ask about opportunities/needs at companies of interest that may not have open reqs. In the end, I had multiple internship and full-time offers and was able to choose a great position in my desired location of Boulder CO, where I both interned and was hired for my first full-time PM role by the same company. With that first Product Management position, I was hooked and haven’t looked back since!</p><p>So what are my takeaways and advice given my own “Path to PM”?</p><ul><li>Get connected and build a strong network of people that are established in the industry, role or company you are interested in.</li><li>Build, ship, launch, lead, develop anything you can — a startup idea, a website/blog, an event, an organization, etc.</li><li>Seek opportunities to tailor existing roles and opportunities in ways that develop skills and experience doing things required of a product manager</li><li>Create your own path, blaze your own trail and be persistent — nobody is going to hand you your first PM job.</li></ul><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/04/path-to-pm-adam-tornes-product-manager-at-twitter/"><em>coloradoproduct.com</em></a><em> on April 28, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4464dbc78410" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/path-to-pm-adam-tornes-product-manager-twitter-4464dbc78410">Path to PM: Adam Tornes, Product Manager @ Twitter</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of a Product Manager versus Director versus VP]]></title>
            <link>https://medium.com/colorado-product/overview-of-a-product-manager-versus-director-versus-vp-99778d725bc1?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/99778d725bc1</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-roles]]></category>
            <dc:creator><![CDATA[Kyle Weiss]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:26:09 GMT</pubDate>
            <atom:updated>2016-01-26T04:25:59.444Z</atom:updated>
            <content:encoded><![CDATA[<p>We are going to kick off our Blog with a series on <em>Product Roles</em> and how each role varies. This series will focus on the work each Product role can play in an organization. Please keep in mind, product team’s responsibilities can be highly varied. Some organizations have parsed these job functions to other roles, sometimes across departments. The success of that parsing will vary from company to company. In this series, we will focus on what we feel the roles entail in a “typical” product organization.</p><p>Welcome to Product Management! Let’s start out the series with a quick summary of each job title most common in product organizations. This summary is the most straight forward explanation we could distill the roles into and does not consider Product Marketing, Product Strategy or the delineation Agile sometimes put on roles (Product Owner, Business Analyst, etc.).</p><p>Starting with<strong> Product Managers</strong> — they fundamentally look after individual products/services: shepherding the short-term development efforts and long-term strategy work to keep a 3–12 month roadmap that’s coherent. There are <a href="http://www.allaboutproductmanagement.blogspot.com/">many</a>, <a href="http://coloradoproduct.com/">many</a>, <a href="http://www.svpg.com/articles/">many</a> resources out there that describe the intricacies of this role. At the end of the day, you want to empower these people to own the vision, execution, and support of a product/service vertical. You want to ensure they are accountable for the results the product is delivering.</p><p><strong>Directors of Product Management</strong> look after the business of product management. They usually help oversee the cohesion of multiple product/service verticals and they should be the guiding light on the process and tools used to report the product team’s direction. They are the stabilizing and negotiating hand that ensure teams are operating with synergy. They know when to step in to support a Product Manager and they, most importantly, know when to step back from the Product Manager to let her flourish.</p><p>The <strong>VP of Product Management</strong> functions as senior staff to the rest of the executive team making sure that the company as a whole is building, shipping and supporting the right products. They are the product manager of the organization itself and they should be brokering, negotiating and setting expectations both up and down the organization. These folks should be a beacon at the executive level who represents product/market/company success rather than any one specific function. Thinking more broadly than Engineering, Marketing, Sales or Support. They need to have deep experience in navigating short-term, choppy waters, while plotting the course that will enable long term smooth sailing. They are the one most likely to say “Yes, but the right thing for our long-term business and the markets we serve is… (<a href="http://www.mironov.com/vppm/">source</a>)”</p><p>In very small organizations, the Director role is probably not necessary; you may find the VP is doing product manager work or vice versa (depends on <a href="http://www.bhorowitz.com/titles_and_promotions">how cheap titles are in your organization</a>). In the next part of this series, we will dive deeper into the Product Manager role and how we feel it shapes up in different organization sizes. Share your thoughts below in the comment section as to how this relates to your experiences.</p><p><em>Originally published at </em><a href="http://coloradoproduct.com/2015/04/product-roles-overview-of-a-product-manager-versus-director-versus-vp/"><em>coloradoproduct.com</em></a><em> on April 8, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99778d725bc1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/overview-of-a-product-manager-versus-director-versus-vp-99778d725bc1">Overview of a Product Manager versus Director versus VP</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good ScrumMaster | Bad ScrumMaster]]></title>
            <link>https://medium.com/colorado-product/good-scrummaster-bad-scrummaster-6031687b589a?source=rss----25db5e98cbfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/6031687b589a</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kyle Weiss]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 04:21:15 GMT</pubDate>
            <atom:updated>2016-01-11T19:42:11.699Z</atom:updated>
            <content:encoded><![CDATA[<p>Years ago, <a href="https://twitter.com/bhorowitz">Ben Horowitz</a> wrote about <a href="http://web.stanford.edu/class/e140/e140a/handouts/ProductMgmt.txt"><em>Good Product Manager, Bad Product Manager</em></a> while he was at Netscape. It has remained arguably, one of the most role shaping pieces I have read. If you have not read it, I would.</p><p>I started reflecting recently on what I value in a ScrumMaster. As a result, I started searching for something similar for ScrumMasters…I couldn’t find anything. There is great dialog around what the role entails, but nothing so pointed and precise as Ben’s original email to his staff. I decided to write one of my own, based on experiences in trainings, past organizations and SCRUM readings. Let me know your thoughts.</p><p><em>Good ScrumMasters know the framework, the process, the tools and have the insight to adapt them to the team’s needs. A good ScrumMaster is the evangelist of accurate and timely reporting. A good ScrumMaster knows her team’s current progress and expected velocity range, always. A good ScrumMaster is a coach, one who removes impediments, builds the team’s confidence and fights the right fight.</em></p><p><em>Bad ScrumMasters have lots of excuses. Not enough buy-in from leadership, Product wont listen, I cant manage this many teams, I dont know the business objectives. </em><a href="https://medium.com/u/7235ff520fbc"><em>Mike Cohn</em></a><em> doesn’t make these excuses when coaching, neither should a good ScrumMaster.</em></p><p><em>Good ScrumMasters measure their success with velocity increases, team morale gains, estimate precision increases and project completions — on time and under budget. Good ScrumMasters appropriately plan releases, sprints, and sizing meetings, all with well scoped stories and expectations. Good ScrumMasters coach Product on story writing and take a personal interest in what will be reviewed by the team. Bad ScrumMasters dont review stories until the day of the respective meetings.</em></p><p><em>Bad ScrumMasters get buried in the “how” with the engineers. Good ScrumMasters recognize they control the process and the “when” of execution. Good ScrumMasters are technical and understand stand-up reports. Bad ScrumMasters let team members labor on beyond their team’s stand up needs. Good ScrumMasters ask what road blocks someone has, because they care. Bad ScrumMasters assume things will get elevated before it’s too late.</em></p><p><em>Good ScrumMasters embrace change as an opportunity to learn and challenge a team. Bad ScrumMasters cling to processes that worked in the past without consideration for the future. Good ScrumMasters report frequently on sprint progress and check in with Product to ensure scope isn’t inflating. Bad ScrumMasters complain that scope is increasing because process isnt being followed.</em></p><p><em>Good ScrumMasters have 100% confidence from their teams that they are looking after the team’s interests. Bad ScrumMasters dont care about buy-in from the team. Good ScrumMasters do anything necessary to help the team perform at their peak. Bad ScrumMasters blame the team’s process doubt on the team’s inability to perform. Good ScrumMasters work hard to know each team member’s skills and work style, understanding how they can best contribute to the team’s success. Bad ScrumMasters treat engineers as interchangeable cogs.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6031687b589a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colorado-product/good-scrummaster-bad-scrummaster-6031687b589a">Good ScrumMaster | Bad ScrumMaster</a> was originally published in <a href="https://medium.com/colorado-product">Colorado Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>