Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What to build next


Published on

When was the last time you and your product team dealt with the dilemma of deciding what to build next?

Here is a quick presentation stepping through some stuff to consider before jumping right in and getting things going.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

What to build next

  1. 1. Familiar question to a familiar problem What to build next?
  2. 2. Hi, my friends call me KC UX Manager @ Ezypay & iconnect360 Lead product design & user research Manage multidisciplinary teams
  3. 3. I’ll be honest The right answer of what to build next depends on your company, context, customers, etc I have no idea what they are (But happy to chat) But here are 5 things to consider
  4. 4. #1 Will your customers/users value it? To the extent they will sign-up, use it, and even pay for it?
  5. 5. If you’re not sure about customer/user value… Come up with a MVP to validate your hypothesis A quick interview Sketch or prototype Guerrilla user testing Get out of the building Follow them home! Eliminate that uncertainty. Quickly. Maybe even tomorrow.
  6. 6. #2 Is it aligned to your vision or mission Having a purpose is good, only if you’re moving towards it
  7. 7. If you’re not sure about your product’s purpose… Our mission: to inspire and nurture the human spirit — one person, one cup and one neighborhood at a time. - Starbucks "Our vision is to be earth's most customer centric company; to build a place where people can come to find and discover anything they might want to buy online." - Amazon To bring inspiration and innovation to every athlete in the world." - Nike It might be worth a think. Purpose is good. Shared purpose is better.
  8. 8. #3 What does your team members think? Are you collaborating? Is there check & balance?
  9. 9. If you’re not sure what your team members think… You might be working in separate silos and not being aligned. Buy-in is crucial Bring everyone in the journey Don’t always go with the HPPO Open your communication channels Bridge your process gaps Everyone’s role – Delivering customer/user value
  10. 10. #4 Have you considered underlying costs? Building a feature doesn’t end there, there are other costs – Support, regression testing, complexity, etc
  11. 11. If you’re not sure…the more the features, the higher the underlying costs F F F F F F F F F F F The work of implementing a feature initially is often a tiny fraction of the work to support that feature over the lifetime of a product, and yes, we can "just" code any logic someone dreams up. What might take two weeks right now adds a marginal cost to every engineering project we'll take on in this product in the future. Kris Gale, VP Engineering, Yammer $ F
  12. 12. #5 What about change management? Whether you’re changing your product’s UI, or having customers change from other products
  13. 13. If you’re not sure about change management… Sign-up Logged-in Logged-in second time Plan and scope for change management. Invest in designing first-time user experiences and communicating change. 40-60% of users who sign up for a free trial of your software or SaaS application will use it once and never come back.
  14. 14. 5 considerations, before deciding on what to build next 1. Will your customers/users value it? 2. Is it aligned to your mission or vision? 3. What does your team members think? 4. Have you considered underlying costs? 5. What about change management?
  15. 15. That’s it folks! More than happy to answer questions or catch-up later