They asked me to scale our fastest methodology. I scaled the cost table instead.

Somewhere past our twentieth project with the same client, I realized I could price a job in about thirty minutes.

Not a formal proposal. An email: scope, timeline, a hard-cost number I hadn't looked up, and a date we could start. The identical document for any other client in the firm took a day or two, because it had to go to field operations first, and field operations wouldn't put a number on anything until they had real bids back from vendors. The bids took as long as they took. But this client wanted work in a week, and I had to figure it out.

No surprise, but the executive team noticed the speed. The work was fast, it was lucrative, and it was the best client relationship we had. So they asked me to scale it.

But what they meant was the work itself. The in-the-room stimuli development and analysis our team cut in half to service the work. I had to tell them they were looking at the wrong part of the job.

The methodology really was unusual. We really did cut the time it took to run a (profitable) project from 12 weeks to 6, sometimes less. And that meant changes to everything we did in a typical client engagement.

But almost none of it was going to scale across the business, because it depended on a client who could decide things at that speed. Most of our clients couldn't. They had legal review, brand approvals, three stakeholders who needed to see materials before they went in front of anyone, and a real institutional aversion to being surprised in a room. That isn't a failing on their part. It's how large organizations protect themselves, and agencies like ours have to shape our work around that reality.

The harder thing to say out loud was that the speed wasn't really the process anyway. It was reps. After a few dozen projects every year, I knew what recruiting cost for their audiences without checking. I knew their rhythm: a hurry to get the work secured, then a week of silence while they figured out internally what they actually wanted, then a two- or three-day sprint to build materials, then the live iteration, and a ten-slide deck at the end where any other client would have gotten fifty. Those reps are what made the system work for that client, and it all lived in my head.

What did generalize was the part that doesn’t go on the case study.

Audiences repeat across clients. What it costs and how long it takes to recruit forty small-business owners doesn't change because the logo on the deck changes, and after enough projects the firm collectively knew that number several times over. It just knew it in pieces, scattered across people's heads and old vendor emails, and nobody had ever sat down and turned it into a table, because doing that is bookkeeping and it wasn't anyone's job.

So when I added the Head of Operations role, that's what I built with the Field Operations team and PMO. Average recruiting costs by audience type. Proposal templates we could fill in for the clients and audiences that came up again and again. A database of project timelines that let us see where things actually got stuck and which clients were most likely to cause it, so we could push ahead in some cases and set expectations early in others. For the media team, whose work was opaque to everyone outside it, we built an offering list with real prices and real turnaround times attached, so a project lead could finally see what they were able to sell.

My first read on field operations was fear. They were treated as a cost center, a wrong estimate meant lost margin, and margin was the thing the finance side cared about most, so of course they wouldn't commit to a number before the bids came in. I came into the operations role holding the project teams' view of it, which was that the client expects us to make it work, so we expect you to make it work.

That read was mostly wrong, and it took me a while to see it. What they were protecting wasn't themselves. It was their craft. They were genuinely good at sourcing and negotiating, that skill was the reason the numbers were good, and putting it into a table a project manager could fill in without them felt like being asked to give away the thing that made them worth having. Which, by the way, it partly was.

The argument that eventually worked wasn't about trust. It was that an estimate that's ninety percent right today is worth more than one that's exactly right in two weeks, because the proposal either goes out this week or the client stops waiting. And once the averages existed, nobody had to guess at all. The estimate stopped being an exposed personal judgment and became a number the firm already owned, which is the part that finally broke the deadlock. The recruiter who pushed back hardest is still there, running the department now as a VP.

Nothing forced the original version. I built it for one client because I was tired of waiting two days for a document I could write in twenty minutes, and I did it without asking.

Now the uncomfortable part for anyone who’s worked in Corporate America. What forced the general version was our parent company. Around that time they started taking a much closer interest in every business unit's numbers, particularly billable time, net revenue, and margin, after years of mostly leaving us alone. I don't think the executive team put me in the role as a financial play. I think they knew I'd build systems and get the teams moving. But that pressure forced the change, and I want to be honest about that.

Last week I made the case that magnitude is what gets lost when we relay problems up to decision-makers, and that leaving it out is the gap. So I should be honest that I did a version of the same thing here, on purpose, and that I'd do it again.

The reason is that my audience was different. I never framed any of this to the operations teams in the parent company's terms. I sold it internally as making their work visible, trackable, and more valuable to the project teams, which was true and which is what I actually believed. Upward, it was a margin and utilization story, and that was also true. I made a call that connecting the two out loud would kill the first one.

Field operations' original instinct wasn't wrong, by the way. Measurement does get used to evaluate people, and they knew that better than I did. If I'd opened by saying the parent company wanted better numbers, the tables would have been built to satisfy a reporting requirement, and they'd have been abandoned as soon as the requirement changed. Built for the teams themselves, they’ve become a core part of how Operations works, outlasting my time there by years.

Proposal turnaround dropped by about half. Project efficiency improved around fifteen percent, project margin moved up roughly five points, and we ultimately crossed that 100 project benchmark a few years later.

I can't cleanly separate those numbers from the parent company's new attention, because both were happening at once and scrutiny alone moves margin for a while. My claim is narrower: we stopped losing weeks to a question the firm already knew the answer to.

Look at the fastest-moving, best-run account in your organization, the one everybody points to.

Ask why it works. If the answer is the process, see whether anyone can describe that process without naming the account, because if they can't, it isn't a process yet. And if the honest answer is reps, then ask which part of those reps has been written down, and who would have to give up something they're proud of to write it.

That's usually where the value is, sitting in one person's head, uncounted, in the least interesting part of the work. It's worth finding out whose head, and asking them nicely.