Adopting Agency Advice Without Breaking What Already Works

There’s a coach, a course, a skills pack, and a template for every part of growing an agency right now. A lot of it is worth your attention.

Applying it without breaking what already works is the hard part.

That’s the part nobody sells you. The advice is everywhere and most of it is good. What’s missing is the judgment to run it through your own agency before you bolt it on, because the same change that fixes one shop guts another.

Good advice and one-size-fits-all are not the same thing

Take time tracking.

Everyone preaches it, and they’re right. The data is table stakes. It’s the decision-making infrastructure you price, staff, and scope against. You can’t run a healthy agency blind to where the hours actually go.

But roll it out wrong and you teach your team something you never meant to teach them: that they’re being watched, measured, commoditized. The spark that made their work good in the first place, the part that doesn’t show up on a timesheet, is exactly the part that gets stamped out when the timesheet becomes the point.

Same trap with every other behavioral change. Project management workflows. File naming standards. Scope-creep guardrails. Every one of them is advice worth taking. None of them is one-size-fits-all.

The advice isn’t wrong. The assumption that it lands the same way in every shop is.

Run the change through how the agency actually works

My first step when I work with an agency isn’t to prescribe anything. It’s to understand how the place actually works, its values, its rhythms, the way it shows up for clients.

That’s not soft. That’s the filter.

Change has to run through that lens or it fits like someone else’s suit. The time-tracking rollout that feels like surveillance at one agency feels like clarity at another. Same tool, different culture, opposite result. The difference was never the tool. It was whether the change respected what made the place work before it arrived.

So before you adopt anything, you have to know what you’re protecting.

Two questions before you roll anything out

“Know which changes help” is easy to say and useless without a test, so here are the two I actually ask.

First: what behavior does this require from the people doing the work, stated as a verb, not a value? Not “more accountability.” Someone opens a timer at 9am and closes it at 5pm and categorizes eleven blocks in between. Once it’s a verb you can ask whether it’s realistic, and most rollouts die right here, on a behavior nobody was ever going to do daily.

Second: how will the person doing it read the reason for it? Every process change carries an implied message about what leadership thinks of the team. Time tracking says either “I need to price this work properly” or “I don’t believe you’re working.” Same tool. The message lands based on what you said, who said it, and whether the first thing you did with the data was help someone or question them.

If you can’t answer both, you’re not ready to roll it out. You’re ready to talk about rolling it out.

A failed rollout costs more than the rollout

The part that gets underestimated: a change initiative that fizzles doesn’t just fail. It spends something.

Your team learns that new processes arrive, get pushed for six weeks, and stop being enforced. The next thing you introduce gets met with a wait-and-see that you have to overcome before you’ve even started. Do that three or four times and you’ve trained an organization to outlast you, which is a much more expensive problem than a messy timesheet.

That’s the real reason to be selective. Not because change is bad. Because you only get so many of these.

Some of it should change you. The skill is knowing which

None of this means stand still. Some of this advice should shift your culture. That’s the point of it. Standing still in a market moving this fast is its own kind of risk.

The skill is knowing which changes help and which ones just break things. That’s the whole job. Not collecting more advice, there’s an infinite supply of that. Choosing which of it gets to touch the part of your agency that actually makes it good.

So change with intention, not by accident. The version of your agency on the other side of a careless rollout might not be one you recognize, and that’s scarier than going slow.