01
Marzo 2025 — Actualidad
Actual Corporate group
Digital transformation.
I don't tell my career through the companies I worked for, but through the industries I moved across. Each one imposes its own rules and leaves behind a different way of deciding: regulatory risk on one side, volume and operations on another, and full responsibility when the business is your own. Twenty-eight years going through all of that is, in the end, what defines my judgment most.
Digital transformation.
Alongside my professional career I am an entrepreneur and business owner. Running your own business changes your judgment: you stop arguing over someone else's budget and start signing your own, and you learn that every technical decision ends up being a cash decision.
Almost a decade in the financial sector, across architecture, systems and technology management. An environment where availability, risk and regulatory supervision shape every decision, and where technology is always discussed alongside the business and compliance. It was the stage that shaped my judgment the most: digital transformation there is not measured in announcements, it is measured in services that keep responding.
Eleven years in a volume industry, with high-value inventory and a sales network that depends on having up-to-date information. The work revolved around modernizing platforms and connecting systems that were not talking to each other.
Three years on the other side of the counter, implementing enterprise solutions in companies from very different sectors. That is where you train the ability to step into someone else's business, understand it within weeks and leave something running.
The beginning of my career: custom software development for internal processes and document management, in an environment where confidentiality was not negotiable. That is where the conviction comes from that a system is worth the process it puts in order.
A long career in a single sector gives you depth. A long career across five gives you something else: the judgment to know which of all those patterns applies here.
The same problem turns up with a different vocabulary in every industry. Having seen it five times cuts months off the diagnosis.
Explaining the architecture to the leadership team and the business goal to the technical team. That is where a project is won or lost.
The discipline banking demands —thinking first about what happens when it fails— applied in industries where nobody asks for it.
Every architecture decision is a budget decision. Discussing them separately is how organizations end up with platforms nobody can sustain.
Architecture and project offices, service processes, teams that have been trained. What is built well keeps working once you're gone.
Low-code, RPA and now artificial intelligence: always the same question —which process it improves, who is accountable for it and what it costs to keep running.
What measures a career is not the projects delivered but the capabilities left in place once you are gone: offices, processes, teams and people. None of this was a solo effort.
Building the architecture function where none existed: reference framework, standards, a review board and decision criteria. Architecture stopped being an opinion and became a process with rules.
Setting up the PMO and standardizing the portfolio: a single methodology, change governance, risk control and a dashboard that management actually uses to set priorities.
Forming teams of architects where there had only been developers solving things case by case. Defined roles, shared criteria and decisions that outlive the project that gave rise to them.
People I trained and supported along the way now hold management, architecture and technical leadership positions in different organizations. Of everything that remains, this is what represents me best.
Rolling out the service management processes — incidents, changes, problems and service levels — with metrics that are genuinely reviewed and not only at audit time.
Business process improvement programs in short cycles: measure, adjust, measure again. Sustained change instead of large projects that arrive late and no longer apply.
Robotic automation projects on critical, high-volume processes: lower operating costs, less human error and team capacity freed up for the work that does require judgment.
AI projects taken to production, not proof-of-concept pilots: models and agents embedded in business processes, with an owner, a metric, traceability and a clear way to switch them off.
Core banking migrations, omnichannel digital channels and legacy systems modernization, with regulatory compliance treated as a permanent process rather than a one-off project.
If you're going through something similar in your industry, open the chat and tell me about it. Comparing notes is usually worth more than any presentation.
An open conversation to share knowledge. Messages reach my console and I reply from there.
Pick the day and time that work for you. Thirty minutes, no sales pitch.
For a video call, just ask for one here and I'll send you the session link.