A chronology — from a first line of code to the framework and the tool it became. Engineer → Leader → Author → Founder.
01 · The Engineer
First line of code, 1990.
I wrote my first line of code back in 1990 (yeah, I'm that old, haha). Back then, programming was raw, simple, and magical. A few lines of code could transform an idea into something functional — something real. I was hooked.
Over the years, I moved from being a technologist honing the craft of coding to leading engineering teams at scale. When Agile entered the scene it was revolutionary — but as products grew complex and platforms scaled globally, engineers wanted more than just to churn out features.
02 · The Leader
Engineers wanted purpose, not tasks.
As I took on more leadership roles, I saw that my engineers no longer wanted to feel like cogs in a machine. They wanted to understand how their work impacted the business, the customer, and the bottom line — asking “How does this feature drive revenue?” and “Why are we doing this at all?” And they weren't wrong.
At the same time, the tools we relied on to implement Agile — like Jira and others — became little more than glorified project management systems. Great for tracking tasks, but they failed to connect planning, execution, and outcomes.
People wanted purpose, not just tasks.
03 · The Author
So I created S+3 Agile.
As I built larger teams, I realized it was time for a new approach — to not lose purpose while making teams more productive. I created S+3 Agile to bridge that gap: a framework that scales with complexity and aligns engineering work with business strategy.
S+3 stands for Sprints plus Three — visibility into the next three sprints, with strategic Horizontal Planning and precise Vertical Execution. It's built to solve the real challenges of today: scaling teams, managing ambiguity, fostering collaboration, and delivering value — not just tasks.
04 · The Founder
Then I built Kaizou.
I spent the better part of three decades watching engineers build extraordinary things inside organizations that were quietly breaking them. I've been the engineer staying late to fix the thing no one planned for, and the leader who asked too much and explained too little. That's the part most founder stories skip — the years of getting it wrong before you get it right.
Kaizou is what I built once I finally understood the pattern. The name comes from Kaizen — the Japanese practice of small, daily, deliberate refinement. It's the tool I wish someone had handed me twenty years ago, built by an engineer who became a leader who became a founder.
You cannot manufacture customer love on top of a tired engineering team.
#HappyEngineersHappyCustomers