Let me start with this, The Flow System, or TFS, is not another framework or methodology. It is a toolbox that enables companies and organizations to address challenges at the lowest level practical.
Fixing a struggling company is not easy, but it is not impossible either. Often, an organization needs better tools. Tools are useful in a particular context, which explains why a tool may create value in one instance. Differently, the same tool could cause damage.
For this series, we’ll be referring to the Flow Guide (https://flowguides.org). It is the starting point to help build an understanding of TFS. I want to credit Brian Rivera, John Turner, and Nigel Thurlow for their work in building the system.
This purpose statement explains TFS better than anything I could write:
Achieving a state of flow occurs when organizations/institutions produce outcomes in which their constraints (e.g., structure, processes, environmental effects) are shaped in a way that enable employees to concentrate on their own interactions among one another and the customer. Flow ultimately results in employees concentrating on the act of doing rather than combatting or succumbing to organizational friction.
Many project management methods and agile frameworks concentrate on taskwork and the illusion of planning with no regard to how an organization is structured to support these activities. Organizations/institutions utilize teams but fall short in developing teamwork skills and fail to restructure leadership to maximize the benefits that can be obtained from the utilization of teams. These shortcomings introduce additional constraints and barriers that prevent organizations/institutions from achieving a state of flow.
The Flow System™ provides a re-imagined system for organizations to understand complexity, embrace teamwork, and autonomous team-based leadership structures.
The Purpose of The Flow System
What The Flow System Is Not
TFS is not a replacement for other methodologies or frameworks. It may highlight a weakness in how the use of a process is suboptimal or, worse, failing. At that point, choices are on the table.
As well, TFS won’t “fix” certain organizational behavior. It can move people toward different ways of work if the business is willing to change.
Additionally, TFS can’t save a company from failing products or services. It is up to the employees to decide to use the tools provided by TFS. They can help resolve those issues.
For my kick-off posts on TFS, click on this link – Agile Value #4 – Embrace Change Like Life Depends On It and this link – Plunge Into The Flow To Find Insight.
