Balancing what is possible with what is realistic
When I work with clients on technology projects, I'll tell them "These are blue sky discussions. Nothing is off the table." I'll usually follow that up with "But just because we discuss something doesn't mean you'll actually get that something." Because even if what is being discussed is available and accessible, it may not be technology the association really needs or can leverage.
Often, we need to balance what is possible with what is realistic. Some examples:
- Yes, it would be great to have a pure CRM system that can automate so many things. But do you have the staff and resources needed to manage it and take advantage of its capabilities?
- Yes, it would be great to have an online community. But communities, especially at their outset, need a lot of care and feeding by staff, to nurture them. Do you have the staff resources to do this?
- Yes, it would be great to collect all those data points about our members. But do you have the technical and staff capacity to collect and analyze that data? And will you actually USE the data?
Technology is a great enabler. But often new technology requires additional resources to really get the most value out of it.
And so, as the old saying goes, just because you can doesn't mean you should. Always keep your mind open about what is possible, but also be realistic about what can be implemented effectively.
![]()
Wes's Wednesday Wisdom Archives
Start small
Start small When I work with my clients on projects that involve measuring member engagement, […]
Some context, please
Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]
Eventually automated emails get ignored
Eventually automated emails get ignored During the discovery and development phase of implementing a new […]
The challenge the AMS providers see
The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]
Be careful about “solutioning” too quickly
Be careful about “solutioning” too quickly One of the great things about software developers is […]
What’s our next action?
What’s our next action? As you can imagine, I spend a lot of time in […]
Don’t automate for the sake of automation
Don’t automate for the sake of automation I’m the laziest person in the world. I […]
Don’t forget about what got better
Don’t forget about what got better Negativity bias is the tendency to focus on only […]
Give a little at a time rather than taking away
Give a little at a time rather than taking away I’m sure there’s research somewhere […]
First, you gotta have the data
First, you gotta have the data When I work with clients on a new AMS […]
