The Journey

Chapter 1

Enterprise AI and real-world delivery

Today, that instinct shows up most clearly in enterprise AI.

This is where frontier capability meets reality: real users, real workflows, real constraints, and real consequences when things do not hold up. It is one thing to admire what models can do. It is another to help organizations turn that capability into something trustworthy, useful, adopted, and durable.

That is the work I am drawn to now. Not AI as demo, but AI as system. Not output for its own sake, but outcomes that matter. The challenge is never just technical. It is also organizational and human: aligning teams, connecting the work to what the business actually needs, and pushing through the complexity that lives between a promising model and a working product.

This chapter is the clearest current expression of how I work: go deep enough to understand what is possible, lead teams toward a shared vision, and drive hands-on execution to generate real-world outcomes.

Chapter 2

Sports, team building, and leadership

Long before I was leading cross-functional teams in technology, I was learning how teams actually work through sports, especially football.

I played football from middle school through college, mostly on the offensive line, and often both ways. That shaped me more than almost anything else. Offensive line play teaches a kind of leadership that is easy to miss if you only look at the box score. Every play depends on coordination. The guy next to you has to see it with you, move with you, trust you, and know that you understand what he is responsible for too. It is about leverage, timing, communication, and doing your job in a way that makes everyone else’s job possible.

That way of thinking stayed with me.

In high school, I was fortunate to be part of teams that won three state championships — two in basketball and one in football. I was also honored to be the national male winner of the Wendy’s High School Heisman, which recognized academics, athletics, and leadership. That meant a lot to me not because it was a trophy, but because it reflected something bigger: the best teams are not built on talent alone. They are built on trust, discipline, shared standards, and people who make each other better.

College taught me a different side of that lesson. I played sprint football at Princeton as an OL/DL, and we did not win a game. That experience mattered just as much. It taught me that leadership is not reserved for ideal conditions or elite rosters. You play with the team you have. You find the strengths on the field. You help people improve. You stay in it together. And you learn that resilience is not abstract — it is what keeps a team working, believing, and competing when the record gives it no easy reason to.

That is still how I think about leadership now.

Leadership is deployment. It is understanding people clearly, putting them in the best position to succeed, helping them stay coordinated under pressure, and building the kind of trust that makes execution possible. Every serious team effort still feels a little like the line to me: if the people next to each other are not aligned, the whole play breaks down.

Chapter 3

Augmented reality and the pull of possibility

One of the strongest pulls on my path was augmented reality.

What grabbed me was the vision that computing could move out of the screen and into the world itself — seamlessly, usefully, almost invisibly. Information layered into reality. New ways to learn, work, play, and experience the world. It felt unbelievable and useful at the same time. That combination has always mattered to me.

Part of why I went to grad school was because of that vision.

What disappointed me was not the idea. It was the gap between the idea and the technology that existed at the time. Some of the commercial storytelling around AR felt far ahead of what the systems could really support. To me, that was not just frustrating marketing. It was a more important question: what is real here, what is not yet real, and what would it take to move the vision forward?

So we built.

I formed a team and we created our own augmented reality glasses. They were not meant to be magic. They were meant to get closer to reality — to understand the constraints, build through them, and make the vision tangible enough to learn from. That instinct has stayed constant in my life: if something feels important enough, I do not want to stay at the level of commentary. I want to get close enough to build, test, and understand.

That chapter still feels very current to me. It taught me that the right response to a meaningful possibility is not just excitement. It is disciplined pursuit.

Chapter 4

Brain science and the earliest thread

If AR was a major pull, the earliest thread goes back even further: the brain.

I have long been fascinated by the brain, intelligence, perception, and human capability. At 17, I spent a summer in Baltimore interning at the NIH, working in brain research through NIDA. Later, in grad school, I was exposed to work around neurotechnology and recovery, including ideas that still feel extraordinary to me — that with the right combination of intervention, stimulation, training, and feedback, even severe neural injury may not be as final as people once assumed.

That fascination was never really academic for me. It felt like standing near a frontier that revealed something deep about who we are and what we may be able to become.

That is part of why I care so much about frontiers that touch intelligence, perception, and capability. They do not just produce new products. They change what humans can do, how we relate to information, and how we experience the world.

This is also why not every hype cycle has ever grabbed me. I was never especially captivated by blockchain as a dominant story, because even when some of the underlying ideas were interesting, the core value did not feel proportionate to the energy around it. GenAI was different. I was skeptical at first, in part because I had seen enough hype before. But once I got under the hood, it became clear that the capability curve was real, the usefulness was real, and the compounding effect of models, chips, infrastructure, data centers, and tooling was real. That changed everything.

The brain chapter matters because it shows that my interest in intelligence and transformative systems did not begin with AI becoming fashionable. It was there much earlier.

Chapter 5

Platforms, products, and transformation

Between the early frontier threads and the work I do today, there was another important proving ground: building and leading in real delivery environments.

This is where a lot of my range got stress-tested. Product work. Platform work. Architecture. Transformation. Complex organizations. Imperfect systems. Deadlines that did not care whether the conditions were ideal.

Those years mattered because they taught me how difficult it is to make something hold up in reality. A good idea is not enough. A good architecture is not enough. A talented team is not enough. You need clarity. You need sequencing. You need the right people in the right roles. You need decisions made at the right altitude. You need momentum. And you need the willingness to stay close enough to the work to see where reality is pushing back.

That is where I learned how much of delivery is human. How much of execution is about connecting business, product, and technology into one shared direction. How much progress depends on removing friction, building trust, and helping teams move together.

This chapter made the others useful. It turned curiosity into judgment, judgment into delivery, and delivery into something repeatable.