Systems approach to management
- Mar 31
- 2 min read
The problem of "false action"
Most management mistakes are made not due to a lack of intelligence, but due to a failure of focus.
When a company's revenue is falling or deadlines are missed, a manager's natural reaction is to target the problem area . But in 90% of cases, the pain point is merely a symptom, while the root cause lies deep within the business architecture.
Iceberg Model in Management
For system management we use a four-level model:
Events (Above Water): What happened? (Example: "The client left for a competitor.")
Patterns (Waterline): How often does this happen? (Example: "We lose 15% of our base every quarter.")
Structure (Underwater): What processes or rules create this? (Example: "The manager incentive system only rewards new sales, ignoring retention.")
Mental Models (Bottom): What are the underlying beliefs? (Example: "Management believes the market is infinite and the customer will come.")
A typical example: if a system generates unstable profits (Event), the cause is often a bias toward attracting new clients while ignoring the existing client base. We analyzed this structure in the article: Sustainable Income Architecture: A Systems Approach to Revenue.
Three Signs of a Systemic Failure in Business
Cyclicity: The problem returns every 3-6 months.
"Blanket effect": Correcting the situation in one department (for example, sales) creates a collapse in another (warehouse/production).
Personality Dependence: The process only works as long as a specific person is “looking after” it.
Algorithm for system diagnostics
(The Framework for Self-Analysis)
Instead of pressuring people, go through the checklist:
Connections: How does Department A influence Department B's results?
Feedback Loops: Does the manager receive a signal about an error immediately or a month later, when it is too late?
Delays: Do we understand that a decision made today (for example, cutting marketing) will only have a negative effect in six months?
Summary for the manager:
A systems approach is not about complexity, but about saving energy. * Instead of pressuring people , change the rules of the game (structure).
Instead of looking for someone to blame , look for a break in the chain of information transmission.
Instead of quick wins , design solutions that take long-term delays into account.
Result: You spend 80% of your time diagnosing and only 20% implementing the change. But this change eliminates the problem permanently, freeing up your resources for strategy.
If you feel stuck in manual management and firefighting, your company needs an architectural assessment. At CSFB, we help you redesign your system so it works for you, not you for it.
⚠️ A correct diagnosis is only 20% of success. To ensure a systemic solution truly works and isn't rejected by the team, use the methodology in our guide:
Comments