03/11/26November 3, 2026·Personal·7 min read
Anyone can build systems
There was a moment when I tried to explain to a colleague how I worked. My processes, my timings, how I anticipated an account at risk before the client ever said a word. I couldn’t. Until that point, everything lived in my head: scattered, unorganized, impossible to transfer. That was the moment I understood that holding onto that accumulated knowledge was not an advantage for me. It was a bottleneck for the team.
This happened at Deale, my most recent professional role. I was the first person on the Account Management team and was responsible for contacting and managing all of the company’s clients during the first six months. As a company only three years old and growing fast, I saw it as a challenge that would help me expand what I believe one person can do alone. In the early calls, I had little idea how to introduce myself, how to define next steps, or even basic concepts of M&A (mergers and acquisitions).
I decided the best strategy given the circumstances was to follow my own instincts. In a commercial and client-facing role serving a specialized type of customer (owners of small and medium-sized businesses across Spain, as well as private investors, both institutional and individual), the best thing I could do was listen before speaking. I focused on understanding what worried each of these clients, without judgment or criticism. My conviction was clear: after listening actively, I needed to commit to offering solutions and making promises I could genuinely keep. That, and only that, is how you build long-term trust.
As time went on, I became more aware that the same pattern kept repeating: clients needed information, follow-through, and a plan that delivered without fail. Their goal was always to reduce the uncertainty of an outcome that, by its nature, took time to arrive. As new team members joined, I took charge of designing onboarding programs for them, systems through which they could work and achieve results similar to mine, working principles and collaboration frameworks, mentorship and additional resources. Within the first six months, the results were clear: the client churn rate dropped from 28% to 5%.
What I built from that point on was not a trick or a special talent. It was the result of three habits. And today I want to share them with you.
Habit 1: Be curious and act like a sponge
I wrote about this on my blog a few weeks ago. The habit of reading, explaining, applying, and repeating allowed me to think in concepts and ideas from fields that seem completely unrelated. For example, the former head of Intelligence of Peru once helped me approach my work creatively when I needed to improve my performance at Deale, while also trying to follow a Political Economy course in France. I also remember applying mathematical principles I learned in a Multivariate Data Analysis class at UPF to build recommendation engines at Amaru Invest.
Exploring different fields of knowledge in parallel, simply by trying to understand how they work, will sooner or later help you find solutions others don’t see. That is the advantage of the polymath.
Habit 2: Be patient and persistent without seeking recognition
Going back to that moment: when I tried to explain my system and couldn’t, the easiest reaction would have been to document just enough to get by and remain the team’s go-to reference. There is a real temptation in that. Having others depend on you feels like a guarantee of security. But it is an illusion: a system that only lives in your head doesn’t scale, and the moment you’re not there, the team is exposed. I chose to prioritize the long-term good of the company over that apparent security.
What this habit requires is accepting that building something replicable takes time, and that during that time no one is going to applaud you for it. The process is not glamorous: you try, you fail, you extract feedback, you collect it, you analyze it, and you try again. You keep the cycle going long enough until the system works the way you would individually, but without you being present. That is transmuting all the accumulated experience and knowledge in your head into something external to you.
One key thing I learned in that process: you need to separate your creation from yourself. A critique of the system is not a critique of you. The moment you achieve that separation, criticism and judgment become nothing more than signals for improvement.
Habit 3: Be humble, share what you build, and make yourself unnecessary
What I’m about to say is paradoxical: yes, to create something new you need to believe you are capable of producing it, designing it, iterating it. The ego may be involved. However, if you build from the ego you will not be adding value to your environment; you will simply be reinforcing the image of superiority you want to project. Remembering that you are the vehicle through which ideas flow, and that those ideas serve not the individual but the common good, is the dominant strategy.
After three years at Deale, there were six people on the team who achieved results even better than mine: average client churn rate stable at 10%, individual retention rate of 90% per portfolio, customer lifetime value in line with the company’s business plan targets. Above all, what marked me most was not the numbers. It was hearing colleagues use the same terms I had used in my early days, following the same processes to anticipate drops, save at-risk accounts, and make upsells. Seeing that they could do it on their own, and do it better, was the moment I felt most fulfilled. The goal from the beginning had always been to make myself unnecessary, even if the ego resists it.
The analogy that helps me think about this is scientific research and peer review. Someone publishes a paper, others review it, improve it with new findings and methodologies, and knowledge advances faster than any individual could alone. The system outlasts its creator.
How to start
These three habits feed each other when necessity comes knocking. In my case, it was arriving at an uncertain environment with no precedent where everything had to be built from zero. For you it might be a project that helps you move up, something of your own that you believe can help your community, or simply automating repetitive tasks at work so you can focus on what matters most.
And when the system works without you, don’t see it as a loss. The process itself is the end. A system that works perfectly opens the door for you to build the next one. We all start with something that only exists in our heads. The difference is deciding to bring it into the world.
What process of yours exists only in your head and you haven’t shown to the world yet?
Read next
- BlogWhat eight years abroad taught meThree principles that helped me move from an unfamiliar university system to the Toulouse School of Economics, and later into the startup world.Read→
- JournalClosing the execution gapProcrastinating getting out of bed is a way of fleeing from what I know is best for me, from the commitments I made rationally the night before.Read→
