Presentation Trifecta; Part 3
Presentation Trifecta Part 3 was posted a couple of weeks ago. I previously discussed part one and part two. As it worked out, in this portion of the recording I have very little participation. There was an early question about video training, and I discussed how there was on-line live training available for SSP and then discussed the (then) upcoming on-line on-demand training.
Most of the conversation seemed to involve the topic of software piracy, and I (for some reason) didn't join in on that part of the discussion. I am willing to say something on matter, although its always a bit of a risk to do so. Those of us in the software industry share a similar problems as those in the music and video industry, in that there is a general perspective among many that the sharing of digital content is permissible. The simple matter of fact for us is that our operations here at R-Technics for SSP are supported solely by the revenue generated by new sales and ongoing subscriptions-- 'nuff said.
In part two, we discussed the influence on how the user interface in SSP was originally designed and how it has evolved. One factor that is important to me is watching users actually use SSP. I do this at our church. It's interesting to see someone try to complete a task, such as add a background to a song. Its interesting to watch both those who are experienced as well as those who are novices accomplish this task. Watching the novices use SSP shows me where they expect to see the relevant user interface controls. Watching those who are experienced reveals to me what process works best for them.
I generally do not run SSP during the worship services at our church. When I'm involved in a service, I'm on the worship team playing keyboard or guitar. And if I was doing anything else, it would be running sound. However, I do use SSP on a regular basis to build the slide shows that our church uses weekly. This has helped me improve the slide show builder in a number of ways, after all, if something irritates me about SSP, there's a very good chance that something is going to change! But I also recognize that there's a significant disconnect between technically minded computer programmers, and mainstream technical users -- so just because I'm okay with how something is, well, perhaps that's the first indication that I should ask for a second or third opinion!
(BE133)
Comments:
I am a firm believer in the idea of 'If you use the software, you should pay for it.' The only problem I have is, if I am going to you a peice of software only only once, I don't want to have to buy it. Don't get me wrong, I would be willing to pay a pay-per-use, but to pay $60 plus dollars for a program you are only going to use once, is a bit much. I realize how that could be costly for a company to keep up with, and understand the issues that the company would face. There really ought to be a way to 'rent' software. If it could be coded for a single use, then deactivate, I be willing to go that route.
In regards to watching others use SSP, it is frustrating for me. I am one of those get it done quickly types, so waiting for someone to make 5+ mouse click to do the same thing that a single right-click will do drives me nuts.
I guess I should watch with a different attitude the next time I train someone. It would more than likely be a good thing for me to see how others percieve the interface. This might give me insights into better ways to train others.