Dallas skyline illustration

CYC26 / Leadership

If You’re Not Shipping, You’re Not a Leader

Leadership is not a calendar of 1:1s. It is whether everything still moves when you leave the room. I learned the hard way, and across four different job families, that kept trying to pull me out of shipping: individual contributor, principal architect, Chief Revenue Officer for an enterprise consulting firm inside companies that move billions of dollars, and now co-founder of a startup whose product sits in other people’s revenue path. Every title got bigger, but the temptation stayed the same - stop shipping, start narrating. This talk is about refusing that trade. How you keep leading from the front instead of the balcony. How you build with the team so you do not become their review queue. How do you instrument work so you can see where it dies, especially when it is stuck on you. How running more than one computer, and putting AI into the path of real work, changes who can cause measurable impact rather than who can write a prettier status update.  Finally, how you scale beyond yourself: taste encoded as defaults, handoffs that survive your calendar, a company that still ships when you are on a plane. If your last user-visible change is older than your last status meeting, this one is for you.

Session abstract

What you’ll learn

Leadership is not a calendar of 1:1s. It is whether everything still moves when you leave the room. I learned the hard way, and across four different job families, that kept trying to pull me out of shipping: individual contributor, principal architect, Chief Revenue Officer for an enterprise consulting firm inside companies that move billions of dollars, and now co-founder of a startup whose product sits in other people’s revenue path. Every title got bigger, but the temptation stayed the same - stop shipping, start narrating. This talk is about refusing that trade. How you keep leading from the front instead of the balcony. How you build with the team so you do not become their review queue. How do you instrument work so you can see where it dies, especially when it is stuck on you. How running more than one computer, and putting AI into the path of real work, changes who can cause measurable impact rather than who can write a prettier status update.  Finally, how you scale beyond yourself: taste encoded as defaults, handoffs that survive your calendar, a company that still ships when you are on a plane. If your last user-visible change is older than your last status meeting, this one is for you.