The Value Proposition
The First 90 Days
When I walk into a team, I didn't build the org chart and I didn't set the habits already in the room. Whatever authority I'm handed on day one is borrowed. What I earn in the first ninety days is the only authority that's mine. Here's how I spend them.
I don't come in with an opinion. I come in with a list of people to talk to first. Before I run a single team meeting, I sit down with every direct report, one at a time, and ask the same five questions: What's working? What's broken? What would you fix if it were up to you? What do you need from me? What haven't I asked that I should have? I ask everyone the same five on purpose. One person's complaint might just be one person's complaint, but four people saying the same thing without comparing notes is a pattern, and I want to know which one I'm looking at before I decide anything. By day 30 I haven't fixed a single thing. I can just say, without guessing, what's true about this team.
- Run individual 1:1s with every direct report before the first team meeting
- Sit in on existing ceremonies before changing any of them
- Pull velocity, budget, and turnover numbers straight from the source, not a summary
- Keep a dated log of what's broken and who it currently belongs to
By month two I've earned an opinion. I haven't earned a mandate, so I go get one. I bring my read of the team back to the people who gave it to me, before I take it to anyone above them. If I got something wrong, I'd rather hear it from them now than get corrected in front of my boss later. Then I ship the one or two fixes that were already obvious to everyone and belonged to no one, quietly, and credit them to the team instead of me. Everything bigger goes into a real plan, one I hand my manager as something to argue with, not something already decided.
- Check my read of the team with them before taking it upward
- Ship the one or two obvious fixes that already belonged to no one
- Set the metrics I'll be judged against, in writing, agreed with my manager
- Present the 60-day plan as something to pressure-test, not a done deal
Talk is cheap by month three. I need something people can point to. I execute the highest-visibility piece of the plan first, tracking the numbers honestly from the day it starts rather than from whenever they start looking good. I tell the team why a change is happening, not just what's changing, because people who don't understand a decision will quietly undo it the moment I stop watching. At day 90 I bring my manager a straight scorecard and set the next ninety days instead of just riding whatever momentum is left.
- Execute the highest-visibility item on the plan first
- Log real before-and-after numbers from day one of the change
- Build the skip-level and peer relationships I didn't have standing for yet
- Bring a straight day-90 scorecard and set the next 90-day arc
Superpowers
Everyone has a favorite superhero, and it's rarely random. Usually it's the one whose powers land closest to how they see themselves. These are the four traits that keep showing up across twenty years of work. Most people in this kind of role are strong on the systems side or the people side. These four are what happens when you build real strength in both at once.
The Fixer
I get handed the broken programs and build the systems that let people stop guessing. Sometimes the program has never existed, sometimes it's been failing for years, sometimes it just needs a tune-up and a more scalable design. I assess what's actually there and build from that reality.
A credit union had been trying to recover a two-year schedule overrun for months. Executives had stopped believing it would ship at all. I rebuilt the timeline, re-established partner relationships, and built the work breakdown structure to form a real schedule. Delivered to every customer the credit union served, full scope and quality intact, and contributed to the team behind a second Malcolm Baldrige National Quality Award.
The Bridge
I take what leadership wants to achieve and turn it into something the team can build. I take what the team builds and turn it into something leadership can see value in. That's the full loop, and it works from the C-suite to the ticket queue.
When leadership says they want to grow revenue, I turn that into something a team can actually build with clear success metrics. When the team builds something that doesn't obviously connect to the original ask, I explain how it fits and why it matters to the business. I move between strategic and tactical without losing the thread.
The Signal
I read what's unsaid before it becomes a problem. Micro-expressions, body language, the gap between what someone says and what they actually do. I catch misalignment before it shows up in any metric, and I act on it directly.
A mocking expression when someone hears a process change tells me that team isn't following it. A client services exec walking the floor instead of using the submission process tells me the process lost them. A leader saying the right words while the person behind him smirks tells me the org isn't ready for what they just agreed to. Those moments tell me what's really happening before any metric catches up.
The Multiplier
I develop people so the team runs without me. I give real authority early, set clear expectations, and build capability through real work instead of training decks. That scales from coaching one person through a hard stretch to retraining an entire department into roles the org actually needs. The measure of success is what other people can do in the room after I've left it.
I took Scrum Masters and developed them into senior-level practitioners who don't need me in the room anymore. I started a weekly office hours tradition that grew from zero to forty-five people showing up voluntarily because they wanted to.
Do any of these problems look familiar?
Whether the company is growing, scaling, transforming, or recovering, these are five of the problems I solve most often. Here is what I do about each one, and where I have done it before.
Our technology is falling behind
Most companies accumulate systems faster than they consolidate them.
We can't keep or develop our people
I fix both the system and the people side at the same time.
We have no visibility into our own delivery
I build the planning infrastructure that gives leadership real-time delivery visibility.
Our organization can't transform fast enough
I rebuild the layer between teams and leadership so it stops filtering reality.
We just lost a key leader
I step into the vacuum and get every pipeline delivering without breaking stride.