The work kept getting closer to the system.
A story about learning, products, teams, and the question AI makes impossible to avoid: what is the team for now?
Learning was never separate from the work.
I came to this from learning and development. That starting point still shapes how I think: a team is not only a group of people doing work. It is a system for building judgment.
Then the work moved closer to the product.
For the last decade, my work has lived where building products meets building the teams behind them. Messy ideas need more than a plan. They need systems, habits, and roles that make the next decision easier.
A good team is designed, not assembled.
That became the through-line: turn ambiguity into a way of working people can actually use. Not a glossy org chart. A living system of ownership, feedback, and learning.
Then AI changed the question.
AI did not just hand your team a faster tool. It changed what the team is for. When agents start handling more of the execution, human work moves toward judgment: deciding what matters, translating ambiguity, orchestrating the system, and knowing when to hold the line.
That is not an adoption problem. It is an org design problem.
Make the progression useful.
Today I work as a systems architect and Fractional CAIO for founder-led companies. The work is redesigning how work flows when humans start supervising agents, and rebuilding roles around ORBIT: a framework for AI-augmented teams.
When AI automates the bottom rung of the org chart, it also removes the rung people used to climb to earn judgment. Redesigning teams around AI and rebuilding how people grow inside them are the same problem.