Category: Product Manager

  • FOMO and product adoption

    Its been a huge month in tech with #wallstreetbets on reddit** and crypto going mainstream – but the breakout success in Apps has to be Clubhouse. Clubhouse launched in April of 2020, perfect for a COVID world, now they have over 5M users on IOS only! They’ve mastered the art of FOMO to drive that growth.

    Source: the twitter thread below

    Why FOMO matters

    For the uninitiated: “fear of missing out” (FOMO) is a huge driver of consumer crowd activity. It was a big, big driver in the #wallstreethbets fight and is fully leveraged in Clubhouse’s explosive growth. @petergyang summarises on this excellent twitter thread.

    Specifically Yang outlines:

    1. FOMO on top creators (they had superstars like @pmarca and @naval early, culminating with @elonmusk, upcoming is Elon with Kanye ????‍♂️)
    2. FOMO on the best content
    3. FOMO on invites
    4. FOMO on growing audience
    5. FOMO on delightful experiences

    The thread expands detail for each of these points – it’s worth a read.

    BUT…I wanted to focus on 2 important messages for the activation part of the funnel (where Contextual helps), that matters a ton for Product Managers and Growth teams:

    1. The app also aggressively promotes follows through: 1. Onboarding 2. Notifications 3. Clubs
    2. “…is the delight of discovering an amazing topic or seeing a top creator join the conversation. Variable rewards cause people to tune in more.”***

    Whilst there is a huge FOMO in acquisition (users get invites which makes them part of the “insiders” club”), its is the ability to re-engage via the Onboarding and Notifications to keep bringing them back.

    The big deal about consumer Apps is the “meh” response once they’ve installed and the users closes the App and doesn’t come back (they go back to Instagram or Tiktok for their entertainment). This is why consumer apps have Day 0 abandonment above 78%.

    FOMO based re-engagement

    Have your product team brainstorm what are the FOMO elements that your users want. Think about it….the user likely went to the effort of installing your App or creating an account. Not all FOMO needs to be about worshipping Elon or Naval or Kanye (does anyone ?????).
    Things that might make sense:

    • if you are ecommerce, then can you alert the user about price drops.
    • if you are real-estate or research, can you capture the users preferences and give them an inside edge that will have them opening the app again.
    • if you have a social graph, let their connections do the re-engagement broadcast (this is how Clubhouse uses “Clubs”).
    • …the list goes on.

    The first point is that it’s likely to acquire a user (even before activation) you’ve nailed the insight that drove them to you. In your Onboarding can you throw up a Contextual feedback question to clarify what is driving them?
    The second point is that these method are well-known and consistent, once you’ve nailed your EXACT version (iterate fast with tools like Contextual to “test-and-learn” don’t get bogged down roadmapping and coding the tests)  then make it repeatable across the product Onboarding and Re-engagement processes. Identify the common questions and use-cases and standardize them!

    Clearly stated by my friend @chrissaad he expands this thinking/expectation to all SaaS products. Products for B2B can often be super-complex and feature rich (Contextual is an example) – but the job of the Product Team is to make the experience as standard as possible and align it with the messaging as the user comes down the acquisition funnel.

    If you apply your particular insights based around FOMO and standardize you may just nail your engine of growth.

    ** Reddit raised $250M off the back of the WSB phenomenon. Social network’s ability to influence group behaviour and now long established markets is analogous to the 2011 Arab Spring.

    *** BTW “variable rewards” is a well-known tool in gamification.

  • A product led indie developer journey

    A product led indie developer journey

    This second part of interview with fintech product Navexa’s founder gives insight into what it takes to be an indie developer.

    Bootstrapping a product and startup in one of the most courageous things to do in tech and something employees never really understand.

    Navarre gives me insight into his journey developing Navexa as an independent and how he has funded things so far.


  • The best gamified onboarding in a fintech product

    The best gamified onboarding in a fintech product

    The onboarding for fintech product Navexa is gamified and sublime. In this interview I discuss with the founder the decisions that led to making a first-time experience that has helped radically increase activation and reduce trialler abandonment.

     

    Navarre Trousselot is the founder of portfolio tracking product Navexa and he takes us through the main features of the checklist/progress-bar above.

    Key takeways:

    1. Initial modal to set the stage and introduce broad concepts.
    2. Sample data to avoid the dreaded “empty state”
    3. By clicking the first modal, the user sees the sample data as “their portfolio”.
    4. This completes Step 1 (View Portfolio) and instantly credits the user with a 1-day extension to their trial.
    5.  Each additional steps extends the trial – with a total of 7 days making the trial a 14 day trial for someone who is genuinely engaged.
    6. When a step is completed you can instantly see down the bottom that the trial has been extended “10 free trial days left”.

    The benefits here are huge – instead of being overwhelmed by all the data and features, the user can self-pace a journey that gives a reward along the way.

    https://vimeo.com/488808379

    Some other things we discussed:

    1. The checklist (when folded) has an animated wave wash across it every 10 seconds. Its not too shouty but the user definitely knows there is something to look at there.
    2. Navexa’s Feedback collection is probably one of the lowest friction I’ve seen. Its notoriously difficult to get a user’s perspective and this method allows easy collection of both one-liner suggestions and long form rants. Navarre mentions how people have given full specs for a feature they want through that mechanism and he gets it submitted to both his email and ticketing system.

    The Indie Journey

    In the next clip of the recording, Navarre gives me insight into his journey developing Navexa as an independent and how he has funded things so far. Sign up for blog updates so you don’t miss out! 

    Are you looking to get more users to love your mobile and web apps?  Click on the buttons below to get your 14 day free trial or contact us for a demo! 


    Get Started


    Get a Demo


    Contact Us

  • Product Managers as storytellers

    Product Managers as storytellers

    Google Product Manager for Duo, Amit Jaiswal does a walkthrough of the importance of storytelling skills in Product Management. 

    As we’ve discussed elsewhere with Atlassian’s PM Lead –  Product Managers have many touch points with company and product stakeholders – Amit suggests how a Product Manager should be communicating internally and externally. 

    Often a Product Manager does not have the organisational clout (power/authority) they need to get concensus. So Amit suggests that the communication style must be: “lead by influence, rather than lead by authority”.

    Audiences

    Amit outlines several audiences for the Product Manager:

    1. investors or supporters of the product (the first ones that must believe to get the product team funded and built)
    2. Customers, prospects
    3. Internal team members (and its role in staff retention).

    The last point is particularly interesting post-COVID – in previous years all the cool companies were able to create perks for staff such as funky offices, fully equipped kitchens, free lunches. When everybody works from home you must be very sure that your product mission is compelling to your team members! ????

    MVPing your story

    Amit runs through some structural elements he learned to do with not overbaking your story and in startup parlance, create an “MVP” (minimum viable product, or perhaps “minimum viable pitch”).
    Amit mentioned a few sources:

    The course: Storytelling for Influence

    The online book: Resonate: Present Visual Stories That Transform Audienceshttps://vimeo.com/486249258

    Banner Image Credit: http://www.discipleblog.com/

  • Ionic Capacitor support(All your OSes are belong to us)

    Ionic Capacitor support
    (All your OSes are belong to us)

    UPDATE July 2022: 

    We are sorry to update that we are no longer supporting Ionic as a Contextual platform.

     


    No…that’s not a typo. Old memers and gamers will remember “All your base are belong to us”.
    It’s our cheeky way of saying that only Contextual supports all that platforms that you need coverage for Announcements, Guides, Feedback and Contextual Help.
    Today we are announcing beta support for Capacitor JS with a V2 plugin!

    Native IOS Apps for iPhone and iPad. Also with the November Macbook announcement using M1 chip, it hints that IOS Apps may run on MacOS soon. Contextual integrations instructions are here. We support Swift and Objective C in a just few fast Mb.

    Native Android Apps for phones and tablets. Contextual integrations instructions are here. We support Kotlin and Java with an SDK of just few hundred fast kilobytes.

    Contextual has a WebSDK that supports all of the main browsers at runtime: Chrome, Safari, Mozilla, Edge etc. We havn’t checked Tor ????. Integration docs are here.

    With our Chrome/Edge extension you can get started even without adding the SDK. 

    ReactNative was open sourced by Facebook and is a super popular hybrid platform for Javascript developers. The main benefit is cross-platform development but with true native user interface widgets and is very fast. Today this is a super-popular platform for B2B App development teams. Integration of our SDK is here.

    Apache Cordova (once called Phonegap) is the grand-daddy of hybrid app platforms and until recently had sponsorship from Adobe via Phonegap Build.

    Whilst not as fast as Native or ReactNative, Cordova remains a very popular platform because of Apache open-source support. Integration of our SDK is here.

    Ionic is a well-funded development environment that breathes more life, UI elements and speed into a  Cordova style model. We support Ionic via our Cordova integration. Ionic support migration from Cordova to their Appflow.

    ionicons-v5_logos

    And….now….Capacitor is a key part of Ionic’s infrastructure. It is the obvious (only??) heir-apparent to Cordova that will be aggressively maintained. 

    Capacitor is billed as “an open source native runtime for building cross-platform mobile and Progressive Web Apps, with JavaScript, HTML, and CSS.”

    It has a lot of build similarities to Cordova, so migration appears to be relatively painless.

    Credit: https://capacitorjs.com/

    So with Contextual supporting Capacitor, this gives Native Mobile and Hybrid mobile developers the richest choice for engaging users with Onboarding, Announcement, Guides, Coachmarks, Tooltips.

    Our beta docs for Capacitor are here

    Platforms not supported by Contextual (today)

    NativeScript is in Beta currently on Android. We are not sure if NS has a long term future, but some big Apps like SAP use it. Docs for Android are here.

    We dropped Xamarin support a while ago. We were bullish on it at one stage because we think a lot of Mobile Digital Adoption in enterprises will come from C# developers, but there is a lack of interest and lack of active OEM support from Microsoft – frustrating for us – if you have a solution, please let us know.

    We are super excited about Flutter and it’s on the roadmap – the integration is pretty deep for us, so it will take some time to get right.

    Unity is a major platform for gaming and VR (using C# or JS), its not currently our focus but we are keeping an eye out.

    Same for Unreal Engine which uses C++. Neither of these are really used in Mobile B2B, B2C apps, in B2C its commonplace for games but most customers are using the platforms we support.

    Can’t I just use a Web Onboarding solution for Mobile?

    Ask other vendors whether they support offline mode, poor networking, variable form-factors (portait vs landscape).

    Contextual will intelligently pre-fetch and buffer content and analytics on mobile because that is the right thing to do. A web-only approach (even on hybrid platforms) is unreliable to these realistic conditions on mobile.

    How do I integrate with a Capacitor App?

    Firstly we are not supporting V1 Capacitor, we are going for V2 only (at this stage)

    The creation of this plugin is really building on the Cordova technology we’ve had in production for a long-time and should not have too many problems. But it is beta. So feel free to check is out and give feedback to our support folks – we want to make this a great one!

    Our beta docs for Capacitor are here