Earlier this year, Andrew Davis and I sat down with the team at the GOTO Book Club for a conversation about our book Flow Engineering. That interview has just been released this week as a podcast, and I’m excited to finally share it with you!
In the episode, Andrew and I talk about why mapping workflows is so important, especially in today’s fast-moving software world, and how the five-maps method of Flow Engineering makes it easier for teams to see the big picture, align on goals, and create better flow. We also explored how AI may support mapping sessions in the future — and how collaboration, trust, and shared understanding remain the key needs.
Here are some of the key themes we covered:
Why mapping matters: Knowledge work is often invisible, which leads to gaps between contributors and decision-makers. Visual models help everyone agree on “what we’re doing and why.”
Five maps for value, clarity, and flow: We walk through Outcome Mapping (defining the “why”), value-stream maps, and forward-looking “future state” maps that help teams uncover obstacles and plan next steps.
Practical, not prescriptive: Flow Engineering is designed to fit into busy schedules and complement existing practices, rather than adding overhead.
AI’s emerging role: From virtual facilitators to smarter tooling, AI can enhance mapping — but it can’t replace genuine collaboration and conversation.
If you’re curious about reducing complexity, aligning stakeholders, and helping your team work with more ease, I think you’ll enjoy it.
👉 Watch the full video on YouTube here or listen on any podcast platform!
What do we not talk about enough that you wish we’d cover? I’d love to hear your thoughts and questions:
