Becoming chief technology officer (CTO) at Zyte in 2025 prompted me to look back on the lessons in my two-decade career in various CTO and CIO roles.
One reflection stands out as a temptation familiar to almost every technology leader.
Early in my career, I was often the troubleshooting engine of the organization: close to the code, managing every detail, fixing problems personally, micromanaging the roadmap. For a time, this approach even worked—at least on the surface. But it was never truly sustainable, and it certainly didn’t deliver lasting value.
Now, with years in the CTO seat across startups and enterprises, I can say with certainty: the real job isn’t building the product yourself, but building the system that builds the product.
What is a system, really?
A system isn’t a JIRA board or a CI/CD pipeline. It isn’t a set of velocity metrics or a perfectly color-coded roadmap. Those things are tools, not systems.
A true system is a living environment—a set of shared language, decision-making principles, and cultural norms. It’s a framework that supports thousands of micro-decisions every day, without losing sight of what matters: customer impact, trust, and ownership.
If you only build for what’s needed right now, you’ll always be chasing your tail. The better path is to design for resilience: engineer feedback loops, build autonomy structures that survive doubling or tripling in size, and invest in observable infrastructure that makes issues obvious before they become catastrophic.
Today, systems thinking means designing not just for humans, but for machines, like bots and AI agents. If you don’t build for that reality, your team and your business will struggle. Managing humans is hard. Managing a blend of humans and AI agents is harder still. Without a strong system in place, it’s simply unmanageable.
Culture over code
The CTO’s real job is to replace themselves with an environment—a culture, a platform, an architecture—that allows talented people to deliver excellence, reliably and repeatedly, even under intense pressure.
I’ve seen first-hand how empowering teams to own their work and building structures for autonomy leads to better outcomes, both for customers and for the business.
For example, at Zyte, I’ve watched engineers transition into product owner roles and immediately build greater trust with customers—not by being the loudest in the room, but by truly understanding the product and asking the right questions. Trust skyrockets, outcomes improve, and the system gets stronger for everyone.
No sergeant makes a good general—unless they embrace that their job has changed. As leaders, we must move from being the hero to being the architect of environments where others can excel.
The work is never done
System building isn’t a project with a start and end date. It is a continuous evolution.
That’s what gets me up in the morning: fighting for every inch of improvement, side by side with great people, building systems that last and make excellence repeatable. The privilege isn’t just in the delivery, but in enabling others to deliver—over and over, no matter the pressure or the pace of change.
If you’re in technology leadership, my advice is simple: stop trying to be the genius who delivers the product. Instead, build the system that allows greatness to emerge—again and again, no matter who is in the room.
That’s the legacy worth fighting for.
