Notes and reflections from building, learning, and staying curious.

Throughout my career, I have often been drawn to moments where something needed to be built from scratch. Not just managed once it existed, but shaped early, when there was still ambiguity and when the right systems, structure, and direction had to be created.

At TikTok, I had the chance to help build the operating foundations at a time when the business was still scaling quickly and many things were still taking shape. What always interested me most was not process for its own sake. It was how to design an operating model that could support growth, bring clarity to complexity, and help teams move with more focus and confidence. For me, that kind of work has always been strategic. It is about seeing what needs to exist before it fully exists, then helping build it in a way that can scale.

I saw something similar earlier in my career at Ogilvy, when I helped lead and launch the first major tech project at an advertising agency that had never launched something of that scale before. The project was TimeWarnerCable.com, which was later taken over by Charter Communications. It was a high-scale and high-visibility program, and it required real depth in technology, product thinking, and execution. That experience stayed with me because it showed me that complex systems can be built successfully even in places not known for engineering, if the right leadership, structure, and learning mindset are in place.

That same instinct came back to me with AI. I realized that if I truly wanted to understand where this world is going, it was not enough to only prompt models or experiment casually. I wanted to build a real product from scratch. Something simple, public-facing, and useful. That is what led me to build InsightLens.

What surprised me most was how energizing the process felt. In building it, old technical muscles started waking up again. Earlier in my career, I had worked much closer to technology and code. Over time, as my roles became more centered on business leadership, scale, and strategy, that layer became quieter. It never disappeared, but it definitely went dormant. This project brought it back to life.

I had to think through the architecture from the ground up. How the front end would work. How the app would be deployed. How the code would be managed in GitHub. How Vercel, Supabase, and the OpenAI platform would connect to each other. How information would move through the system, from user input to model response to app output. How to make the product simple on the surface while keeping the structure underneath clean and reliable. It was not about building something huge. It was about building something real and learning by doing.

That process reminded me of something important. A lot of growth comes from stepping back into spaces where you are no longer fully fluent, but willing to learn again. It made me feel lively, stretched, and honestly more playful than I have felt in a while. There was something deeply satisfying about moving from idea to working product, and seeing that what looked intimidating at first became manageable once I committed to it step by step.

This project is small in the grand scheme of things, but it meant a lot to me. It reminded me that I do not have to choose between strategic leadership and building. The two can feed each other. In many ways, the same mindset that helps build organizations and operating systems can also help build products.

More than anything, this feels like a beginning. Building this first app has inspired me to do much more in this space. Not because I want to suddenly become something I am not, but because I can feel how important this shift is, and I want to engage with it in a real way. I want to keep learning, keep building, and keep exploring what becomes possible when strategy, technology, and curiosity come together.

Good leadership starts with curiosity. Asking more questions and talking less creates space to understand what is really happening, where the friction is, and what matters most. But curiosity alone is not enough. Leadership also requires decisiveness. At some point, someone has to create clarity, make the call, and help people move. The balance matters. Stay open long enough to understand the problem well, then be clear enough to move the team forward.

Another important part of leadership is not becoming too attached to your own ideas. With experience, it becomes easy to assume you already know the answer. But strong leadership is not about ego or proving a point. It is about getting to the best answer, wherever it comes from. That requires real humility and a genuine openness to other people’s thinking. It also works best in an environment where people feel respected, heard, and safe enough to speak honestly. At the end of the day, work is still about people. The strongest teams are usually not the loudest or the most argumentative. They are the ones where good ideas can surface without unnecessary tension, and where people can challenge each other without losing kindness.

That is also why diverse thinking matters so much. Strong leadership is not just about having strong ideas personally. It is also about knowing who is in the room, understanding what different people bring, and creating the conditions for those strengths to come together in a useful way. Some people bring structure. Some bring creativity. Some see risk early. Some see possibilities others miss. A big part of leadership is knowing how to bring those different strengths together and channel them toward something meaningful.

This is one reason building small things still matters. Building has a way of keeping all of this honest. It reminds you very quickly that ideas are easy and execution is humbling. It forces clarity. It exposes tradeoffs. It makes feedback real. It shows, in a very practical way, that the first idea is not always the best one and that progress often comes through iteration, openness, and learning.

That closeness to the work is healthy for leaders. It sharpens judgment. It keeps humility alive. It makes strategy more practical. And it helps leadership stay grounded instead of becoming too abstract or distant.

Leadership is not only about setting direction from above. It is also about staying close enough to the work to understand what is changing, what is hard, and what is possible. Building small things is one way to do that. It keeps leadership real.