When's the "least bad" time?
When working with clients on a new project, especially a new system launch, the question is always asked, "What's the best time to do this?" And after a long discussion about all the possible dates and how none of them will really work, I usually suggest "How about we find the 'least bad' time to do it, then?"
Because with rare exception, my clients are busy all year round. (I did have one client once who was so slow during the summer months that the membership director painted the office!)
And the fact is, there is likely to be no "good" time when work is slow enough that it's a great time for a new system launch. So what we're looking for then, is the "least bad" time.
Framing the date as "least bad" allows us to acknowledge that there is no "ideal" time to do this, so we're going to do it when it's the least disruptive. And most of the time, that's the best we can hope for.
Wes's Wednesday Wisdom Archives
Once you know, what will you do?
Once you know, what will you do? I’ve yet to meet a client who didn’t […]
If it’s not in your AMS, why not?
If it’s not in your AMS, why not? I like to tell my clients they’ll […]
Why checkboxes and tags are awesome and dangerous
Why checkboxes and tags are awesome and dangerous One of the most common functions in […]
Don’t miss obvious engagement data
Don’t miss obvious engagement data What I’ve experienced with my clients over the years is […]
All data requires active management
All data requires active management It’s a simple fact of data management that is often […]
Documentation is critical for consistency
Documentation is critical for consistency There are so many reasons why documenting your data management […]
Consumer demands change and technology changes
Consumer demands change and technology changes When I work with clients on the selection of […]
Why I write
Why I write Thirty years ago, I started a new job as director of membership […]
DAN – The Data Analytics Network
DAN – The Data Analytics Network I’m a huge fan of users groups (both internal […]
Process before technology
Process before technology In a conversation with a client recently, I was reminded (yet again) […]