One of the new projects that I am getting into is about comparing two different softwares (used for the same purpose). It is meant for the experts on Software A to be able to understand what's new in Software B. So the course will include some general observations, feature comparisons, file system comparisons, etc.
The default way to do this is to keep saying - 'this' works in Software A in this manner where as 'this' works in Software B in that manner. Which I don't want to do. I would like to make the comparison easier for the learner.
I wanted to know if anyone in the community has worked on anything similar? Any ideas, samples, or references would be of great help...
Aare there advantage to the process in software B over software A that you can use as selling points, e.g. software A took 10 steps but software B takes 3.
There is sometimes merit in (or need for) showing what will be different in the learners' work flow or primary work tasks. Focus not so much on the software differences, but more on:
if you want to accomplish this...now do it this way.
Thanks for the info Michelle. The comparison feature used by Microsoft is interesting. But this is not an upgrade. In fact they are two different operating systems.
Very true statement Bob. But like i told Michelle, it is not a transition from old to new. But transition from a different system altogether. A very simple example i can think of is introducing the Mac OS to somebody who is an expert in Windows OS. So we need to tell them instead of minimizing, you can dock. The hard disc partition set up is like this in windows but you will have to deal with it differently in Mac... so n so...
So what we have done is to identify some key topics. E.g., General Observations, File System, Program Execution, etc. And we are contacting the SMEs of both operating systems to understand how the File System and Program Execution is different in them. Once this is done, I am confused on how to present this. Like I said earlier, a comparison looks like an obvious choice. Just wondering if there is any other option...
I guess what I'm saying (and not so well! lol), is they already know how to do it on the other system, right? So you neither need nor want to spend their valuable time teaching that anymore..... ESPECIALLY if they have no choice and must convert to the new way anyways.
Rather show the improvement/upgrade/difference only.. For example....
Old System - Task X
12 steps
Requires 3 levels of approval
New System - Task X
Only 8 steps!
Let's review them together....
Step 1
Step 2
Step 3
Step 4
etc
Let's practice them....
Here's a Job Aid to remember them...
Tell us what you think?
Still 3 levels of approval - But Streamlined!
Let's look at how much simpler...
Approval #1
Approval #2
etc
Try a sample and see the time savings...
Let's see how it works in this scenario....
Scenario A
Scenario B
etc
What a few of us are trying to say is.... Yes, it's ok to draw out the differences compared to what they know.... but DON"T do a full side by side where you wind up reteaching the system they are leaving behind.
10 Replies
Is this an upgrade from A to B?
Aare there advantage to the process in software B over software A that you can use as selling points, e.g. software A took 10 steps but software B takes 3.
When Microsoft upgraded feom 2003 ro 7 and introduced the office button, they had a comparisn feature in from menus to Ribbons https://technet.microsoft.com/en-us/library/ff959696(v=office.14).aspx#section1. It used to be online but it apears you need to download it - it might give tyou an idea.
Regards
Michelle
Sayuj,
A wise veteran trainer once told me, "don't teach what you don't want them to focus on".
I bring this up because if they must transition from the old to the new, do you truly want to reinforce what they have now?
There is sometimes merit in (or need for) showing what will be different in the learners' work flow or primary work tasks. Focus not so much on the software differences, but more on:
if you want to accomplish this...now do it this way.
Spot-on, Brenda.
Thanks for the info Michelle. The comparison feature used by Microsoft is interesting. But this is not an upgrade. In fact they are two different operating systems.
Very true statement Bob. But like i told Michelle, it is not a transition from old to new. But transition from a different system altogether. A very simple example i can think of is introducing the Mac OS to somebody who is an expert in Windows OS. So we need to tell them instead of minimizing, you can dock. The hard disc partition set up is like this in windows but you will have to deal with it differently in Mac... so n so...
Exactly. Thanks Brenda
So what we have done is to identify some key topics. E.g., General Observations, File System, Program Execution, etc. And we are contacting the SMEs of both operating systems to understand how the File System and Program Execution is different in them. Once this is done, I am confused on how to present this. Like I said earlier, a comparison looks like an obvious choice. Just wondering if there is any other option...
Thank you everyone for your inputs...
Sayuj,
I guess what I'm saying (and not so well! lol), is they already know how to do it on the other system, right? So you neither need nor want to spend their valuable time teaching that anymore..... ESPECIALLY if they have no choice and must convert to the new way anyways.
Rather show the improvement/upgrade/difference only.. For example....
Old System - Task X
New System - Task X
What a few of us are trying to say is.... Yes, it's ok to draw out the differences compared to what they know.... but DON"T do a full side by side where you wind up reteaching the system they are leaving behind.
Hope this nuanced difference makes sense!
Completely agree with you Bob. Thanks for the insights. The detailed
explanation really helped. Thanks for taking the efforts. Very useful.
This discussion is closed. You can start a new discussion or contact Articulate Support.