In response to The Daily Post’s writing prompt: “All It’s Cracked Up to Be.”
Currently I am working as a systems analyst and one of the things I have to do is presenting new features of the system to the clients. Showing the system may take two forms:
- Demo – when one person shows the system for others who are just watching;
- User training – when one person demonstrates what to do and others have computers and they repeat the demonstrated scenarios.
With new system features the second kind of showing may become stressful, because there are a lot of unknown parameters:
- The system may work slower than usual, when numerous people simultaneously push the “Save” button in the test environment;
- There may be more people in the training than there were in the invitation, so the demonstrators have to give them rights in the system;
- The system may be slow, if no one has clicked through scenario in that day (SharePoint);
- The system integrates with other systems, and all these are test versions, so some integrations may stop working;
- Trainees usually want to test their favorite scenarios, not the suggested ones;
No one can control all this, and no one guarantees, that the training will succeed. However, I have received two pieces of advice from colleagues, that have helped me to turn the trainings out exactly as I’d hoped.
The first is to click through the scenario before the demonstration, pretending to be like a simple user – with test user, with fewer rights, with some more steps than will be actually shown. This can make the system a bit faster, and gives confidence.
And the other advice is meant to calm me – it doesn’t matter whether I stress about the demonstration or not, because the performance of the system if not affected by my mood. System will do what it was programmed to do. So I can be calm, because stressing out doesn’t make anything better.
Since I have received and used these advice, the demonstrations of the system have gone as well, as was expected.