Systems Thinking Is Learned Before It Is Taught
My understanding of systems began long before software, shaped by a factory floor, imaginative technology on television, and children’s newspapers.
As a child, I was exposed to a small table salt factory run by a close family member. It was filled with motors, mechanical linkages, electrical components and wiring, and control mechanisms. At the time, it felt ordinary. In hindsight, it was my first engineering classroom.
Being surrounded by machines and electrical systems removed fear early. I was encouraged to observe, touch, and experiment. I watched raw salt move through multiple stages of processing and saw how machines interacted. Complexity was not intimidating. It was something to understand.
That comfort with systems did not come from textbooks. It came from proximity, even before I could read or write.
At the same time, popular science fiction reinforced that curiosity. The television series Knight Rider captured my imagination in a powerful way. As a child, seeing a car that could drive itself, talk to its driver, and respond through a wristwatch felt magical. The moving red scanner light, the sound effects, and the idea of intelligence embedded in a machine planted an early seed about what science and technology might one day achieve.
The original series followed the adventures of Michael Knight and his technologically advanced, artificially intelligent automobile, KITT. What made that inspiration enduring was not only the fiction itself, but how approachable it felt. Advanced technology was presented not as something distant or intimidating, but as something that could be understood, interacted with, and trusted.
That sense of accessibility extended beyond television. Children’s newspaper Wijeya published simple circuit diagrams inspired by science fiction, including versions of the iconic moving scanner light. Building those basic circuits became my first hands-on experience with electronics. Around the same time, the same publications introduced computers through serialized articles, translating abstract ideas into concepts that felt concrete and learnable.
Get Asanka Priyanjith’s stories in your inbox
Join Medium for free to get updates from this writer.
Looking back, three forces clearly converged:
- Practical exposure to real-world systems
- Imaginative inspiration from science fiction
- Accessible, hands-on learning
Together, they removed fear and replaced it with curiosity.
Equally important was the environment created at home. I was given freedom to explore, paired with clear boundaries. That balance mattered. Freedom built confidence. Boundaries built discipline. Failure was allowed, but responsibility was expected. Hard, honest work was consistently promoted and encouraged.
Today, when I lead large, multi-million-dollar software programs, I see a direct line back to those early experiences: comfort with complexity, confidence in uncertainty, and the ability to reason about systems, make decisions with incomplete information, and remain composed under pressure.
Technology leadership is not shaped only by degrees, certifications, or frameworks. Often, it is shaped much earlier by environments that encourage curiosity, reduce fear, and make systems feel approachable.
Those lessons stay with you for life.
