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
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
