Customer Retention – From Lagging Indicators to Intelligent Systems
May 22, 2026
— Services
The instinct under pressure is to hire your way out. The teams that actually scale are built, not bought.
Sustained success isn’t about finding unicorns. It’s about operationalizing a strategy rooted in team dynamics — the right structure, the right accountability, and the conditions that let good people do their best work. That’s a design problem, and it’s one you can solve deliberately.
— The Principle
A high-performing team isn’t a collection of strong individuals. It’s a system — clear ownership, shared standards, and the kind of trust that lets people move fast without stepping on each other. Most teams underperform not because the talent is wrong, but because the structure around them is.
You don’t fix a struggling team by adding more people to it. You fix it by fixing what the people are working inside of.
Hiring follows the operating model, not the other way around. The roles you open, the seniority mix, the build-vs-partner calls — all driven by what the business actually needs next.
Reporting lines, decision rights, and ownership defined first. Adding people to an unclear structure multiplies the confusion; it doesn’t dilute it.
Distributed and global teams need accountability designed in, not assumed. Communication cadences and clear handoffs are what make a team in five time zones perform like one in a room.
The goal is a team that moves when you’re not in the room. That means developing people who own outcomes, not just execute tasks.
— In Practice
A team of about six needed to become a team of nearly thirty — fast. That kind of growth is where cohesion usually breaks: ownership blurs, communication overhead compounds, and the group that moved easily at six starts tripping over itself at twenty. The risk was never finding the people. It was staying one team while adding them.
The work was a structured build — defining ownership, accountability, and communication cadences up front, then growing into that structure rather than bolting it on once the cracks showed. The team scaled to 27 and kept operating as a single unit, not a loose collection of people who happened to share a roadmap.
The measure of a team isn’t how it performs while you’re building it. It’s whether it holds together after you’ve gone.
— Track Record
Across two decades of operating roles, the work has repeatedly been the same: stand up the team, define how it runs, and make it durable.
engineering team — built and still operating 10+ years on
from a DevOps function established from the ground up — team, processes, tooling, and standards from scratch
program (Deloitte and client personnel) led across a $15M engagement spanning five states
stood up from zero — professional services, customer support, and a 20-person software division
— Where It Applies
Team-building isn’t function-specific or industry-specific. The friction shows up everywhere talented people are underperforming the structure around them.
Engineering · Customer success · Professional services · Support · Operations · DevOps
SaaS · Collections · Healthcare · Banking & financial services
The same principles translate to legal practices, retail/wholesale/CPG, and restaurants.
— The Lens
Building teams that last is the throughline of a career spent in operating roles — from running a 20-person software division to directing customer-facing organizations of 60+ people, with the management-consulting rigor of a Deloitte tenure underneath it.
The difference between a team that performs and one that merely staffs a function is design. That’s the work.
— Keep Reading
— Let’s Talk
Growth exposes structural weaknesses faster than anything else. If your team is working hard and still falling behind, the answer usually isn’t more people — it’s a better design around the ones you have.