Don't forget, your staff have day jobs...
The vast majority of my work is finite project work (e.g., system selection or implementation). It's literally my full time job.
But for most of my clients, selecting and implementing a new AMS, or implementing a new website, or executing pretty much any other major technology project is in addition to their "normal" day-to-day job. That is, it's more work added to their already full plate.
There are three things to keep in mind when your staff is working on a large project that isn't part of their day-to-day job.
- Setting realistic timelines - Saying "we've got to get this done sooner" won't magically make it happen. And it also leads to point two...
- Understanding the trade-offs - When you add new projects to someone's list, you have to remove other projects (or move them to the bottom of the list). You can't just say "Do it all." (Well, you can, but you'll lose staff pretty quickly.)
- Showing grace for overburdened staff - Most often, the project your staff is managing and working on is outside of their typical skill set. And it's now more work for them. Keep that in mind throughout the project, and treat your staff respectfully and with the understanding that this can be challenging work.
"Extra work" is a reality of work. These projects will come up from time to time. Keeping these three points in mind will help you navigate the inevitable rough waters.
![]()
Wes's Wednesday Wisdom Archives
Perfection is expensive (in fact, it’s not possible!)
Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]
AI is a journey, not a destination
AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]
Action produces information
Action produces information “Action produces information. If you’re unsure of what to do, just do […]
Why a single source of truth is so beneficial…
Why a single source of truth is so beneficial… The holy grail of data management is […]
Just because you can, doesn’t mean you should
Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]
Data doesn’t need to be perfect to be useful
Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]
Don’t just clean data, clean reports and queries
Don’t just clean data, clean reports and queries One of the reasons I exhort my […]
Beware the automated “How did we do?” trap!
Beware the automated “How did we do?” trap! One of the downsides of technology is […]
Hindsight is 20/20
Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]
Cheaper now; costlier later.
Cheaper now; costlier later. Most of my clients are very cost-conscious, understandably. After all, who […]
