Leading in the terbulent environment of an AI startup
I spent the last 12 months scaling technical teams, navigating the chaos of AI startup life. It’s been a year marked by breakthroughs, resilience, and some tough but rewarding lessons.
We tackled massive technical challenges and hit ambitious goals that moved the company forward in a big way:
Looking back, here are a few principles and lessons that defined our year—and our growth.
One of my key responsibilities is to align technology with business needs, even when those needs shift fast. This means resisting the urge to build “perfect” systems—instead, we build adaptable ones.
We adopted domain-driven design to map business problems to teams, giving them autonomy and driving productivity. We embraced hexagonal architecture to maximise reversable decisions. Every team is using the same core tools, similar project structure and the same design patterns. Making it easy for teams to help each other, re-use work and share knowledge.
Perfect is the enemy of good. In our world, it’s better to be pragmatic and aim for good enough and prioritise reducing the number of changes needed to react to new information quickly.
Consistent effort to stay in the top right quadrant
One of my guiding principles has always been prioritize strategic work over tactical firefighting. But in a startup, immediate issues can cloud your ability to think even a few weeks ahead. Our strategic goal was to grow ARR by scaling to meet our growing customer demand.
So we made the conscious (and at times painful) decision to reduce near-term sales activity so we could double down on foundational technical improvements. That short-term hit paid off—we're now operating at a scale we need to support 10x more customers.
We achieved this by enacting the "kaizen initative", inspired by the Toyota term for "continuous improvement". This involved proactively identifying our largest bottlenecks and making plans to address them, then looking for the next bottleneck.
We also simplified ruthlessly. Startups don’t starve—they drown. By trimming back non-essential projects, clarifying priorities, and choosing simple, durable plans, we preserved our most valuable resource: Time. Time to achieve our strategic goals.
I believe teams of people with good attitude beat teams with more experience and a bad attitude every time. Passionate, humble engineers who communicate well can learn any skill and teams of them become greater than the sum of their parts. That belief guided our hiring and mentoring practices all year.
In our 1:1s, we put mentorship before status updates. We grew leaders from within, encouraged radical candor, and practiced healthy conflict resolution, even around minor topics so we’d be ready when the stakes were high.
We embraced a “leader-leader” model: everyone gets ownership, everyone is trusted to lead and held accountable. The result? Autonomous teams that move faster and make better decisions. The accountability ripple effect is real — and powerful.
In a world obsessed with speed and AI-powered pivots, it’s tempting to chase the next shiny insight. But we learned that sometimes, sticking with a solid-but-not-perfect plan is smarter than constantly shifting gears.
One failed pivot taught us this the hard way. We moved too fast, ended up with a half-baked solution, and had to roll it all back. Now, we absorb customer learnings, update plans thoughtfully, and protect team momentum while staying agile.
It’s about discipline, not rigidity. We adapt and iterate, but we also need to commit to a plan long enough to see the benefits. This balance has been key to our success.
I’ve always been outcome-focused—but this year reminded me to lead with empathy, especially in moments of tension. The strongest teams challenge each other with respect and with care.
I feel incredibly fortunate to be at Ocula, working with such a talented, driven team. I’ve grown more this year than any before—technically, strategically, and personally.
Do you work in a startup or with AI, what was your biggest learning?