Working in a marketing agency for the financial sector is a rewarding and fun career path. As the head of the digital team at Yardstick, I oversee a group of talented website designers and developers who work tirelessly to create and maintain exceptional websites for financial advisers and planners.

It’s a rewarding job, but there’s a three-word phrase that frequently pops up in our inboxes, Slack messages, and client calls – one that seems harmless at first but often carries significant implications:

“Can you just…?”

It’s a phrase we hear all the time. “Can you just change this button colour?” “Can you just move that text slightly to the left?” “Can you just add this small new feature?”

Individually, these requests seem minor, quick, and simple. And sometimes, they are.

But often, they are the tip of the iceberg, revealing complexities that aren’t immediately obvious to those outside the development team.

The hidden complexity behind “Can you just…?”

The phrase implies ease and speed, but digital work isn’t always that straightforward. Here’s why:

1. Small changes can have big consequences

Moving a button might sound trivial, but if it affects responsiveness across devices, it could require multiple adjustments. A seemingly simple tweak to a form might require changes to the database, testing, and compliance checks.

Sometimes, these small changes can even unintentionally break other parts of the site, especially when they interact with more complex systems like animations, tracking, or third-party integrations.

2. The domino effect

Websites are intricate ecosystems where every element interacts with another. A small request in isolation may not be much, but when compounded with multiple similar requests, it can lead to scope creep, timeline delays, and increased costs.

A series of “quick fixes” can slowly morph a clean, streamlined build into a patchwork of mismatched parts – reducing overall quality, consistency, and performance.

3. Time and resource allocation

Each “quick fix” takes time – sometimes more than expected. When developers are constantly pulled into ad hoc tasks, it disrupts focus and workflow, impacting the efficiency of bigger projects.

Every interruption has a cost; it pulls attention away from complex builds or strategic improvements, and that can cause bottlenecks not just for one person, but across the whole team.

4. Client expectations v technical reality

It’s natural to want your website to reflect updates quickly. But sometimes, what seems like a small cosmetic update can sometimes involve updating plugins, modifying code libraries, or navigating third-party limitations.

What might look like “just moving a button” can mean touching 10 different files and testing across four browsers and five screen sizes.

How to make “Can you just…?” work for everyone

This isn’t about discouraging requests but about creating an understanding of the process behind them. Here are a few ways to make these small requests more effective and manageable:

• Be clear and specific – The more context and detail you provide, the easier it is to assess the request’s feasibility and impact. Include screenshots, describe what you’re trying to achieve, and let us know if there’s a particular deadline or reason behind it.
• Understand priorities – If multiple requests are in play, consider which ones align with the broader business objectives and need to be prioritised. This helps us allocate the right resources to the most impactful tasks.
• Batch similar requests – Instead of sending multiple one-off changes, grouping similar requests can make implementation more efficient. It reduces the back-and-forth and allows developers to plan and execute changes more smoothly.
• Trust the experts – If a developer or designer pushes back on a request, it’s not to be difficult – it’s to ensure the best possible outcome. Often, there’s a reason why something hasn’t been done a certain way, or why an alternative might be better.
• Schedule regular check-ins – Having scheduled sessions for reviewing changes, updates, and new ideas can reduce the volume of reactive “Can you just…?” requests and keep things running more strategically.

The final word

“Can you just…?” isn’t a bad phrase, but it’s one that needs careful handling in website development. By recognising the effort behind even the smallest changes and fostering better communication, we can create a smoother, more productive workflow – one that benefits both our team and our clients.

So, the next time you find yourself about to say “Can you just…?”, take a moment to consider what’s really involved. You might just gain a new appreciation for the work happening behind the scenes.

And, if you ever have a “can you just” moment – go ahead and ask. Just know that there’s always more behind the screen than meets the eye. That awareness helps us deliver better results, work more efficiently, and build stronger partnerships with the clients we serve.

Here to help

Got a request for us? Get in touch and let us help!

Email hi@theyardstickagency.co.uk or call 01156 8965 300.