The “Discovery Center Challenge”: A Case Study for Product Managers
In November 2018, our product team for the SAP Cloud Platform Discovery Center launched the “Discovery Center Challenge”. The Discovery Center Challenge is a contest through which users can earn over $2,500 USD in prizes for using the product. This blog is a case study for Product Managers who are interested in what prompted our team to invest in such a contest and how they could devise and deploy similar methods in their products.
The “Discovery Center Challenge”: A Case Study for Product Managers
A common qualification that you see requested on job openings for Product Managers is “experience launching a product.” It makes sense. A Product Manager should have an entrepreneurial mindset and know what it takes to get a product from concept to launch. But that’s only half the battle. Actually, it’s more like a quarter of the battle. All Product Managers should be familiar with the product lifecycle and its four stages: Introduction, Growth, Maturity, Decline, refer to Image 1 below. Once the Product Manager and product team have launched the product and introduced it to the market, they have entered the first stage. The team must then get the product from the initial introduction to the second stage of rapid, habitual growth.
Image 1. The product lifecycle and its four stages
For technology products, the movement between the Introduction and Growth stages brings to mind the technology adoption lifecycle model, refer to Image 2 below, and the metaphorical chasm between early adopters (i.e. visionaries) and the general public (i.e. pragmatists) that Geoffrey Moore proposes in his variation to the model. Often, to move between these stages requires the same methods as crossing this chasm. These methods must create a sort of “bandwagon effect” to build momentum (i.e. growth).
Image 2. The technology adoption lifecycle
There are numerous methods to enter the Growth stage and build the momentum necessary to cross “The Chasm” and push through this stage. One such method that I have been researching over the past year utilizes the “Hook Model” described by Nir Eyal in his book Hooked: How to Build Habit-Forming Products, refer to Image 3 below. This model describes ways that Product Management teams can leverage psychology in an ethically sound manner to build products that become default solutions to users’ impulses. The model begins with internal and external triggers.
Image 3. The Hook Model
In Hooked, Eyal, a writer for TechCrunch, Forbes, and Psychology Today, introduces the concept of “paid triggers” and defines these triggers as “paid channels [that] are commonly used to get users’ attention and prompt them to act.” In other words, paid triggers are investments that companies make to occupy more of their target users’ attention space in the hopes to create a touchpoint with their product. Some familiar examples of paid triggers include the following:
Example 1. Paid triggers utilizing sponsored advertisements
Example 2. Paid trigger raising the visibility of your product in search engine results
Example 3. Paid trigger offering part of your product for free
As an additional example, we can investigate the product that I work on, the SAP Cloud Platform Discovery Center. The SAP Cloud Platform Discovery Center has faced the same struggle as any product moving from the Introduction to Growth stage. Our early adopters have been technologists from “SAP shops”, companies that primarily run SAP software, who have been given a license to SAP Cloud Platform and are now experiencing the pain of figuring out what their company can do with it. But these early adopters are too few to constitute rapid, habitual growth. We have reached Geoffrey Moore’s metaphorical chasm and our Product Management team has been in full strategy mode to determine how to extend our reach to the general public. One result of our strategic brainstorming was our paid trigger which we named the “Discovery Center Challenge”. If your product team is also facing “The Chasm” and looking to utilize triggers to reach the next stage in your product’s lifecycle, I would recommend following the “Bullseye Framework” proposed by Justin Mares in his book Traction: How Any Startup Can Achieve Explosive Customer Growth.
Our paid trigger is fairly simple: we will give you money to use our product. As you can see in my other blog announcing the “Discovery Center Challenge”, we are offering tiers of prizes that increase in value linearly with your investment of time and energy in our product. These tiers start at $25 USD for taking the first action and increase all the way to $2,500 USD (the price of a ticket to the 2019 SAPPHIRE NOW conference). This first action that we ask is to start a Mission; an endeavor that takes less than 5 minutes. We have this as the first action because a Mission is the basic building block of our product and embodies the value of what the SAP Cloud Platform Discovery Center provides. We are willing to give away money for starting a Mission because we believe that once a user takes that action the intrinsic value of the SAP Cloud Platform Discovery Center will become evident and these paid triggers will merely be icing on the cake.
Through the Discovery Center Challenge, we hope to reach new users and expand our user base. These new users include our key HR personas which are the personas that I work most closely with to build the SAP Cloud Platform Discovery Center. If you are in HR Operations, HR Information Systems, or an HR function, I have published additional blogs about the SAP Cloud Platform Discovery Center that may interest you:
- Why should HR care about an “extensibility” platform?
- What does it mean to extend SAP SuccessFactors with SAP Cloud Platform, and why should HR care?
- Making the HR department successful with platform technology
Triggers, including paid triggers, are just the first step of Nir Eyal’s Hook Model. As you can see in Image 1 above, there are additional steps that Eyal proposes to create a habit-forming product. The Discovery Center Challenge is one of our methods to succeed at this step, and we won’t be able to determine the degree of its success until after the contest concludes in March 2019. I will continue to share Product Management insights cleaned from building the SAP Cloud Platform Discovery Center in future blogs.
In the meantime, if you have feedback for the Discovery Center Challenge or the SAP Cloud Platform Discovery Center please let us know using the Comments section below. Additionally, if you are on a product team and have also faced the challenge of moving from Introduction to Growth reach out to me on LinkedIn – I love to talk product!
About the author
Colin Kraczkowsky is on the Product Management team for SAP Cloud Platform and is currently building the SAP Cloud Platform Discovery Center. His domain expertise includes SAP SuccessFactors extension development on the platform.
Colin’s professional history includes enablement and extension development for SAP’s analytic portfolio and front-end design and business development for a digital media startup in Washington, D.C.
In his spare time, Colin likes to explore new areas, watch scary movies, try weird foods and participate in Turkey Trots. Colin is currently located in Palo Alto, California.
Connect with Colin – https://www.linkedin.com/in/colinkraczkowsky