How do you organize your work requests? Have you got your system down?
I’ll be honest: when it comes to task management, I’ve started, abandoned and restarted systems. It’s easy to let ourselves get disorganized when things get chaotic!
But for requests that involve staff (or other constituents), it’s never a good idea to let this slide. You need to proactively capture those needs, stakeholders, and project updates. Otherwise, details slip through the cracks and communication breaks down across teams.
A good process keeps us covered here. We know how to build a framework that guides us in executing requests. We’ve also figured out how our colleagues should reach out to us. Now it’s accountability time: how do we document and manage that process from start to finish?
Have you ever spent unnecessary time on a request, all because you & your colleagues weren’t on the same page? *raises hand*
It’s not a great feeling! But that’s what happens when you don’t organize those requests early on. If you write content for your org, create reports, build lists, or do anything that requires even the slightest bit of niche expertise….let’s chat.
A while ago, I shared tips on how to build a staff process that people can actually follow. Because when you start getting overwhelmed with requests, a process is key to staying cool and organized.
We did the first step of clarifying how these requests play out in our orgs today. We’ve got notes on everything that matters: the types of requests we get, the needs of our requestors and our own team’s capacity. (If you haven’t read that first post, you’ll want to start here.)
Now that that’s done, we need to translate those points into a living, breathing process. That’s a big leap, especially when you’re not used to doing it!