> ## Content Index > Fetch the complete content index at: https://jonathancanales.com/llms.txt > Use this file to discover other available public pages before exploring further. # Why every team needs a systems thinker (and why you should be one) - URL: https://jonathancanales.com/en/why-every-team-needs-a-systems-thinker/ - Published: 2026-10-02T13:15:59.000Z - Updated: 2026-10-19T01:02:42.000Z - Description: Some people fix the problem in front of them. Others ask why the problem keeps coming back. The second group is easier to overlook, because when they do their job well, nothing dramatic happens. The fire never starts. - Author: Jonathan Canales - Tags: Leadership and teams, #en Why every team needs a systems thinker (and why you should be one) 0:00 /434 1× [![Listen on Spotify](https://jonathancanales.com/content/images/2026/10/image-ebade917.jpg)](https://open.spotify.com/show/1RbZ5C2DI8VFR4RA6paicv?ref=jonathancanales.com) [Read in Spanish →](https://jonathancanales.com/por-que-todo-equipo-necesita-pensar-en-sistemas/) Some people fix the problem in front of them. Others ask why the problem keeps coming back. The second group is easier to overlook, because when they do their job well, nothing dramatic happens. The fire never starts. These people are systems thinkers. You do not need a philosophy degree to be one, and you do not need a fancy title to need one on your team. 💡 Key idea: A systems thinker does not just fix the problem in front of them. They ask why it keeps coming back, and they change the cause. ## What a systems thinker actually does A business is a set of parts that depend on each other: people, processes, tools, customers, money, deadlines. A systems thinker looks at how those parts affect each other, not only at each part alone. Here is a simple picture. Imagine sales promises faster delivery to close more deals. Operations gets overloaded and starts missing dates. Customers complain, support gets swamped, and the team has less time to improve anything. Sales, meanwhile, sees a slow delivery team and promises even more urgency next quarter. Every department is doing its job. The company is still going in circles. Someone who looks at one department sees a delivery problem. A systems thinker sees a loop. Seeing the whole loop is also a strategic call; I separate the two levels here: [strategic or tactical: the difference that changes how you work](https://jonathancanales.com/en/strategic-or-tactical-the-difference-that-changes-how-you-work-and-how-youre-seen/). ![Whiteboard-style doodle: a loop of four boxes (Sales promises, Ops overloaded, Late deliveries, More urgency) and a person asking 'And then what?'](https://jonathancanales.com/content/images/2026/10/2-doodle-systems-loop-g.png) ## Why it matters more now Companies add tools, automations, AI assistants and new channels faster than they redraw how work flows between them. Each addition fixes one spot and quietly changes five others. Without someone who tracks the connections, you collect fixes that fight each other. AI makes this sharper. Automating one step in a messy process often gives you a faster mess. Before you automate anything, someone has to ask where the work comes from, where it goes next and who depends on it. That is systems thinking in plain clothes. ## Five habits you can spot 1. **They ask "and then what?"** If we do this, what happens next? And after that? Many bad decisions look fine at step one and painful at step three. 2. **They look for the cause, not the person.** When something fails twice, they check the process before they check who was on shift. 3. **They draw things.** A napkin with boxes and arrows beats a 40-minute argument. Seeing the flow makes the gap obvious. 4. **They notice delays.** Some problems show up weeks after the choice that caused them. People who track that gap stop blaming the wrong thing. 5. **They fix a small piece and watch.** They change one thing, observe what moves, and adjust. They do not announce a grand reorganization. ## Why you want people like this on your team - **Fewer repeat problems.** They fix the cause, so your team stops spending Mondays on last week's fire. - **Better handoffs.** Many errors live between people or departments, not inside them. Systems thinkers spend their time exactly there. - **Safer changes.** Before a new tool or policy goes in, they ask who else it touches. That saves you from the "we fixed A and broke B" surprise. - **Clearer conversations.** They can explain how the pieces connect in simple words, which helps a team agree on what the actual problem is. - **Better use of AI.** They pick the right process to improve first, instead of automating whatever is loudest. ## They do not replace specialists A team full of systems thinkers and nobody who knows the details would be a team that draws beautiful maps and ships nothing. You still need the accountant who knows the tax rules, the developer who knows the code and the operations lead who knows the warehouse. The systems thinker connects them. They translate between the specialists, point out where one person's fix lands on another person's desk and keep the whole picture visible when everyone else is focused on their piece. Think of them as the person who knows how the pieces fit, not the person who knows more than everyone. That is also why they work well at any level. An assistant who notices that two reports contain the same data, entered twice by two people, is thinking in systems. So is a CEO who asks why three departments each keep their own customer list. ## What it looks like with AI projects In practice, AI pilots often stumble for reasons that have little to do with the model. The data lives in three places. The output goes to someone who was never asked. Nobody owns the result after the demo. A systems thinker asks these questions before the pilot starts: where does the input come from, who uses the output, what happens when it is wrong and who is responsible next month. Those four questions cost nothing and head off a lot of the disappointment. That is exactly the broken-handoff problem; I wrote about it here: [why a new AI tool won't fix a broken handoff](https://jonathancanales.com/en/why-wont-a-new-ai-tool-fix-a-broken-handoff/). ## How to find one (or grow one) You will not often find them by job title. Try these questions in interviews or in one-on-one conversations: - "Tell me about a problem that kept coming back. What did you change so it stopped?" - "When you improved one thing, what else moved?" - "If we double our customers next year, what breaks first?" Listen for answers that mention other teams, delays and trade-offs. Be careful with answers that only blame a person or a tool. You can also grow this skill in people you already have. Ask "and then what?" in your meetings. Ask someone to draw the process before proposing a change. Reward the person who prevented the problem, not only the one who rescued everyone from it. ## And if you want to be one Start small. Pick one recurring annoyance in your business. Write down the steps that lead to it, who touches each step and where waiting happens. Then ask where the loop could be broken with the smallest change. That exercise alone usually shows something nobody had said out loud. ⚠️ A warning: Systems thinking can turn into analysis paralysis. Not everything needs a map. If the printer is jammed, fix the printer. Use the habit for problems that repeat, spread across teams or change when you touch them. ✅ One thing to try this week: Choose a problem that has come up more than twice. Gather the people involved for 20 minutes and draw the steps on a whiteboard. Ask "and then what?" at each arrow. Write down the one change that looks smallest and most useful. You may find the person who already thinks this way. They are probably the one holding the marker.