About Applied End-to-End Flow
Applied End-to-End Flow is a framework for improving value delivery, the book series that explains how to use it, and the knowledge base that documents it. This page is about why we built it, how it operates, and how we work together.
Why we built this
We kept seeing the same patterns across decades of practice. A leadership team commits to a transformation. Training and new practices improve the team metrics, but the strategy remains stuck. Senior leaders ask what went wrong. Practitioners point at governance. Coaches recommend more training. Vendors pitch the next framework.
We wanted a field guide that connects diagnosis to action under real organizational conditions. A leader facing a constraint needs to know what is happening, who can change it, and how to test a response. Those questions shaped this framework.
The diagnostic names what is obstructing value delivery. The operating methods help the people with the necessary authority choose, run, and review a response.
What we built it to do
The framework connects diagnosis and response. Each improvement starts with the operating context, then proceeds through bounded work and evidence-based review. That makes the next decision part of the method from the beginning.
The three Guiding Principles on the homepage (Practical Actionability, Incremental Improvement, Context-First) compress this stance into pillar form. The framework's specific moves, the Three Barriers diagnostic, the Value Acceleration Process, the structural gaps under each barrier, are how those principles show up in practice. The knowledge base is where each piece gets the depth treatment.
How we work together
Every book, every article, every framework concept is co-authored by Curtis Hibbs and Joshua Barnes. We use the Lennon-McCartney model: both names go on every piece of work, regardless of who held the pen on a given section. The byline is Curtis Hibbs and Joshua Barnes. That's the structural truth of how the framework develops.
Applied End-to-End Flow doesn't fragment into "Curtis's part" and "Joshua's part." Concepts develop in conversation. Each one gets tested against the other author's field experience before it stabilizes. Disagreement is the editing process. Agreement is the publishing trigger. Both of us have to stand behind every line for it to ship.
Individual bios live on the authors page.