Flow Engineering: Collaborative Mapping for Effective Action at Scale - Steve Pereira & Andrew Davis


NEW EPISODE #173


“Three characteristics of an organization that is operating with maximal effectiveness are value, clarity, and flow.”

Are you feeling the strain of growth? Struggling to maintain alignment and efficiency as your organization scales? In this episode, I sit down with Steve Pereira and Andrew Davis, authors of the groundbreaking new book, “Flow Engineering”.

Learn why traditional scaling methods focusing on rigid coordination can actually hinder progress and how flow engineering offers a solution. We delve into the challenges and paradox of scaling, the core principles of flow engineering, its five primary mapping techniques, and the leadership mindset shift required to create a culture of flow engineering.

If you’re looking to overcome misalignment and optimize performance as you scale, this episode is a must-listen!

Listen out for:

  • The Problem with Scale
  • The Dangers of Increasing Coordination
  • The Paradox of Scale
  • Flow Engineering
  • 5 Primary Maps
  • All Maps are Wrong
  • 5 Principles of Flow Engineering
  • Leading Flow Engineering

Show notes & transcript: techleadjournal.dev/episodes/173.
Follow @techleadjournal on ​LinkedIn​, ​Twitter​, ​Instagram​, ​YouTube​, ​TikTok​.
Buy me a coffee ☕ or become a patron 😎.



3 Key Takeaways

  1. The Challenges of Scale

    As organizations scale up, there is an inevitable increase in distance between everything in the organization—distance between individual actions and their impact, distance between employees and the organization’s core mission, and even physical distance between colleagues, partners, and customers.


    This increased distance can be harmful if left unchecked. It often manifests as distraction, disorientation, and disengagement – three substantial human costs of scale.


    Distraction hinders our focus on things that matter and from getting things done. Disorientation caused by misalignment between people and teams. Disengagement stems from a lack of clarity regarding desired outcomes and their significance.

  2. The Dangers of Increasing Coordination

    Our default response to the challenges of scale is often to increase coordination. After all, increased scale seems to demand extreme coordination to manage the amplified complexity of communication and collaboration.


    However, it’s crucial to remember that collaboration comes at a cost, especially without a proper support structure of protocols and guidelines.


    Paradoxically, as the Ringelmann effect highlights, individual effort declines as group size grows. Our best work often emerges in less coordinated settings, where waiting times, handoffs, and shared responsibilities are less prevalent.

  3. Flow Engineering

    To achieve effective collaboration at scale, three elements are essential: value, clarity, and flow. This means having a clear sense of the value we are delivering, clarity on how our work fits into the bigger picture, and the smooth flow of actions.


    Building upon the foundations of cybernetics and the Toyota Production System, flow engineering offers a practical approach to achieving these elements.


    At its core, flow engineering helps teams bridge the gap between the current state and a well-defined target state through collaborative mapping exercises.


    The goal of the exercises is to establish a clear objective, identify gaps, and implement a feedback loop for continuous evaluation and course correction.



2 Quotes for Reflection



1 Tech Lead Wisdom

You don’t need to know all the answers.
There’s often a feeling if you’re a tech lead or in some position of responsibility, you’re expected to have the answers. You’re not expected to have the answers.
If you try to generate the answers, you’re almost certainly going to be wrong, and just basing it on your assumptions. And we operate so heavily on assumptions.
What you need to be doing is hosting the conversation, bringing together the conversation to clarify that.

video preview

SPONSORS

Manning

Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.

Get a 45% discount for Tech Lead Journal listeners by using the code techlead45 for all products in all formats.
https://mng.bz/ZYlj


Tech Lead Journal Shop

Are you looking for a new cool swag?

Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available.

Check out all the cool swags available by visiting techleadjournal.dev/shop. And don't forget to brag yourself once you receive any of those swags.

☎️ Book a 1:1 session with me

Tech Lead Journal Podcast

A weekly podcast about technical leadership and excellence. Check out on techleadjournal.dev. Find out more about me: links.henrysuryawirawan.com.

Read more from Tech Lead Journal Podcast

NEW EPISODE #175 “All data scientists and analysts should spend more time in the business, outside the data sets, just to see how the actual business works. Because then you have the context, and then you understand the columns you’re seeing in the data.” David Asboth, author of “Solve Any Data Analysis Problem” and co-host of the “Half Stack Data Science” podcast, shares practical tips for solving real-world data analysis challenges. He highlights the gap between academic training and...

NEW EPISODE #174 “Raise the bar of the team so that they bring sustainable practices. If your code stinks, no matter how you desire to be agile, you cannot respond to the change.” Dr. Venkat Subramaniam is a renowned figure in the software development community, an award-winning author and founder of Agile Developer, Inc. In this episode, Venkat sheds light on the frequently overlooked challenges of software development and provides valuable insights for succeeding in the field. We delve into...

NEW EPISODE #172 “The quality is connected to the risk, and the risk is connected to the testing. If we don’t keep an eye on quality, our testing and development will drift, because we are no longer building the thing that people care about anymore.” Mark Winteringham is a quality engineer and the author of “Testing Web APIs”. In this episode, discover how holistic, risk-based testing strategies can transform your software quality. Mark explains how to prioritize our testing by understanding...