Key Takeaways

Saim Abbasi credits his mechanical engineering background for one specific skill that has been more useful than any other in building companies and evaluating investments: the ability to think in systems. Not in components, not in events, but in systems, meaning the relationships between components and the feedback loops that determine how the system behaves over time.

What Systems Thinking Actually Is

Systems thinking is the practice of looking at any situation and asking not just "what is happening?" but "why does this keep happening?" and "what is maintaining this behavior?" The discipline identifies the feedback loops, the delays, the reinforcing dynamics, and the balancing forces that determine whether a system stays in one state, oscillates between states, or spirals toward an extreme.

In a business context: a company that has recurring customer service problems is experiencing the output of a system. The system-thinking response is to find the input that is generating those problems repeatedly, not to hire more customer service people to handle the output. The hiring is treating the symptom. Finding and changing the input is treating the cause.

People Problems That Are System Problems

The most practically useful application of systems thinking in company building is recognizing when a problem that looks like a people problem is actually a system problem. If the same type of mistake keeps happening with different people in the same role, the role is the problem, not the people. If a behavior that leadership tried to discourage keeps reappearing after each intervention, the incentive structure is the problem, not the individual people.

Intervening at the Leverage Point

Systems theory identifies the highest-leverage intervention point as the feedback loop, not the output. In practical terms: if customer retention is declining, the highest-leverage intervention is not more outreach to churning customers. It is understanding and fixing what is driving the decision to churn in the first place. That is the feedback loop. Treating the output without addressing the loop is work with no compounding effect.

"Change the system and you change the behavior. Change the behavior without changing the system and the behavior comes back."