Should your agency challenge you, or just do what you asked?
Andrew Rannard
on
Both, depending on what’s being decided. A good agency should push back when what you’ve asked for won’t get you what you need. When the decision is yours, it should raise any concerns once and then respect what you decide. I’ve spent most of my career sitting between clients and delivery teams, and that’s the balance I’d look for.
Most clients come to us with a clear idea of what they want, and a lot of the time they’re right. Sometimes, though, it’s an answer to a problem that hasn’t been properly looked at yet. If we just build what’s on the list, we can hit every date and still hand over something that doesn’t do the job. If we question everything, the project slows down and your team gets fed up with us.
When should an agency push back?
In my experience it tends to come down to one of four things:
The scope won’t get you to the goal you’ve described
There’s a risk you can’t really see from your side, like security, accessibility or what the platform will cost to run after launch
The budget or timeline doesn’t fit the work, and it’s far better to say that at the start than halfway through
Users are likely to struggle with what’s been asked for, and we’ve got evidence to show it
How we raise it matters as much as when. We try to do it early, explain why, and come with an alternative rather than just a concern. Then we make the point once, because if a client has heard our reasons and still wants to go another way, keeping on about it doesn’t help anyone.
Which decisions should an agency leave to you?
There are also decisions that just aren’t ours to make, and questioning them only slows things down. Things like:
Brand, tone and how you want your organisation to come across
Priorities you’ve set using information we don’t have
Internal politics, and which stakeholders need to be involved and when
Trade-offs you’ve made knowingly, like launching with fewer features to hit a fixed date
If one of those carries a real risk we’ll say so and explain why, but after that our job is to support the decision and make it work.
What does that look like in practice?
The stripped-back homepage
On one website project, a senior stakeholder wasn’t happy with our homepage designs. Their view was that people don’t scroll, so anything below the fold wouldn’t get seen, and by the end they wanted about the most basic homepage you could build.
We pushed back. A homepage with very little on it can make it harder for search engines and AI tools to work out what an organisation does and who it’s for. That’s not easy to spot from the client’s side, and it’s exactly the kind of risk we should be raising.
The mega menu
This one I was involved in myself. A client wanted a mega menu on their new site, and based on what we’d learnt in discovery we didn’t think there was enough content to justify one, so we said so. It turned into a bit of a design-off between their designer and ours, with neither side able to win the argument, and when it started getting tetchy I was asked to get involved.
Once I spoke to some of their senior leaders, the reason came out. They were changing strategy in six months, would be publishing key insight reports, and wanted the mega menu to promote them, so it now had a business case.
Our push-back was fair based on what we knew. What we were missing was the reason behind the request, and the way to get it was to ask the right people why they wanted it.
How can you tell if your agency has the balance right?
If you’re a few weeks into a project with an agency, these are the questions I’d be asking:
Has the agency questioned anything in your brief?
When it’s disagreed, has it given you a reason and an alternative?
Does it raise a point once, or keep coming back to it after you’ve decided?
Once you’ve made a decision, has the team got behind it?
Are you hearing about risks when they come up, or after they’ve happened?
So, should your agency challenge you?
Yes, but only on the things that matter. The mega menu didn’t need a better design. It needed someone to ask why. A good agency questions what could put your goal at risk, says so once, and then backs your decision. The part you can help with is sharing the reasons behind what you’re asking for, as early as you can.
Andrew Rannard
Strategic Account Manager
Andrew is a strategic customer success leader with over 15 years of experience driving digital transformation for global enterprises. His proven approach has empowered industry leaders including Sky Sports, Heineken, Coca-Cola and RS Group, to achieve transformative business outcomes by aligning technological capabilities with strategic objectives.
Frequently asked questions
Is it a bad sign if my agency never pushes back?
Not always, but it’s worth asking why. If a few weeks in they haven’t questioned anything in your brief, either the brief was very clear or they’re not looking at it closely enough, and it’s worth finding out which.
What should I do if my agency keeps challenging a decision I’ve already made?
Tell them, because a good agency should make its case once, with a reason and an alternative, and then get behind what you’ve decided. If the same point keeps coming back, it’s fair to ask whether there’s a risk they think you haven’t understood, and if there isn’t, to ask them to move on.
How do I get my agency to challenge me at the right moments?
Put the reasons in the brief, not just the requests. If a feature or a design choice is there because of a change in strategy or something coming up later in the year, say so at the start. It also helps to give your agency access to the people who know why a decision was made. With the mega menu, the reason only came out once I spoke to their senior leaders, and it would have saved a lot of back and forth if we’d heard it in week one.