Artwork

Content provided by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Discovery for Technical Platform Teams

52:41
 
Share
 

Manage episode 371485591 series 2522423
Content provided by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
There are two pillars in this episode. We start with the Technical Platform at bol.com. We'll explore what type of software engineering these teams are working on and what they are trying to achieve for the rest of our engineering community. The other part is Product Discovery. We try to figure out what problems we are solving in the discovery phase. While doing this we keep our focus on the Technical Platform and try to uncover how these specific challenges are solved.
What this episode covers
  • The Technical Platform:
    • What are we trying to achieve by having Technical Platform teams?
      • Which product are they working on?
    • How differs their setup from product teams?
    • Are there other things that are different?
  • Product Discovery:
    • What – in general – are we trying to achieve during Product Discovery?
      • Which problems are we solving?
      • What roles should be involved to do this well?
      • How to document those?
    • What are the questions we ask ourselves during this phase?
    • How to keep a good pace? The “customers” are facing a problem now and also expect an instant solution.
    • Is this different for Platform Products?
      • What aspects need additional attention?
      • How well do engineers in the Platform Space know the challenges engineers in product teams are facing?
        • How to get a common understanding of their problems?

We wanted to stay away from discovery techniques as Double Diamond, Triple Diamond, Opportunity Solution Tree, Hypothesis Prioritization Canvas. Let us know if you want a specific episode on these techniques.

Guests


Notes
  continue reading

121 episodes

Artwork
iconShare
 
Manage episode 371485591 series 2522423
Content provided by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
There are two pillars in this episode. We start with the Technical Platform at bol.com. We'll explore what type of software engineering these teams are working on and what they are trying to achieve for the rest of our engineering community. The other part is Product Discovery. We try to figure out what problems we are solving in the discovery phase. While doing this we keep our focus on the Technical Platform and try to uncover how these specific challenges are solved.
What this episode covers
  • The Technical Platform:
    • What are we trying to achieve by having Technical Platform teams?
      • Which product are they working on?
    • How differs their setup from product teams?
    • Are there other things that are different?
  • Product Discovery:
    • What – in general – are we trying to achieve during Product Discovery?
      • Which problems are we solving?
      • What roles should be involved to do this well?
      • How to document those?
    • What are the questions we ask ourselves during this phase?
    • How to keep a good pace? The “customers” are facing a problem now and also expect an instant solution.
    • Is this different for Platform Products?
      • What aspects need additional attention?
      • How well do engineers in the Platform Space know the challenges engineers in product teams are facing?
        • How to get a common understanding of their problems?

We wanted to stay away from discovery techniques as Double Diamond, Triple Diamond, Opportunity Solution Tree, Hypothesis Prioritization Canvas. Let us know if you want a specific episode on these techniques.

Guests


Notes
  continue reading

121 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide