<?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 garrish on Medium]]></title>
        <description><![CDATA[Stories by garrish on Medium]]></description>
        <link>https://medium.com/@grrsh?source=rss-d0b3ed044bf7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2lD7Y_FHjd6501pA.jpeg</url>
            <title>Stories by garrish on Medium</title>
            <link>https://medium.com/@grrsh?source=rss-d0b3ed044bf7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:25:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@grrsh/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[Service-as-a-Service?]]></title>
            <link>https://medium.com/@grrsh/service-as-a-service-8423223dfa87?source=rss-d0b3ed044bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8423223dfa87</guid>
            <category><![CDATA[enterprise-software]]></category>
            <dc:creator><![CDATA[garrish]]></dc:creator>
            <pubDate>Sun, 09 Jul 2017 18:14:46 GMT</pubDate>
            <atom:updated>2017-07-09T18:14:46.040Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9BUkZgu0MRDL2oCYWVha8g.png" /></figure><p><strong>Service-as-a-Service?</strong></p><p>I’m seeing this idea more — although it is often hidden due to perception that it is “pro serve” revenue (bad) vs “service as a service” revenue (not always bad).</p><p>The key with ServAAS is that the service must be productized. The words and definitions are wrapping around, almost touching each other now.</p><p>In a classic service context, “productized services” have edges. Think: Terminix vs Accenture. In order to make a ServAAS model work, it needs to be incredibly clear where the service stops. In other words, what will your people NOT do for a customer. It is soooooo easy to drift into extra work.</p><p>In many respect, obscuring people behind a wall of technology helps in this regard. Customers don’t necessarily know that it is HITL, nor should they. Customers that know will press and push for more. Companies that want to keep customers will provide. And then the virtuous cycle begins to erode.</p><p>Getting to this kind of model is a sea change for either services or software companies.</p><p>For services companies, adding boundary conditions is heretical from a customer satisfaction point of view — it means a lot of saying no! Typically services companies don’t have the structure to execute on this, and financially, don’t perceive the investment as valuable. For example, who defines the “product”? Who markets it? How do we charge? etc etc. Product companies have things like PRODUCT MANAGERS who do this stuff. Services companies don’t (usually). It is a tough investment because a product function is very fixed cost oriented. It can’t readily be variabilized into “projects” which are often the unit-of-measure for a services company.</p><p>Software companies have the opposite challenge. In addition to the cultural “eww” factor of adding service to their cost base, it also requires new structures. For example, how do you measure, manage, reward, etc. a cadre of people who take data from one system and put it into another? They aren’t “project people” (which, actually software companies can grok just fine… it’s pro-serve!) and they aren’t product people. They are somewhere in-between. They are providing a bounded service, but the mechanism is labor. Unlike other parts of a software company that do this (dev), it is inherently uncreative. It is mostly about moving from point A to point B as cheaply as possible… akin more to a call center support function than an inherent part of the revenue bearing “product.”</p><p>Perhaps a better name for this would be “solution-as-a-service” — maybe companies would be more comfortable with this. But, don’t get me started on the definition of a “solution.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8423223dfa87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2016 Product Management Almanac]]></title>
            <link>https://medium.com/@grrsh/the-2016-product-management-almanac-a2518a7d23dc?source=rss-d0b3ed044bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2518a7d23dc</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <dc:creator><![CDATA[garrish]]></dc:creator>
            <pubDate>Wed, 30 Dec 2015 19:42:02 GMT</pubDate>
            <atom:updated>2017-07-09T17:07:25.962Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Product Management Almanac</strong></h3><p>We’ve lost the old ways in Silicon Valley. A topic that I think is especially under-represented is the function of software product management (especially enterprise). So much of what most product managers face has been faced before. But it seems like every company, every PM, every “micro generation” keeps learning every lesson anew.</p><p>In the spirit of the Old Farmers Almanac, I think we need a Product Management Almanac — a yearly, PM go-to guide that is “useful, with a pleasant degree of humor.” A vernacular. Hey it worked for farmers right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*sbDNxR37vD4LIW0h7wMGaw.png" /><figcaption>The Old Farmer’s Almanac is still alive and well. If you are concerned more about slugs in your garden than software go <a href="http://www.almanac.com/">here</a> to pick up a copy of the real Almanac</figcaption></figure><p>Such a thing would cover topics such as:</p><ul><li><strong>What is a Product? —</strong> Closely related these days to What is a Solution? like this: <a href="https://youtu.be/IAE0bfi9dIE">hahahaha</a>.</li><li><strong>PM is not the same as _______. </strong>Project Management. UX. Product Marketing. Product Managers are a thin-skinned bunch, eh!</li><li><strong>Market-centric versus customer-centric — </strong>This could also be thought of as “Stuff you Should and Should Not Do for Customers.”</li><li><strong>Why PM is the best job ever / worst job ever —</strong> This topic could fill a semi.</li><li><strong>Enterprise and Consumer are vastly different —</strong> Discuss.</li><li><strong>Tactics for different parts of the product lifecycle —</strong> What you need to do for a mature product is not what you need to do for a new product. It’s the science-y part of PM.</li><li><strong>Predicting delivery / roadmapping and the like — </strong>Like <a href="http://a16z.com/2015/11/13/high-output-management/">so many high output followers of Ben Horowitz here in the valley</a> I recently re-read the Andy Grove classic High Output Management. Of note he discusses stagger charts and why overall predictive-y behavior is gold. It is a tenet of manufacturing to have a product(ion) forecast. Of late, I hear this a lot in the form of “we’re agile, we can’t predict” (total bullshit, btw)</li><li><strong>Quick and dirty customer validation — </strong>This is really an enterprise thing, my apologies to you consumer guys. Also: How to do validation when you have more time.</li><li><strong>The best agile management tools and the best way to use them — </strong>By this I mean <a href="https://www.rallydev.com/">Rally</a>, <a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="https://www.versionone.com/">VersionOne</a>, <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a>. A story as told by PMs, not Dev. There is a TON of thinking about how to organize dev teams around these tools, but not a lot about how to align with PMs… specifically strategic thinking and the longer term goal alignment for the product.</li><li><strong>How to deal with a shitty boss / idiot employee.</strong> On the former, the best advice I’ve ever seen on this was Norm Augustine (<a href="https://en.wikipedia.org/wiki/Augustine%27s_laws">Augustine’s Laws</a>), former CEO of Lockheed Martin, and a guy who predated the internets by about 10 years. To paraphrase: “If you don’t have a great boss, go get one.” The latter could probably be summed up with <a href="https://hbr.org/1999/11/management-time-whos-got-the-monkey">not taking the monkeys</a>. So much here, where to begin.</li><li><strong>Hiring interview questions to ask when you don’t have time to prep.</strong> We’ve all been there, over and over.</li><li><strong>Whose job is it?</strong> This is the perennial question of what to expect from pre-sales, sales, pro-serve, marketing, product marketing, HR, finance, etc. etc. In other words, all the other people at the company that you, the “CEO of your product,” will need to engage with to make your product successful. At larger companies this is where the dreaded <a href="http://www.valuebasedmanagement.net/methods_raci.html">RACI model </a>gets whipped out, God help us all.</li><li><strong>Shit you hear from the [insert role here] and how you respond.</strong> How do you deal with the pre-sales team that can’t demo? Or the product marketing team that can’t write content? Or the support team that can’t troubleshoot? And so forth. It is the tactical coping mechanisms for bridging a skill or motivation gap.</li></ul><p>I’m sure I missed a bunch. Fill in the gaps for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2518a7d23dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>