It started in 1992,
in the Army.

The Story

Built from accountability, not theory.

I've spent the better part of three decades at the intersection of strategy and execution. Not consulting from the outside, but working inside organizations during the hard moments: turnarounds, transformations, leadership transitions, and the slow, difficult work of building something that actually lasts.

That experience is what I bring to the boards and leaders I work with today. Not frameworks borrowed from someone else's context, but the practical, earned judgment that only comes from having been accountable for real outcomes at the highest levels.

I started in line leadership, running teams, owning P&Ls, learning what execution actually requires before I had any business advising other people on it. I moved into senior executive roles across technology, services, and enterprise transformation. I've led organizations through the kind of change that doesn't fit neatly into a consultant's slide deck.

Today I run Virtuoso Strategy, my independent advisory practice, alongside a senior leadership role in enterprise consulting. The practice is deliberately small: never more than five active board seats. Up to three advisory engagements. Speaking on the topics I've lived through. And writing that reflects what I'm actually seeing inside organizations, published every week.

I started in the Army in 1992. Four years enlisted, stationed at the Pentagon, working on secure communications. That's where the thirty years starts, and it's where I learned that owning the risk isn't a posture. It's a job.

Since then I've owned P&L at every level I've worked, and managed pieces of it at every level above that. Twenty-person companies where I knew everyone's name. Mid-market firms from a few hundred to a couple thousand. And now a company with tens of thousands, where the hard part isn't making the decision. It's getting the decision to survive the trip.

Public companies answerable to shareholders and the market, and private ones. Private companies with boards built to resemble public companies, and private companies run by the owners and founders. Commercial businesses, and government contractors where set-aside status shaped what you could bid before anyone got around to talking strategy. I've also worked inside government rather than selling to it, and being on both sides of that table teaches you things the briefing decks leave out.

Before any of the advisory work, I came up technical, and I worked every rung of it. Junior engineer to architect to leader. I designed networks and security architectures, built large-scale automation programs, and wrote the policy that governed them, for defense and intelligence agencies, federal and state government, and commercial clients across telecom, media, life sciences, financial services, and healthcare.

Then I ran the people who do that work. Teams of engineers, architects, and consultants. I ran support organizations through telecom mergers, which is where you learn that two working systems do not make a third working system. More recently it has been enterprise-wide modernization for Fortune 50 companies, at a scale where the technology is rarely the hard part.

That's a gloss across thirty years, not a resume, and none of it is what I sell today. But it is where I learned to read risk before it shows up on a P&L, and to tell the difference between a problem that is technical and a problem that is wearing a technical costume. That turned out to be most of what business advisory actually is.

Single-city operations. National footprints. Multinationals across North America, Europe, the Middle East, and Africa. Russia, Asia, and South America I haven't worked directly, and I'd rather say so than pretend the map is complete.

I bring it up for one reason. Most advisors have depth at one altitude. The problems look different at twenty people than at twenty thousand, and counsel that works at one end will quietly wreck the other. I've been accountable at both.

My books and speaking keep coming back to one moment. The room goes quiet, and everyone starts doing the math on who owns the downside. The Room Goes Quiet is the first of them.