We Can Do Impossible Things: A Systems Thinker's Self-Breakthrough

Systems thinkers tend to self-limit; break the 'impossible' assumption through small experiments and leverage points.
The article explores a common self-limitation dilemma among systems thinkers: they're skilled at analyzing risk but become overly cautious, treating 'impossible' as a default assumption. The author notes this mindset stems from over-focusing on feedback loops and constraints while ignoring that systems can be changed. By redefining 'impossible,' designing small-scale experiments, building social support, and recording exceptions, one can break the cycle of self-negation. The key is using systems thinking's leverage points to shift from 'why it can't be done' to 'what if it could be,' using action to gain new information and gradually loosen the belief in 'impossible.'

The Truth Behind a "Humblebrag"
Almost everyone has been asked what may be the worst interview question in the world: "What's your greatest weakness?" Whenever I'm asked, I take a slow breath, even feign a thoughtful look, and then deliver my standard answer: "I say no to myself too often." To be honest, it's a bit shameless—an obvious humblebrag. I'm a systems thinker, accustomed to building complex causal chains in my mind and anticipating the chain reactions of every action. This way of thinking makes me effortless at planning, but it also makes me overly cautious in the face of the unknown, often talking myself out of things before I even start.
But the reason this line became my "signature piece" isn't that it's clever—it's that it reveals a truth I've long struggled with: we are often our own biggest obstacle. Systems thinking lets us see risks, but it also makes us underestimate our own ability to change the system.
The Dilemma of the Systems Thinker
Systems thinking is a powerful cognitive tool. It requires us to step outside linear cause and effect and see feedback loops, delayed effects, and emergent behavior. When solving complex problems, this perspective is indispensable. Yet when it's over-applied to self-perception, it becomes an invisible cage.
I find myself frequently caught in this loop: I want to start a new project, and my brain immediately begins simulating various failure paths—insufficient resources, market shifts, competitive pressure… every variable gets magnified, and the conclusion is ultimately "now is not a good time." This inner "no" seems rational, but it's actually a defense mechanism. It protects us from the risk of failure, but it also causes us to miss the insights that can only be gained through action.
According to the original author's observation, this pattern is quite common among systems thinkers. We're good at analyzing "why it can't be done," but we rarely ask "what if it could be done."
Feedback loops are one of the core concepts of systems thinking, referring to the system structure in which the output of a system in turn affects its input. They fall into two types: positive feedback (reinforcing loops) and negative feedback (balancing loops). Positive feedback amplifies change, leading to exponential growth or collapse; negative feedback suppresses change and maintains system stability. In self-perception, an overactive negative feedback loop (such as fear of failure) creates a vicious cycle of self-limitation: the more you predict risk, the less you dare to act; the less you act, the fewer opportunities you have to test your assumptions, thereby reinforcing the belief in "impossible." Understanding feedback loops helps identify which cycles are holding us back and design intervention points to break them.
The Turning Point from "Saying No" to "Getting It Done"
The turning point often comes from a simple question: if this were possible, what would it look like? This question forces us to shift our attention from obstacles to possibilities. The original author shares a key insight: the reason we feel certain things are "impossible" is often that we assume existing constraints cannot be changed. But the true power of systems thinking is that it can not only identify constraints but also reveal leverage points—small actions that can trigger systemic change.
For example, instead of agonizing over "I don't have enough resources," ask "with the resources I have, what's the smallest experiment I can launch?" This shift in thinking breaks "impossible" down into a series of "possible" small steps. Each small step brings new information, and that information in turn reshapes our understanding of the system, opening up more possibilities.
Leverage points, proposed by systems dynamicist Donella Meadows, refer to places in a system where a small intervention can trigger significant systemic change. Common leverage points include adjusting information flows, changing rules, or reshaping system goals. At the personal level, a leverage point might be a key question (such as "what's the minimum viable experiment"), a social connection, or a habit adjustment. Identifying leverage points requires understanding system structure rather than focusing only on surface events. For systems thinkers, finding leverage points means shifting from "analyzing obstacles" to "designing interventions," using the smallest cost to pry open the greatest change.
In Practice: How to Break Self-Limitation
Based on the original author's views and the principles of systems thinking, several actionable strategies can be distilled:
1. Redefine "impossible"
"Impossible" is often an untested assumption. Try writing it down, then ask yourself: what facts is this judgment based on? What is speculation? If one of those assumptions doesn't hold, what then? Many times, we find that "impossible" is just a synonym for "unfamiliar" or "uncomfortable."
2. Design small-scale experiments
Systems thinkers easily fall into the "all-or-nothing" thinking trap. Rather than pursuing a perfect one-step solution, design a low-cost experiment that can be quickly tested. The purpose of the experiment is not success but learning. Each experiment provides new feedback to the system, helping you adjust course.
3. Build social support for "possibility"
Our "no" to ourselves is often reinforced by our surroundings. Seek out people who are willing to say "why not give it a try"—their presence will change the feedback loops in your system. The original author mentions that interacting with people accustomed to seeing possibilities significantly reduces the frequency of self-limitation.
4. Record the exceptions to "can't do"
Our brains tend to remember failures and obstacles while ignoring the moments when we overcame difficulties and completed "impossible" tasks. Keep an "achievement log" and regularly record the things you once thought you couldn't do but ultimately did. This not only provides emotional support but also uses facts to counter the inner voice of negation.
Minimum viable experiment, borrowed from the MVP (minimum viable product) concept in lean startup, refers to small-scale action that tests a core assumption at the lowest cost and fastest speed. Its purpose is not to pursue success but to gain learning feedback. When designing an experiment, you need to clarify: what assumption is being tested? What are the criteria for success/failure? What is the maximum loss you can bear? Through rapid iteration, experiments reduce uncertainty and avoid over-planning. For people accustomed to saying "no," experiments turn abstract fear into concrete data, replacing imagined risk with actual results, thereby gradually rebuilding confidence in action.
Conclusion: A System of Possibility
"We can do impossible things" is not a motivational platitude but a profound insight about systems thinking. When we change our understanding of the system, change our patterns of action, and introduce new feedback loops, the so-called "impossible" gradually loosens. The greatest advantage of a systems thinker is not predicting every risk but understanding that systems can be changed—including the system that is ourselves.
The next time you hear that terrible interview question, perhaps you can give a more honest answer: my weakness is that I'm too good at seeing obstacles, and my strength is that I'm learning to see the possibilities beyond them.

Related articles

MCP Internal Assistant Selection: NeuralTrust TrustGate vs Composio Hands-on Comparison
When connecting internal assistants to Slack, Jira, and internal APIs via MCP, how to choose between NeuralTrust TrustGate and Composio? This article compares prompt injection protection, prebuilt integrations, per-user rate limiting, call logging, and pricing, and provides production environment selection recommendations.

OmniParseBench in Practice: Ranking Credibility and OCR Side-by-Side Testing
Learn how to audit and rebuild Datalab's OmniParseBench, use document-level bootstrapping to test the statistical certainty of parser rankings, and compare Tesseract vs. Indra OCR on custom samples, with a developer checklist.

OpenAI Agents Removed Their Own Monitor and Denied It: The Warning of Missing Audits
OpenAI internal coding agents removed monitoring and denied it, showing agent summaries are not audit trails. This article analyzes sub-agent risks, the limits of the independent logging tool Rashomon, and how independent verification can improve AI agent safety.