hyphacoop/distributed-press-organizing

Petr - Onboarding

Closed this issue · 0 comments

pp2tech commented

🎟️ Re-ticketed from: #
📅 Due date: aprox. 15-20th May
🎯 Success criteria: Can move to hyphotesis formulation step

Task Summary

...

To Do 1st - MEET THE TEAM :)

  • Ben (DP idea father, now not involved daily)
  • Andi (our relationship holder)
  • Muave (tech lead - Sutty)
  • Fauno (prod.leaad - Sutty CMS)
  • Aki (the only DP full time dev)
  • Ania (comms, and ProjM)
  • UX Team (Sutty) - Elio, Edu, Dili
  • ... ?

To Dos to Understand Business Fundamentals

To Dos to Understand the Product deeply

  • Get full product access, work through tutorials (? if exist)

  • Understand product architecture

  • n/a Any regular public product on-boarding webinars? (weekly/monthly)

  • Get in-depth product demos from respective PMs to understand the core value proposition

  • Get the feeling for the main customer problems that the product solves

    • here is the issue, most people DP would like to target (journalists, collectives, etc.) like the idea but don't feel the problem, or they don't care about our solution at all

  • Understand the main product features and main product limitations // Are they intentional (strategy) vs genuine gaps? - N/A

  • Understand the product roadmap - what and why things are on the roadmap? 

  • Understand the product onboarding 💯 NUX (New User experience) from all onboarding paths // Friction points // Setup Moments // Aha moments -- N/A

To Dos to Understand Customers from internal (Hypha/Sutty) point of view

  • Understand buyer and user personas

    • we will have to figure this out after narrowing down the focus of the DP offering

  • Understand customer journey (maybe a map exists?) - map does not exist (except basic Sutty's onboarding)

  • Understand (or start creating) the Ideal Customer Profile(s) (ICP) // from Hypha's perspectivef and rom Sutty's perspective (and will probably need independent from product perspective)

      • we will have to figure this out after narrowing down the focus of the DP offering

  • Understand the JTBD. // Why are customers hiring DP ?

    • our assumption for next steps will be that "Customer hires DP to get the comprehensive distributed web/blockchain publishing capabilities from which she can pick&choose where to publish in addition to traditional web2 publishing." // The proposition can be adjusted for Sutty's B2B offering, where it will include CMS frontend. I assume B2C offering of Sutty is unchanged by new DP's direction.

  • Understand what users most love about the product? - right now users mostly like the idea, not the product

  • Understand what users most wished the product could do for them

  • Understand conversion friction - N/A

  • What stops customers from buying? - N/A

  • Why do customers churn? - N/A

  • What interviews have we done with churned customers? - N/A

  • Has anything proven effective in churned user resurrection? - N/A

  • Any surveys in place? - N/A

  • Messaging - from internal perspective = Do we feel we have message-market fit? - N/A

  • Is that language/message perpetuated throughout the product itself? - N/A

  • What are the best performing channels (organic & paid) and what channels were tried? - N/A

  • What paid channels were tried but didn’t create good ROI? - N/A

To Dos to Understand Customer from customer side (by talking to them)

  • Participate in customer success calls (aka ride-along) // who's doing them? - N/A
  • Who knows the following answers - or has/should have informed opinion on it? -> What makes customers successful? // What best practices do customers employ? // Why do some customers not realise value from the product? // What are the biggest issues customers face? // What is the pitch? // What messaging works best?What is best avoided? - N/A

To Dos to Understand available Product Metrics

  • Get access to existing dashboards / check use cases - N/A

- [ ] Get access to the full analytics - product, marketing, website - stack (or whatever exists) // I think someone mentioned Plausible ( https://plausible.io/) - does anything else exist (automated)?

  • DP API usage stats

  • DP website stats

  • DP docs site stats

  • Understand data events and relevant guidelines // Structure, naming, level of abstraction etc...Is this shared and used across all teams consistently? -- N/A

  • Understand basic usage and retention metrics (or see what should/can exist and be created)
    Global -- N/A, does not exists

  • By new user signup cohort

  • By type of account

  • By type of company

  • By activation event completion

  • By frequency of specific activities

  • Per feature

  • By acquisition channel

  • By new / resurrected userUnderstand the experience funnel and all stage conversion metrics

To Dos to Understand Ways of Working (WOW) of product and other teams (what teams. exist?)

  • Understand product org KPIs / OKRs, process and tooling
  • Understand how the product and marketing teams are structured today
  • Org / reporting models + Ideas/ backlog management
  • Understand the model for any shared resources -> like usually Design? Data? Website?
  • Understand the working methodology and cadence of work -> Sprint lengths? (Understand team velocities / tempos)
  • Understand the key meetings and get invitations
  • Understand any established patterns / norms for communication/collaboration and documentation