Training and testing

Training and testing

I've written before that the best form of training follows this process: Tell them what you're going to do, tell them what you're doing, tell them what you did.

When working with your software company to report bugs or other issues, you should follow a similar process:

  1. Tell them what you were trying to do. For example, "I'm trying to process a membership order."
  2. Tell them how you did it. For example, "Here are the steps I followed." Be as explicit as possible and include screenshots!
  3. Tell them what happened. Show the results of your steps (again, including screenshots).

We've all heard "a picture is worth 1,000 words." I mentioned screenshots twice above for that very reason. Screenshots often communicate more than any narrative can.

"The membership join process doesn't work" is reporting a bug, but it's almost useless in terms of helping the software company figure out your problem. But following the process above will clearly communicate the issue and bring a resolution much more quickly.

Wes's Wednesday Wisdom Archives

Is that meaningless data?

September 25, 2019

Is that meaningless data? I’m not a big quotes guy, but one of the few […]

Be aware of unintended consequences

September 18, 2019

Be aware of unintended consequences I’ve written before that every decision involves a trade-off. When […]

Positive change is harder to see

September 11, 2019

Positive change is harder to see Humans are wired to see negative change because we […]

MVP: Minimum Viable Product

September 4, 2019

MVP: Minimum Viable Product In product development there is a concept known as MVP, or […]

You always need a reason for collecting data

August 28, 2019

You always need a reason for collecting data When you ask for data from someone […]

If you’re unhappy, speak up!

August 21, 2019

If you’re unhappy, speak up! My clients will often ask me something along the lines […]

Does it advance the mission?

August 14, 2019

Does it advance the mission? Because associations are mission-driven, everything you do should be seen […]

How should you start a new data project?

August 7, 2019

How should you start a new data project? When you’ve got a new data project […]

A Data Integrity Report…for Reports!

July 29, 2019

I’ve written elsewhere about the value of data integrity reports. But one of the most […]

Simple rules for complex systems

July 28, 2019

Simple rules for complex systems I first heard the phrase “simple rules for complex systems” […]

Scroll to Top