john gibbon
  • Bio
  • Stanford Class
  • Product Mgt
  • Product Dev
  • Career Resources
  • Blog
  • Talking Product Strategy

Inspired

4/18/2018

0 Comments

 
Picture
​The second edition of Inspired is even better than the first (which I reviewed here and used to be my favorite product management book).

It is the best articulation of how to be successful in product management and how to create successful products that I have ever read. It is impossible not to run into into insights about challenges you are having or have had as a product manager when reading it. (This can be a little creepy, how does he know about all these mistakes I have made, is he a psychic?)  

Do you want to get a job as a product manager? Read and re-read Marty’s book and steal at least a few of his insights for the interview - you’ll sound like a genius.

Some of the topics that resonated for me (I’m sure there will be different ones for you):

-Product management is distinct from other essential roles: design, engineering, product marketing, and project management (Chapter 1).

-Two inconvenient truths that often cause failed product efforts are: at least half our ideas are just not going to work (customers ultimately won’t use it - which is why you need customer validation early in the process) and it takes several iterations to implement an idea so that it delivers the necessary business value (Chapter 6).

-The three overarching product development principles from Lean and Agile which help you create successful products are (Chapter 7)
     -Risks should be tackled up front, rather than at the end.
  -Products should be defined and designed collaboratively, rather than sequentially.
     -Its is all about solving problems, not implementing features.

-You need a team of missionaries, not mercenaries to create the smallest possible product that meets the needs of a specific market of customers (Chapter 8,9).

-A product manager must bring four critical contributions to their team (Chapter 10): 
    Deep knowledge 
        1) of your customer 
        2) of the data 
        3) of your business and its stakeholders 
        4) of your market and industry 

-Product managers (PMs) need product designers - not just to help make your product beautiful - but to discover the right product (Chapter 11).

-Typical product roadmaps are the root cause of most waste and failed efforts in product organizations (Chapter 22).  It is all too easy to institute processes that govern how you produce products that can bring innovation to a grinding halt.  You need to try to wean your organization off of typical product roadmaps by focusing on business outcomes, providing stakeholders visibility so that they know you are working on important items, and by eventually making high-integrity commitments when critical delivery dates are needed (Chapter 60). Part of this is managing stakeholders which includes engaging them early in the product discovery process ideally with high-fidelity prototypes (Chapter 61).

-Products should start with a product vision in which the product team falls in love with the problem, not the solution (Chapter 25).

-Strong product teams work to meet the dual and simultaneous objectives of rapid learning and discovery while building stable and solid releases in delivery.  Product discovery is used to address critical risks: (Chapter 33)
    -Will the customer buy this, or choose to use it? (value risk)
    -Can the user figure out how to use it? (usability risk)
    -Can we build it? (feasibility risk)
    -Does the solution work for our business? (business viability risk)

-PMs can’t rely on customers (or executives or stakeholders) to tell us what to build: customer doesn’t know what’s possible, and with technology products, none of us know what we really want until we actually see it (Chapter 33).

-While Amazon has a culture of “write the press release first”, Marty suggests PM should write a “happy customer letter first."  Imagine a letter sent to the CEO from a very happy and impressed customer which explains why he or she is so happy and grateful for the new product or redesign.  The customer describes how it was changed or improved his or her life.  The letter also includes an imagined congratulatory response from the CEO to the product team explaining how this has helped the business  (Chapter 36).

-Product managers need to consider the role of analytics and qualitative and quantitative value testing techniques (Chapter 54).

-What it really means for a PM to be the CEO of Product is testing business viability: listening to Marketing, Sales, Customer Success, Finance, Legal, BD, Security, etc. before building the product (Chapter 56).

-Establishing a strong product culture requires (Chapters 66-67)
    -Innovation culture: compelling product visions, strong product managers, empowered business and customer savvy teams product teams often in discovery
    -Execution culture: urgency, high-integrity commitments, accountability, collaboration, results orientation, recognition, strong delivery management, frequent release cycles 
    (and it is hard to do both)
    
    

0 Comments

Different Ways to Price Your SaaS Offering

2/17/2018

0 Comments

 
Picture

​There are several distinct pricing models for the on-going use of a Software-as-a-Service (SaaS) offering.  


​​​(Often there will be distinct tiers in these different models in which the cost increases as the capacity or capabilities of the offering increases.  Also there are often increasing discounts for an increasing amount of pre-committed volume; with an additional “overage” fee for when a customer surpasses that volume.)  


