Be careful about “solutioning” too quickly

Be careful about "solutioning" too quickly

One of the great things about software developers is that they tend to be "solutions-oriented." By that, I mean that if you give them a particular data management challenge, they want to figure out some way the software can address that challenge. This is a good thing!

But too often, we jump to solving a problem ("solutioning") before we really understand the scope and breadth of the problem itself. An example:

One challenge a client has is address changes made by members via the member portal. When these address changes are made, sometimes they can affect which chapter the member belongs to. And so the client wants a solution that allows for the staff to check address changes before they are "posted" to the member's account. An interim step to allow for quality control.

On the surface, this seems like a challenge worth addressing, and anything that could automate the process would certainly be helpful. Upon further digging, though, we discovered that, for most of the year, there are only about 10-12 of these changes per month. So rather than trying to build something to automatically deal with this, the correct approach is to check these manually as address changes are made. No automation required.

My recommendations before solutioning an issue:

  1. Understand the depth of the problem. How often does "this thing" happen? How many transactions occur in a given time period?
  2. Understand the breadth of the problem. For example, what's the financial or reputational impact if we don't automate this? If it's done manually and takes a little more time than automation would, who will notice, and is that a big problem, or a little problem?
  3. What if we did nothing at all? Or put another way, do we really need to do what we think we need to do? If we did nothing, would anyone notice?

Solving problems is great. But sometimes the solution is more than the problem demands. Be careful about falling into the trap of "solutioning" without understanding the breadth and depth of the problem.

Wes's Wednesday Wisdom Archives

Data is for action

June 22, 2022

Data is for action When deciding whether or not to collect a piece of data, …

Data is for action Read More »

Have you shopped yourself?

June 15, 2022

Have you shopped yourself? I’ve always been fascinated by the “secret shopper” concept. (Maybe it’s …

Have you shopped yourself? Read More »

To improve adoption, decrease the friction

June 1, 2022

To improve adoption, decrease the friction “Before you try to increase your willpower, try to …

To improve adoption, decrease the friction Read More »

“Is this normal?”

May 25, 2022

“Is this normal?” ne of the greatest parts about my job is that I get …

“Is this normal?” Read More »

Give your staff more freedom, not less

May 18, 2022

Give your staff more freedom, not less I often tell my clients, when it comes …

Give your staff more freedom, not less Read More »

My advice? Stop doing that

May 11, 2022

My advice? Stop doing that! There is a classic TV sketch featuring Bob Newhart as …

My advice? Stop doing that Read More »

Is a college degree really required?

May 4, 2022

Is a college degree really required? I saw a job listing last week for an …

Is a college degree really required? Read More »

Small actions become big wins

April 27, 2022

Small actions become big wins I’ve written before about how data accretes, the idea that …

Small actions become big wins Read More »

Try not to OFFEND your members…

April 20, 2022

Try not to OFFEND your members… I recently received an email from an association where I’ve …

Try not to OFFEND your members… Read More »

How will you use that data?

April 6, 2022

How will you use that data? One of the beauties of technology today is how easy …

How will you use that data? Read More »

Scroll to Top