Meet Anand Saranath
Technology Architect | Systems Thinker | Explorer of Systems & Stories
I’m a technologist by profession and an architect by instinct. Over the years, I’ve come to believe that good architecture is less about diagrams and tools, and more about connecting purpose, people, and design.
My work has taken me across system architecture, AI, platform engineering, and large-scale technology transformation. What I enjoy most, though, is making complex things easier to understand and helping teams think more clearly about the systems they are building.
Outside work, I write about the other systems that shape us — people, memories, leadership, learning, music, places, mistakes, and the small ideas that stay with us over time.
That is why this site moves comfortably between architecture and reflection. One article may be about agentic AI or system design; another may be about a person who changed my life, a piece of music that stayed with me, or something I noticed while simply looking at the world differently.
When I’m not thinking about systems, I’m usually listening to Ilaiyaraaja, writing, travelling, or trying to capture light through a camera lens.
How I Think About Architecture
I have never seen architecture as a collection of diagrams, frameworks, or technology choices. For me, it begins with understanding intent — what the business is trying to achieve, the constraints within which we are operating, and the patterns and principles that can help us make better decisions.
At the centre of that is architectural thinking: seeing the system as a whole, recognising patterns, understanding trade-offs, and designing for change rather than only for the problem in front of us.
Good architecture also depends on more than technology. People, process, and engineering practices all influence whether a design survives contact with reality. Governance, standards, non-functional requirements, and compliance matter too — not as controls added at the end, but as part of how resilient systems are built.
When these things come together well, architecture should ultimately create business agility, operational excellence, and trust. The real test is not whether the initial design looks elegant, but whether the system can continue to adapt as the organisation, technology, and problems around it change.
That is what architecture means to me: thinking in systems, designing with intent, and creating something that can evolve.
