Artwork

Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Player FM -팟 캐스트 앱
Player FM 앱으로 오프라인으로 전환하세요!

Discovery for Technical Platform Teams

52:41
 
공유
 

Manage episode 371485591 series 2522423
Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.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

126 에피소드

Artwork
icon공유
 
Manage episode 371485591 series 2522423
Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Anthony Moendir & Tim Beeren, Anthony Moendir, and Tim Beeren 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.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

126 에피소드

모든 에피소드

×
 
Loading …

플레이어 FM에 오신것을 환영합니다!

플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.

 

빠른 참조 가이드