Per User or "Per Seat"
     Pros: Easy to calculate and allocate, encourages adoption and increased usage by users who have a license or seat.
     Cons: Discourages adoption across a company by creating a barrier (seat license) for potential infrequent users - who might later become frequent users. Slack’s per-active-user model partially addresses this by only charging for users have been active in the last two weeks (https://www.quora.com/Who-pays-for-Slack)
     Examples:  Salesforce (CRM).  Has a standard per user licensing model which increases as the number of users and the capability increase (currently from $25/month to $300/month). https://www.salesforce.com/editions-pricing/sales-cloud/
     This pricing model can sometimes vary across roles. 

Per Transaction
     Pros:  Enables adoption from the occasional to the power user which helps make the offering ubiquitous across the client's organization significantly increasing its value and impact. (This is SAP Concur's pricing model and its adoption is often aided by it being the only way an employee can be reimbursed for their expenses. Opinions are my own, but I work for SAP Concur).
     Cons: For some high price per transaction offerings, the lack of an all-you-can-eat model can limit usage for a given user or on a given project. 
     Examples: Concur https://www.concur.com/en-us/small-business/expense.
     Note: A variation of this per-number-of-transactions model is a per-$-of-transaction model.  For example it seems that Zuora, a subscription billing company (so helps actualize pricing models), bases their model on the amount of subscription revenue the customer has on Zuroa's platform. https://www.quora.com/Does-anyone-know-the-cost-to-use-a-solution-like-Zuora
https://www.mckfastgrowthtech.com/time-rethink-per-user-pricing-enterprise-saas/

Per User or Per Transaction Freemium (free is often ad-supported) 
    Pros: Enables easy adoption
    Cons: Must have compelling enough capabilities so that users will adopt the free version; but still significant enough differentiation that users will upgrade to the paid version. 
    Examples: Slack:  https://slack.com/pricing.  While Slack has a standard per user model, they also have a free version "for small teams wanting to try out Slack for an unlimited period of time.” So Slack doesn't limit time, but it does limit storage (and other premium capabilities) in the free version. 

Per Project
     Based on the value of the project (construction management) or portfolio (financial assets under management) that is benefiting from the offering.
      Pros: Encourages viral adoption for all users and third party partners across a project (leading to familiarity and possible adoption on future projects). The benefits of this type of model is that it encourages interactivity and adoption with all the participants involved; both within the subscribing company and by other third parties (often subcontractors).  
     Cons: This all-or-nothing approach makes it unsuitable for use on a small portion of a given project; and makes it difficult for the gradual increased adoption across an entire project. 
    Examples: Some financial services SaaS products and some construction management products such as Aconex, a construction project management tool. Aconex drives adoption of their  “project wide solutions" by including "unlimited access to training and support resources for every organization you work with.”  (From certain sources it seems that Aconex contends with the cons of this model by offering an enterprise model for companies that adopt their tool across many projects and a per user pricing model when the tool is just used for a small portion of a project). 
https://project-management.com/aconex-software-review/
https://www.aconex.com/pricing
https://www.eurekareport.com.au/articles/138999/aconex-xero-construction-sector

Per Resource Used (or Pay-as-You-Go): 
    This is more common in the rent-a-resource world of PaaS/IaaS where providers will charge based on resource usage; example per CPU or per GB storage.
   Example: AWS (https://aws.amazon.com/ec2/pricing/) which has per hour (and per second) pricing that can vary depending on required availability of service, "on-demand" is more expensive than "spare capacity" pricing.  

Per Outcome or % of Savings:
     While many offerings claim a hard dollar ROI, a pricing model which is based on a percentage of that return on investment (such as savings) can be compelling.
     Pros: Obviously this model aids adoption since the buyer only pays if they receive the guaranteed benefit.
     Cons: Only certain offerings have specific well-defined financial benefits such as savings. Also there are specific companies who have moved away from this models since it leads to disagreements with their customers over the specific savings achieved.
     Examples: Vat Reclaim: TaxBack https://www.taxback.com/en/corporate/vat-recovery/ and VATiT: https://www.vatit.com/en/page/vat-recovery

Per Company (Flat-rate or tiered) 
    For simple services provided by SaaS providers                  
    
https://www.cobloom.com/blog/saas-pricing-models

Open Source Model
    Open sourced companies often charge for support or additional features (in which case it could be consider a type of freemium model). https://techcrunch.com/2016/02/09/the-money-in-open-source-software/
     Examples: RedHat (Linux) or Docker (containerization) 

Loss-Leader
    Some offerings are either free or sold at a considerable discount as a loss leader for other products or services that are provided by the company (such as computer hardware).


Other Notes:
   Hybrid Model: As noted by McKinsey, companies can use hybrid models that include both user and non-user metrics. https://www.mckfastgrowthtech.com/time-rethink-per-user-pricing-enterprise-saas/
   Price as a Client Buys:  Almost as bad as trying to convince a prospect that they have a problem that they should pay you to solve, trying to convince a customer to purchase your solution in a manner that doesn't align with their business and how they typically buy services is problematic. Therefore you should understand how a typical customer buys a solution like yours before you define your pricing model. 
   Pricing Strategy:  This blog posts suggests a few different models used to price a SaaS offering, but it doesn’t address the more complex question of what should your price be considering a given model.  (One simple framework is the three C’s: cost-based pricing, customer value-based pricing, and competitor-based pricing.) 
  On-Premise: SaaS pricing models are typically distinct from on-premise pricing models which are generally based on a one-time perpetual license plus an on-going service and support fee.
   Non-Profit Pricing: Many of these companies provide a free or significantly reduced pricing for non-profits which is a good cultural signal about the company.
    Setup and Training Costs:  Ideally your SaaS product is easy to “discover, try, and buy” with a quick time to value with minimal setup that can be performed by the customer. Sometimes either the complexity of the software or the topic prohibits this, so that there needs to be implementation (and possibly data migration) and/or training provided either by the SaaS company or a third party.  Often this is baked into the on-going fee, sometimes it is a distinct upfront cost. 
    Sources:  Information for this article came from sources including: 
          https://www.inturact.com/blog/the-top-10-saas-pricing-strategies
          https://www.cobloom.com/blog/saas-pricing-models
          https://www.cloudesire.com/7-best-pricing-models-for-saas-businesses/
          https://blog.kissmetrics.com/saasy-pricing-strategies/

0 Comments

Slides from "Decisions You Must Make to Grow" Your SaaS Product Business" (Presented at Dreamforce '13 Founders Forum)

11/21/2013

0 Comments

 
Growing Your SaaS Product Business from John Gibbon
Growing your SaaS Product Business (with speaker notes) from John Gibbon
0 Comments

Cloud Business Fundamentals: 5 Rules To Live By (Decisions You Must Make to Grow Your SaaS Product Business)

11/1/2013

3 Comments

 
Presenting at Dreamforce '13 as part of Founders Forum 

A hands-on session around company and product strategy which will help you make decisions on how to grow your SaaS product business, including how to:

-Measure growth and define success
-Identify common roadblocks to company growth
-Determine where to focus your efforts 
-Refine company & product portfolio strategy and trade-offs
-Assess different potential opportunities    


Thursday, 11/21/2013 10:00 AM
p.force.com/foundersforum
Click here to learn more about my session in the Dreamforce app


3 Comments

So You Want to Grow Your SaaS Product Line       (Product Management / Product Strategy Notes)

10/12/2013

0 Comments

 
0 Comments

Talking Product Strategy at Apttus Accelerate

9/9/2013

0 Comments

 
Picture
Picture
0 Comments

Answering Questions CIOs Ask About Cloud / SaaS

7/11/2013

0 Comments

 
0 Comments

Presenting at SydStart, CeBIT, and Salesforce CCT

5/28/2013

0 Comments

 
Picture
Presenting "Enterprise Application Opportunity" at Sydney Startup @ CeBIT 2013 Also presented "AppExchange" at Salesforce CCT (Customer Company Tour) 2013
Picture
Presenting "Enterprise Opportunity" at SydStart 2013 with Peter Lee (sydstart.com). Also gave similar presentation at Salesforce Partner Academy at Sydney 2013 CCT
0 Comments

THE Questions for a Product Management Team

6/22/2012

1 Comment

 
Recently a CEO suggested I consider doing some short term consulting work for his company.  He wanted to know what questions I would ask to figure out how I could help his product management / products team.

This is what I came up with (what do you think?):

-How do you balance short term improvements with long term innovation and new revenue opportunities?

-How do you make product decisions using different market, portfolio, and client analysis techniques?

-What are the components (including success metrics) you include in a business case or MRD for different situations?

-Which among the many different PRD or requirement documentation options do you use?

-How do you change the organization of a team and its processes based on the stage and size of the product line and the company? (i.e. How agile should you be?)

1 Comment

Product Discovery at Google

9/29/2009

0 Comments

 
I recently gave a talk at Google on Strategy and Product Discovery.

We discussed: 
     Discovering Features and Products (Product Strategy)
     Discovering Products and Product Lines (Product Line / Company Strategy)
     Marty Cagan: Using High Fidelity Prototypes for Product Discovery
0 Comments
<<Previous

    Categories

    All
    Books
    Careers
    Cloud Computing
    Energy
    Enterprise2
    Humor
    Marketing
    Product Management
    Smart Grid
    Strategy

    Archives

    February 2018
    September 2017
    July 2016
    August 2014
    March 2014
    November 2013
    October 2013
    September 2013
    July 2013
    May 2013
    June 2012
    March 2012
    March 2010
    October 2009
    September 2009
    August 2009
    June 2009
    May 2009
    March 2009
    February 2009
    January 2009
    December 2008
    November 2008
    October 2008

    RSS Feed



    The postings on this site are my own and don’t necessarily represent my company's positions, strategies, or opinions
✕