Kyle Evans

35 posts

Kyle Evans banner
Kyle Evans

Kyle Evans

@ProdityCo

Product Management and AI consulting, education, and workshops. Discussing technology, UX design, and philosophy on my podcast and newsletter.

Katılım Ağustos 2023
29 Takip Edilen12 Takipçiler
Kyle Evans
Kyle Evans@ProdityCo·
Why do so many product teams struggle with communication? Or creating an effective strategy? Or balancing priorities? Issues I'm sure many of us have faced. And what I discussed with Christoph Steinlehner recently. So many great product topics: open.spotify.com/episode/5kVYIU…
English
0
0
0
8
Kyle Evans
Kyle Evans@ProdityCo·
Had an incredible conversation with the founders of OAK THEORY - Hannah Ryu and Veronica Shelton. Hannah and Veronica break down the latest trends in design, from the rise of AR to the subtle shift toward softer, more organic visuals. open.spotify.com/episode/6JGE9z…
English
0
0
0
20
Kyle Evans
Kyle Evans@ProdityCo·
It's hard to believe we're at episode 100! Who would have thought? Not me. To celebrate, we've decided to talk about a few things we've learned through the past 100 episodes and highlight some of the discussions that have been part of the journey so far: open.spotify.com/episode/6Jzj92…
English
0
0
0
4
Kyle Evans retweetledi
Paweł Huryn
Paweł Huryn@PawelHuryn·
I hate the word "requirement" in a PRD. The advice from popular websites on adopting a heavy, waterfall approach only deepens this frustration. They insist on documenting every detail: - Requirements - User stories - Acceptance criteria - Data flows - Dates and milestones ...all supposedly crafted solely by the PM. Where to start? The name ”Product Requirements Document” might be misleading. Because it’s not about documenting the “requirements.” Empowered product teams are led with the strategic context, given problems to solve, and are held accountable for the outcomes, not the output (features). They start with a generic problem, perform product discovery together, explore the problem and solution space, and run experiments to validate their assumptions before the implementation. To product people, the idea of waterfalling requirements from stakeholders to the product team or from PMs to other team members by writing detailed documents should sound absurd. Of course, I get that some initiatives need to be summarized. But a good PRD is a living document that captures your product discovery journey. It explains why the initiative matters, the objective, and how the success will be measured (key results). It's not a rigid contract. And it shouldn't replace open communication and building alignment. Actually, collaboration is key. And it’s way more important than documentation. --- What do you think about replacing the term PRD with something that better captures its essence? Product Initiative Brief? Product Discovery Canvas? Something else? Let me know in the comments. 🧵
Paweł Huryn tweet media
English
7
24
173
25.9K
Kyle Evans
Kyle Evans@ProdityCo·
In this episode, Ryan Glasgow, the founder and CEO of Sprig, shares his insights on product management and experience scaling companies like Weebly and Vurb from startup to successful exit. Ryan also explains the importance of product-market fit and meeting user needs.
English
0
0
0
42
Kyle Evans
Kyle Evans@ProdityCo·
Hubert Palan, founder and CEO of productboard, and @kylelarryevans explore the evolving landscape of product management and its impact on the tech industry. We discuss the evolution of product management, the importance of gaining a deep understanding of customers, AI, and more.
English
0
0
0
30
Kyle Evans
Kyle Evans@ProdityCo·
In this episode, Vidya, founder of Product Rebels, shares her experience in coaching product teams and transforming organizations. We explore the importance of understanding the customer problem and achieving product-market fit.
English
0
0
0
11