First things first

When everyone’s giving you tasks and they’re all urgent, where do you begin?

As UX writers, we get a lot of asks. There are far fewer of us than designers, product managers, and a slew of other stakeholders who need copy from us. That means we’re getting lots of requests at the same time, while the people asking don’t necessarily have an understanding of everything else we’re juggling. We don’t want to let anyone down or miss any deadlines, but at the same time, we can only do what we can do. Here are some things to keep in mind when deciding how to prioritize and not burn yourself out trying to do it all at once.

Process

There’s no one-size-fits-all solution, do what’s right for you. Maybe you do want emails, but the subject line must begin [COPY ASK]. Maybe you want Slacks, but in a dedicated channel for copy asks. Maybe a shared monday/Trello/Asana board were people can open tickets. Whatever you decide, communicate it and stick to it. Make it known that asks that don’t follow the intake process will be duly ignored. It’s not personal, it’s process, and it’s in place for everyone’s benefit.

If you’re part of a team, and not a lone soldier, you’ll need a step two: from intake to triage. Let task owners know which writer has been assigned so that a) they know who to follow up with and don’t bug the whole team; b) they know the task has been picked up and not fallen between the cracks.

Impact

Every task is a use of your time and your time is a limited resource. Every minute you spend on one task comes at the expense of another. Make that tradeoff wisely.

Urgency

Image Credit

This might be the most obvious one — prioritize according to urgency. Is the task part of a fix for a security breach? Pop that baby up to the top of the list. Is it to support a marketing campaign planned for Q-no-one-knows? It can wait.

ASAP is not a deadline. Let task owners know that specifying deadlines are a requirement in the intake process, and anything labeled ASAP boards the express train to the bottom of the list.

Sometimes, owners won’t know how to define their deadline, you can help. Ask what the task is blocking; and what dependencies the task has and the timeline for those to be resolved. I’ve had owners tell me they need something quickly and the truth was they needed it the following sprint, while others told me there was plenty of time — three whole days. Because “fast” is subjective, keep asking questions until you get a hard enough answer that you can line it up fairly against everything else you’ve got going on.

Scope

I’ve been asked for 500 words which the owner assumed would take days, when the truth was that I had so much evergreen content to lean on, that I scoped it at about an hour. I’ve also been asked for a 10-word error validation that the owner assumed was a matter of minutes, but once drilling down into the various states, segments, and entry points, realized the task would take two days.

Don’t let owners dictate scope. Only you have the tools and experience to scope accurately and when you manage expectations — including your own — everyone benefits.

Dependencies

Scalability and automation

Doing the research, getting the approval, installing, distributing, training, and maintaining the tool will take time away from other tasks, but will pay for itself many-fold in the currency of your time, a valuable commodity indeed. Look for ways to improve overall efficiency and do take the time away from ticking tasks off your list, to make task ticking faster and better overall.

Communicate

Image credit

UX writer specializing in complex products. Passionate about making tech accessible to mass markets. Also a proud em dash enthusiast.