The information was there.The shared picture was not.

Before I had a name for systems thinking, I was already asking why things worked the way they did. Sometimes because something did not add up. Sometimes because a familiar process looked different from another angle. And sometimes because two things that seemed unrelated turned out to be connected.

My path moved through different environments, rarely in a straight line. Education, operations, business, technology, and organizational work each gave me a different language, different constraints, and a different way of seeing problems. Some decisions worked. Some did not. Looking back, those turns mattered less for where they took me than for what they allowed me to see.

There was a period when work became the way forward rather than education. Years later, I returned to education through a different route. Other plans changed along the way. I do not look back at those years simply as setbacks to overcome. They felt more like a process of being tempered by different realities, each bringing its own pressures, limits, people, and ways of thinking.

Perhaps the most enjoyable part was discovering that something learned in one place could suddenly explain something happening somewhere else. A process in operations could illuminate a business problem. A technical constraint could reveal a human one. A conversation about people could change the way I looked at data. The pieces kept meeting in unexpected places.

Over time, those connections became difficult to ignore. The questions followed me from operations into business systems and organizational work, and eventually into what I chose to build. I was not looking for a company idea. I was trying to understand what I was seeing. Optylion grew from that process, and from the belief that better understanding can begin when we see how things connect.