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

The vaguer the question, the vaguer the answer

February 9, 2023

The vaguer the question, the vaguer the answer As the old saying goes, the devil […]

The best choice given the information you have

February 2, 2023

The best choice given the information you have “Hindsight is 20/20” is a cliché because, […]

Action isn’t the same as progress

January 25, 2023

Action isn’t the same as progress I’ve written before that not taking action is an […]

Start with the end in mind

January 18, 2023

Start with the end in mind Like so many, I probably first heard the phrase […]

It’s quiet in here…maybe TOO quiet…

January 11, 2023

It’s quiet in here…maybe TOO quiet… One of the truisms of data management is that […]

It’s ALWAYS about expectations

January 4, 2023

It’s ALWAYS about expectations The headline reads: “Tesla sets record for vehicle deliveries, an increase […]

It’s hard to get UNangry

December 14, 2022

It’s hard to get UNangry I often emphasize to my clients the importance of testing […]

Some history IS important!

December 7, 2022

Some history IS important! When I’m advising clients on data conversion (moving data from one […]

“Many mickles make a muckle.”

November 30, 2022

“Many mickles make a muckle.” “Many mickles make a muckle.” – George Washington Apparently, this […]

It’s easy to collect; it’s harder to manage

November 16, 2022

It’s easy to collect; it’s harder to manage The beauty of today’s highly configurable AMS […]

Scroll to Top