Problem awareness

If the first part of defining a problem is awareness ("No data, no problem”), it's worth asking:

How are you becoming aware of problems in your systems?

• Are you asking your staff about pain points they experience?

• Are you making it easy for your constituents to report any difficulties they may have?

• Are you tracking error messages that may appear at various points in user workflows?

• Are you monitoring and measuring all of those inputs to make high priority issues more visible?

Of course, there’s an alternative: Just a wait until an issue becomes so painful that it has to be addressed immediately. But that's never fun.

Here’s the thing:

Proactively gathering information puts you in a position to address any issues or opportunities before they become urgent.

How are you making that happen?

All the best,
A.