On Twitter @alshall stimulated an interesting conversation about Inherent Simplicity here:
It prompted me to write down the following:
Inherent Simplicity (IS) is used to deduce the Constraint. But if you want to apply IS, you have to start from the Constraint.
Because the founding force of IS relates to the degrees of freedom that a system has. The less the degrees of freedom, the more IS is applicable.
And the Constraint is the element of the system that mostly limits its degrees of freedom.
Why is this important?
Because of leverage.
Acting on the Constraint has the greatest systems effect; in virtue of the fewer degrees of freedom.
That’s why if you want to apply IS, then thinking and action need necessarily to be centered around the Constraint.
There is a difference between logically deducing IS in theory, and practically applying it in reality.
IS application needs focus on Constraint. Otherwise impact will be limited; and you’d need to do more work to get the same effect.
That’s the idea and power of IS: the economy of action!
That is the simplicity: you do one little thing on the Constraint and you get greater effects. The opposite is to improve everything, everywhere, all the time, and get nowhere while piling up layers of Operational Costs for nothing.
You cannot apply the idea of IS without centering it around the constraint.
Of course, first you need Step 1: Identify the Constraint. In knowledge-work, that is elusive, as you know.
And it is THE problem that #tameflow resolves.
TameFlow does to knowledge-work what TOC has done to manufacturing, sales, marketing, project management, supply chain management, etc.
TameFlow is the only approach that will let you perform Step 1 in knowledge-work.
What do you think about this?