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

Ratio of Data to Errors

April 12, 2023

Ratio of Data to Errors One of the elements of a good data governance plan […]

Back to basics

April 5, 2023

Back to basics Over the past couple of years I’ve noticed that some AMS vendors […]

Your people matter

March 29, 2023

Your people matter I’ve written many times about how people, process, and technology have to […]

We remember moments…

March 22, 2023

We remember moments… “We do not remember days, we remember moments.” – Cesare Pavese Another […]

Acknowledging problems is part of managing expectations

March 15, 2023

Acknowledging problems is part of managing expectations Research was done some time ago that suggested […]

Need data? Consider third-party sources

March 8, 2023

Need data? Consider third-party sources I always tell my clients, only collect data that you’re […]

Action must follow the decision

March 1, 2023

Action must follow the decision When I work with my clients on their projects (whether […]

Everything should be focused on improving user adoption

February 22, 2023

Everything should be focused on improving user adoption Your AMS is a tool, and a […]

Needs change over time, and that’s OK

February 15, 2023

Needs change over time, and that’s OK I was speaking with a couple of association […]

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 […]

Scroll to Top