A world of accelerating change demands a new generation of management with the skills to drive decisive action and elevate performance. Managers tasked with delivering results collide with peers whose conflicting goals, perspectives, and incentives freeze progress and create a glacial pace of change. New thinking and practices are needed to act in alignment. You can't copy-and-paste a solution, and you can't do it alone. To collaborate effectively you need to create a shared map of the territory, you need to pick your battles, you need Flow Engineering In this new book by value stream experts Andrew Davis and Steve Pereira, readers will discover profound yet practical applications of systems thinking, psychology, and organizational design. With a step-by-step guide to visualizing the outcomes, processes, and dependencies, Davis and Pereira use case studies from across industries to show readers how to unlock innovation and optimal performance. Learn how to co-create value stream maps of the hidden relations and interactions that constrain your teams, maps that everyone can align with and act on. Reach across the whitespace in your organization and replace friction with flow using Flow Engineering.
(if you're going to listen to the audiobook, subtract 1 star; if you're looking for one single book that synthesizes concepts related to the flow of work in modern IT, add 1 star)
I didn't fall in love with this book. It feels very "dry" & mechanical (but I think this flaw is less painful in the Kindle/paperback versions because of all the diagrams and sketches), the wording is very enterprise-y, and all the concepts have already been presented many times. What is more, sometimes the authors are (apparently on purpose) mixing concepts that probably should not be mixed - e.g., when they look for the correspondence between the individual state of "flow" and the flow, as defined by Goldratt/Reinertsen.
Another very specific thing about this book is that it does not try to prove anything—it simply states opinions as they don't need any confirmation/proof. This is a manner typical for many consultants, and it works quite nicely for the vast majority of the time until, e.g., they start advocating for SAFe.
The main topic of the book is, in fact, not the "flow" (btw. if you really want to upskill in this area, I strongly advise you to read Reinertsen's "Flow"), but Value Stream Mapping. There's nothing particularly wrong about that, but as in the case of many other concepts mentioned in this book, they are presented mostly as "terms" with some explicitly named advantages - one can't resist the impression that actual implementation is beyond the scope of this book, so it's main role is to attract new customers for the consulting services (provided by the authors and their associates).
3 stars. It's not the best book by IT Revolution Press, but it is not the worst either.
The book tackles the issues businesses face when scaling up, emphasizing the productivity and collaboration challenges that arise. It argues that individual efforts can't match the collective output of well-coordinated teams, even if individual efforts are more significant.
The authors rely on past studies to support their points, focusing on the elements of a productive team: purpose, shared views, and value/clarity and flow. They identify three main challenges when scaling: alignment, visibility, and on-ramp gaps. Addressing these requires solutions that meet budget, schedule, and scope constraints. The book suggests integrating feedback loops and control systems, drawing inspiration from Lean implementation and Kotter's eight steps for driving change.
Cybernetics is discussed as a means of enhancing collaboration between humans and IT through feedback loops. The book's concepts of value, clarity, and flow echo Marcus Aurelius' ideas of right judgment, action, and willingness. As organizations grow, individuals and teams may drift apart, losing focus on their original goals.
The book promotes value stream mapping (VSM) as a tool to help businesses maintain focus and alignment. VSM, part of Lean manufacturing, is vital for understanding and improving business processes. It visually represents systems, facilitating better communication and collaboration.
Key takeaways at the end of each chapter offer valuable insights without rereading the entire text. Readers can jump to Part 2 for practical guidance on implementing these ideas. The book conveys a "Seven Habits" vibe and highlights the existence of an ISO standard for value stream mapping (ISO 22468:2020).
Overall, the book offers a straightforward approach to process mapping that simplifies traditional methods. While it doesn’t introduce groundbreaking ideas, it provides a practical method for improving mapping processes. Part 3 focuses on leadership and management, offering useful suggestions, though it leans toward promoting their method.
My review is for the audiobook version. I am quite familiar with the topic as a management consultant doing business transformation, but I would recommend reading the paper copy, not the audiobook. There are too many references to visuals that I think I missed some of the points because of it.
I can imagine this book loafing on the performative bookshelf harboured by every modern CEO. Something to flip through, and perhaps studied deeply/memorized by a very few.
I must admit my pleasure was hampered by the galley copy. At least 1/3 of the text is figures. But the galley copy doesn't render them. Half the time, the reader can't understand the text for this reason alone.
The rest ... there's a lot here. There's a structure for each section. There's lists and takeaways. And the (dreaded) figures, in all their absence. But like many such texts of its ilk, this would be better off as a course or workshop series. I'm not going to remember anything, let alone apply it.
Also, there were a few contradictions. For example, "making the map" is more important than the map itself ... but in the next section, we're advised to "share the map" as resources.
The authors know what they're talking about, nonetheless. Take this apt quote: "The role of leadership is to assume the risk and responsibility of guiding others safely in a beneficial direction, in spite of great uncertainty." And this one: "There are two types of challenges: situations where you don't know what to do, and situations where you know what to do but don't want to do it." (I'd really love to know how to tackle the second one ...) The form their insights took here didn't work for me, but it may for others.
Thank you to Edelweiss+ and IT Revolution Press for the advance copy.
A modern refresher to value stream mapping and project execution
Steve and Andrew have done a great job of condensing a complex topic into a book (with a good flow!).
I love the generalizations in the book such as prescriptive to generative solutions to scale or cybernetics before jumping into Flow Engineering.
The authors have done a great job of providing a prescriptive model, a blue print to implement Flow Engineering in any organization.
This book has a wealth of references from Steven Covey, Peter Senge to Simon Wardley. Be prepared to hit your library and pull out the references. I really enjoyed learning the “Liberating Structures” structures. Thanks to the authors for introducing me to the subject.
As a change practitioner, I did not appreciate repeated statements like “three months is long enough for change/transformation”. I wish the authors touched on people side of change and introduced/referenced change management discipline so support the amazing process oriented flow engineering discipline.
Flow Engineering offers an accessible and practical introduction to Value Stream Mapping (VSM) and its application in modern software engineering. The book effectively bridges Lean Management principles with the unique challenges of the software industry, making it a valuable resource for engineers, managers, and team leaders alike.
One of the standout aspects of the book is its focus on Outcome Discovery and Outcome Maps—two powerful tools that helped me personally identify strategies to scale a software organization. By leveraging these tools, the book shows how to break down complex workflows, visualize dependencies, and pinpoint bottlenecks that can hinder scalability.
Rather than sticking to theory, the author provides actionable insights with real-world examples that make it easy to see how these concepts can be applied directly to scaling software teams. For anyone looking to optimize their processes, improve cross-functional collaboration, and support sustainable growth in a software organization, this book offers indispensable advice.
I started reading this as I'm in gauging in a pretty extensive project that will require various mapping to both understand the problem and understand if we've attained a solution.
I got about halfway through this book and I realized a couple things. First it felt over complicated. Perhaps it's written for engineers who want a more technical view of a tool or have little or no concept of mapping not for someone who's been doing it for a number of years.
Second I felt that it was very sterile. Perhaps it was more the way the narrator read it, but there was very little excitement about using these tools. Perhaps it was written more as a textbook with a case study, but I just found my attention being focused on other things.
On the plus side, there is a ton of very good resources that go with the audiobook. Quotes, references, tables, and other things are almost a book within the audiobook.
There may be a time I choose to listen to the entire book again, but right now is not that time.
If you’ve ever been part of a team that’s “trying to improve” but keeps spinning in circles, this book is for you. Flow Engineering gives you five really simple and visual tools to actually figure out where things are stuck and how to fix them without overcomplicating it.
The authors walk you through each map step by step. You start by getting clear on your goals, then map your current state, dependencies, and what a better future might look like. Finally, you lay out a plan that your team can act on. It’s smart, practical, and doesn’t waste time.
What I liked most is that it’s not just for software teams. I can see this working in marketing, operations, customer support pretty much any group that needs better flow and less chaos.
A couple things to keep in mind: it’s packed with info, so if you’re brand new to this kind of thinking, maybe start slow. I wouldn’t mind a super lightweight version just for small teams. But again, overall, its usable by all teams regardless of size and should be a go-to reference on every leader's bookshelf.
A Fantastic book! "Flow Engineering" makes sense of the chaos within organizations. It's a practical, guide to aligning teams on outcomes, delivering continuous value, and improving iteratively. Combining insights from both physical and digital engineering, it consolidates years of learning into an accessible volume. The book focuses on creating a flow-centric culture of collaboration and innovation, using value stream mapping and emphasizing the human aspects of development. Whether you're a startup founder or a seasoned coder, this book is a game-changer for software development. Highly recommend!
This book does a great job of outlining both the benefits of flow engineering and in providing a step-by-step guide to understand and implement into any organization, regardless of industry or size. It balances theory and practice in a way that’s digestible and actionable. It provides practical tools we could use to help eliminate waste and improve collaboration and output, without flowery exec jargon. Highly recommend!
As someone who has worked in software for over 40 years, I can safely say that I wish this book was available back then, or at any point in my early career. It is easy to read, insightful, and extremely practical. It addresses the complexities of cross-functional teams, scale, and provides a framework for improved collaboration, and output. A must read for anyone in the space.
This is one of those books that you read when you have the time. In my case, some of this was review and in others, it brought together concepts I had thought about but not integrated in my own thinking. Anyone involved in software development or product management should read this book
a lot of great ideas and relevant insights. wish there was more practical discussions about how to navigate common challenges in rollout but overall a good framework and introduction to the practice.
A great collection of practices and theory around how the flow of value can be mapped and improved incrementally without any fluff. I'd been waiting for this book to come out for a while and was happy to receive an advanced copy through IT Revolution press.
This book gives some useful case studies of flow engineering in the real world and ties back to many of the places of origins from various practices and ideas so you are getting a qualified book to help you on your own personal explorations and learning journey.
I read this book after the Wiring the Winning Organisation and I find Flow Engineering to be much more approachable. It is a shame that there are references to SAFe in the book but that is more a personal choice. I would recommend this book to anyone in the ways of working and architecture space as a compliment to a set of sociotechnical practices that are emerging in the community.