The solo traveller…Calling out problems

Lately I’ve been swirling around thoughts of how awkward calling out problems are, especially the ones where everyone thinks there is no problem or perhaps a few have noticed the problem, yet no one is calling for action. Say for example you are creating a User Guide to support users. When you’re reading it there are gaps or ambiguities. Everyone else is saying it’s good enough.

This is exactly why you should have people in your team that are outside the building of products or artefacts. They will hold you to account.

In the example, call out the problem and why it’s a problem and add an open question “How are we going to solve this?.

I’ve learnt that without the call to action you can sometimes get in a back and forth debate about the problem. Discussions are a good thing, however, at some point you need to do something about it.