We knew it was going to be a challenge… but when we laid out the objectives for VeSys 2.0, one of the key VeSys Classic traits we wanted to capture was the ease-of-use. Although there would be some things we just wouldn’t be able to address in the very first release, we worked hard to nail some of the basics:
1. The tool can be installed easily on a single machine in one go (no more AutoCAD install!)
2. All the services are automatically set-up for the user, they just click and go! Really, they shouldn't need to know they exist at all.
3. We provided a rich set of starter symbols and library parts all with simulation models attached and a project showing how they could be used
4. There’s a test drive AVI supplied that takes a user through a front-to-back-nothing-to-completed-harness-design process
5. Although we had added the power of users, we’d made it easy to create & edit them
All of this, we thought, would mean that you could download an evaluation copy and be happily experimenting with the tool in minutes, not hours. The proof of the pudding is in the tasting (is that a UK only phrase?), so we carefully watched beta-users… when we spotted them struggling we made changes. In short, we did everything you were supposed to do. We were very successful, the first wave of new users were up and running in minutes.
Can you feel the but coming?
We did get a lot right, but what’s to come really shows the a few misplaced assumptions can have a disproportionate impact on usability. What I’m going to do is go through 4 of the 5 things above (the Test Drive has been very well received, people just want more of them!) and illustrate what we got wrong (and what we are going to do about it).
The Easy Install
Lesson Learned: Sometimes it’s better to just give up
There is a technical issue that we found with the installer pertaining to Windows permissions and over-active security software, but that’s not the really interesting bit… There’s no way around it, if the user doesn’t have permission to install software, or to write to certain directory then they don’t and there’s nothing you can do about it. It’s not even that we crashed or just bombed out. The installer dutifully slogged on doing what it could. There’s the mistake… We should have just given up and told the user they didn’t have the right permissions. In this case, nothing is better than something (that didn't completely work).
Automatic Service Set-up
Lesson Learned: Too much information
You’ve run the installer, you are asked to reboot, you do. You log back in and go to the programs menu and the VeSys group… now… all of the services VeSys needs to run are up and running silently in the background just as they should. However, as we know some users don’t or can’t run services we have the capability to manually start and stop the services. We put the icons to do this (Start and Stop VeSys Manager) in the program group. Users are smart, they see the Start VeSys Manager icon and they think “I should run that before running VeSys”. They get an error saying it couldn’t start. Well it couldn’t. So the user thinks the install hasn’t worked, time to pick up the phone or send an e-mail to the sales guy or CSD.

What we should have done is leave those applications for the system admins to use, and not make them as visible to users. Everything was fine, and if the only icon they had had was “VeSys” they would have clicked that all would have been well.
Getting Started with Starter Data
Lesson Learned: The First Step is the Hardest
VeSys Classic, and perhaps more importantly AutoCAD, is a file based application. When you start it up you get a blank sheet. When you click save, it just has to ask you way to save the file. As long as you can see how to add a device and a wire, you are pretty much good to start exploring.

VeSys 2.0 opens up with an empty screen. What had become obvious to our beta testers; that you needed to click New Project, create a new design (more on that later) and then get going… turned out not to be obvious to those who hadn't just watched Nuri (the Product Manager for VeSys and the CHS Interactive Flow). All those users see is an empty screen. Then, if they do figure out they need to create new project (easy enough, one click and give it a name) they still have a blank sheet. We had left the New Design button in a context menu. Again, we and our beta testers had become blind to this. New users… got stuck. There are two perspectives on this… one is that you are only three mouse clicks and a couple of keystrokes away from getting stuck in… the other is that unless you know how to find the button.. it might as well be impossible.
Easy User Management
Lesson Learned: Even easier than do something… is doing nothing
I mentioned above that AutoCAD and VeSys Classic just drop you into a blank sheet. Off you go. Before the application even starts up, we ask for a user name and password.

That’s fine, in fact it’s a real benefits of the tool, controlling which users have permissions to do which things (see Correct by Constriction). Except that if you are evaluating the software what you really want to do is just click on the application and get stuck in, rather than being challenged to prove you are worthy to connect. Again, the system admins may want to get things set-up, but evaluators or a one-man design consultancy just would rather we didn’t ask.
So what are we going to do about it?
In the end, none of these problems have not been solved over a quick conversation, and in-fact early tool users didn't see them as important enough to report to us, it took over a month before I happened to be in a meeting where a user half mentioned the problems. However, we really don't believe that these kinds of issues match our design brief, so we are going to fix them. Sadly they came a little too late to make it into the first Service Pack, but we are going to resolve them immediately afterwards (some of the work is already done). I'll make sure I keep you the readers up to date on exactly when and how we will be delivering the changes, but we are not going to sit on them for a minute longer than we need to.