RETHINKING TECHNOLOGY LEADERSHIP
Turning Software Delivery Into a Strategic Advantage
If there’s a theme in my career, it’s this: the hardest thing to build isn’t software. It’s a system and culture that can survive hypergrowth, acquisitions, and constant change. That’s the work I love.
I modernize the delivery system, integrating where needed, improving flow end-to-end, and change how leaders lead, fund, and measure technology.
My purpose is to help leaders rethink engineering effectiveness and impact.
My mission is to make software delivery a strategic business advantage.
CONTEXT
Why this work exists
I’ve lived both eras: big-project, control-heavy delivery and today’s modern product delivery. The failure mode I see most often is adopting practices without changing the operating model, the measurement system, or leadership behaviors.
Software is knowledge work. Outcomes and timelines involve uncertainty. High-performing organizations don’t “predict harder”, they design for adaptability with smaller decisions, fast feedback, and disciplined flow.
VALUE
What changes when this works
What leaders get
Technology investment tied to measurable customer and business outcomes
Faster, safer delivery with less rework and fewer surprises
Teams with clarity of purpose, higher engagement, and stronger accountability
More predictable delivery without relying on heroics or burnout
How I help
Align
Connect strategy to outcomes/OKRs and define what “success” means before building
Flow
Reduce WIP, shorten feedback loops, manage dependencies, and remove bottlenecks across the system
Operate
Strengthen ownership, quality discipline, and decision rules so speed doesn’t create debt
BELIEF
What I believe about strategy
Technical strategy is customer-focused and business-led. The business sets direction; customers, market, growth, risk. Technology turns that into options, tradeoffs, and a competitive execution system that can deliver.
LEADERSHIP
How I show up as a leader
I start by listening; to the business, the customer, and the people doing the work.
I treat technology as a core business capability, not a back-office cost.
I take calculated risks when the feedback loops are tight.
I build strong teams with clear ownership and I lead as a teammate who listens, asks, and removes friction.
I create space for experimentation and innovation with guardrails: small bets, fast learning, and measurable outcomes.
I drive clarity of purpose: outcomes, priorities, and repeatable decision rules.
PRINCIPLES
Core principles
These govern how I design teams, measure progress, and make tradeoff decisions.
Outcomes over Outputs
I don’t reward activity; I reward measurable customer and business impact.
Flow over Utilization
I optimize lead time, WIP, bottlenecks, and dependencies; busy isn’t the goal.
Visibility over Guesswork
If we can’t see the work, we can’t manage it.
Accountability
“You build it, you own it.” Teams own what they ship; quality, security, operability, supportability.
Quality is a delivery strategy
Speed without quality is debt; readiness is part of throughput.
Systems thinking over hero culture
I fix the system. I don’t rely on heroics or burnout.
“Fast flow happens when friction fades”
-Phil Clark
PERSPECTIVE
Art of the possible
This is hard at scale, but it’s absolutely attainable. If it doesn’t sound inspiring yet, you may not have experienced an organization that built these capabilities end-to-end. Once you do, it changes what teams believe is possible.
“I view the product strategy less as any one specific thing, and more as how do we iterate and learn as quickly as possible… If we can learn faster than every other company, we’re going to win.” In today’s competitive landscape, teams that ship the fastest win.
– Mark Zuckerberg
Video excerpt from Zuckerberg’s interview on the “Acquired” podcast, recorded live at the Chase Center on September 10, 2024.