Island Web Works

You may recall we’ve been working on improving the speed of MIGTurbo 2.0 further by making various optimisations in the call to the server and its response to the client (your web browser). Having set the precedent and the model to use, this work continues.

Our new Security Editor for MIGTurbo 2.0 builds on our existing security mechanism in MIGTurbo 1.8 and 1.9 by introducing Roles and Rules. Without going into too much detail at this stage, this will provide users with an elegant and flexible solution for securing their system, whether they prefer MIGTurbo “locked down” or with more liberal access. The customer decides, not the software.

It’s important we get the user interface for this right, as it is a new concept and we need to be sure that users can jump on board with the new flexibility this offers. If you’ve used Windows file permissions, you’ll quickly become au fait with the new interface. 

Using the same technique, by using AJAX and web services to circumvent the traditional web page processing pipeline, interaction times were cut again. In fact, moving rules up and down the list occured so fast you couldn’t be sure if it had actually happened. Using AJAX means that we can update the page seamlessly, so can change small elements of the page with no-one but the most eagle-eyed users noticing. Using web services, we can do it faster. 

This presented us with a problem. We actually needed to slow down the interface to provide the user the reassurance that something had actually happened. We’ve come up with a nice visual cue that takes 0.5 seconds to run through, but gives the user the confidence that something has actually occured.

Take a look at the first screenshot from MIGTurbo 2.0, albeit a very small one (we don’t want to give too much away just yet!)

I’ve just clicked the “Up” button to move the UserAdministration rule above the rule above it (thereby allowing UserAdministration members to perform this particular action). Instead of simple redrawing the rules, the rule “fades out” and then redraws. This gives a small and simple visual cue that something is happening. 

Another effect we’re working on is when deleting rules. In the same example, if I was to delete the rule by clicking the Delete icon, the rule is turned red, then faded out. This gives the impression that the rule has been “blown up”. Another simple cue that confirms something has happened without requiring any interaction or confirmation by the user.

We hope to add more of these interstitials to reinforce the actions that the user is performing within MIGTurbo 2.0. They don’t just provide a key aspect of a user experience, though, they also make the use of the product a little bit more fun (but don’t “blow up” too many things)!

Nathan MIGTurbo MIGTurbo 2.0, User Experience (UX)

Following on from Nathan’s last post, the question that springs to mind is Why Bother! The reason, in a single word is ‘Confidence’, if you lose the clients confidence you have lost the war. Regardless of the label you assign a business like ours, we develop software. Business software, productivity software, CRM software, the label is secondary to the fact we build software solutions, and part of the solution is a product that works. If a product is slow and laboured, it may be the most functional, secure, useable product on the market, however, all you will hear from users is ‘it’s slow’.  And they would be right!  Clients need to be confident that the investment they have made actually improves productivity and slow systems don’t tend to inspire that confidence.

The largest cost to most businesses today is labour and a slow network, PC, or software application is costing you money, every single hour of each and every day it is in use.

If a computer operator regularly waits for their PC to process instructions, you could easily be losing 20 - 50% (or more) productivity per staff member. This means that in order to support a 50% growth in business you will need to either increase staff by 50% or increase productivity by 50%, and one of the simplest ways of improving productivity is to use the correct tools for the job.

When it comes to Business productivity - faster is usually better!

Charles MIGTurbo User Experience (UX)

It’s been a tough couple of days on the MIGTurbo CRM 2.0 project. I’ve been working on the code to Display and Edit Client Details. It’s nothing spectacularly complex or detailed, of course, but there was a niggling issue that was bugging me.

MIGTurbo 1.8 /1.9 is fast, very fast. So in writing next-generation code to replicate the functionality and speed users are used to, we need to make sure that we can maintain a similar level of user expectation. As with the commitment to maintain the User Experience in terms of user-interface, we also need to make sure users’ expectations of speed is maintained.

Traditionally, when editing a record on a web application, there is the inherent cost of applying the changes to the server, retrieving the latest details and updating the user interface. All quite costly. In the slowest tests performed in the last couple of days, this was taking up to 5 seconds. A lot of debug code, and support resources are involved here and this does not represents a “real-world” scenario, but even 2-3 seconds will give a feeling of “lag”.

Improving the speed of this was very important, and if we could do it using the same foundations we’re implementing for improving extensibility, then all the better. So, armed with acronyms and search terms, I set upon resolving the speed issue and tweaking the code to extract every bit of performance possible. Effectively, this has taken 2 days … to gain 4 seconds of performance. Now, a typical round trip takes less than half a second (in rough tests).

Was it worth it? Of course it was. Those 4 seconds, multipled by all our clients, multiplied by the number of times a user performs that single function and you get a significant time difference that exceeds 2 days. What would have taken a round trip of approximately 30Kb (even using AJAX - albeit ASP.NET AJAX) now takes a round trip of less than 200 bytes in a typical scenario. That’s a lot of bandwidth given back to the network and it all goes to ensuring MIGTurbo 2.0 remains an enterprise class CRM.

Just in time for the live streaming of The Gu’s Keynote at MIX09 and all without a Diet Coke, too.

Nathan MIGTurbo MIGTurbo 1.9, MIGTurbo 2.0, User Experience (UX)

The last couple of weeks we’ve been using the beta version of MIGTurbo 1.9  in the office - trying out new features and hunting down bugs. 

I always find it interesting to see a product go from development to a ‘live’ test environment and with this release it’s been no different.  After a few days testing we had a rather substantial list of (albeit minor) bugs to go through.  In addition to the typical ‘but why would anyone do that?’-bugs, there were also a good few interesting suggestions on how to improve the user interface. 

With version 1.9 we’re trying to both move MIGTurbo forward with some exciting new features whilst at the same time keep all the existing users happy with the familiar environment they said they liked.  In fact, with the default settings you’d be hard pushed to see any immediate changes at all.  Sure, the branding has changed slightly, and there are a few minor layout differences, but in essence it’s still good old MIGTurbo!

Regarding the new features, I think the one that will excite people most will be the customisable tab layout.  In 1.9 every user can have their own personalised layout, giving the administrator the option to optimise MIGTurbo for different types of work tasks.  Another great new feature is the Firefox browser support.  Until now MIGTurbo has always been a Microsoft-centric software, and although that’s still true ‘under the hood’ we are now inviting non-Windows users for the first time - great news for Apple fans!

We’ve now swatted all known bugs but will keep running it in beta for the next week just to be sure. If all goes well we are aiming to go gold on Friday 13th!

Andreas MIGTurbo, Uncategorized MIGTurbo 1.9

Charles recently blogged about the challenges around making improvements to established products and designs. MIGTurbo is a successful CRM package and is evangelised and valued by its users. One of the reasons behind this, we believe, is the supremely simple and quick user interface. We are currently internally testing the next version, MIGTurbo 1.9, and this has a number of exciting new features which will further enhance the user experience - or ‘UX‘ to its friends.

So when moving towards the next major milestone in the MIGTurbo roadmap, MIGTurbo 2.0, it presents a challenge to us. While we are looking forward to being able to provide more features and better performance with a contemporary design, we must balance that with what we know has made the product such a success up until now … and that is the simplicity of the user-experience.

One thing I have really appreciated since joining Island Web Works is the opportunity for frank discussions about everything from the fundamentals of the Microsoft SQL Server Paging mechanism to the finer details of Natural Selection. These discussions have allowed me to come into the business as a new member of the team and also as a new and fresh user of the MIGTurbo application while still being able to contribute my opinions and outlandish statements without fear of tarnishing any egos. So when looking at what form the user experience of the 2.0 release should take, a full and frank discussion could be had. 

We quickly identified and agreed that we did not want to repeat Microsoft’s mistake with the Office 2007 user interface. Previous users of Office 2003 were able to use their years of experience using the world’s most popular office suite to create and manage their documents, spreadsheets and presentations with relative ease. Ever since Word 6.0, the user interface has been more or less consistent even as new features were added. Then, in 2007, Microsoft redesigned the entire user interface of the Word, Excel, Access and Powerpoint products to use ‘Ribbons’. Sure, the Ribbons are beautiful, and I happen to prefer them, but most users just want to get the job done and when functions not only move but appear to disappear altogether, user unrest is sure to follow. So despite extensive usability testing and user experience workflow modelling when coming up with the Ribbon Experience, users are still rejecting the user interface due to requirements of loss of productivity and requirement of re-training staff. While we need to maintain a consistent experience with previous versions, one of the key components of the MIGTurbo 2.0 roadmap is extensibility, so we equally didn’t want to restrict any opportunities in the future. We need to be able to provide extra functionality, in new places, but not disturb the central usage workflow.

Our challenge is how to maintain a consistent user experience for those users who have used the product for years, while providing visible opportunities to help them get more out of their usage of the product - but at the user’s own pace. We are working on an experience which will mirror our existing UI design and associated benefits, but will also hint at opportunities to help users focus on the job in hand. One key example I use is a month-end procedure. We want to be able to facilitate everyday use whilst accommodating specialised use, so provide the regular “everyday view” but give enough cues to help the user realise that they can extend their view on the system to perform specialised procedures even easier than before. This did not happen with Office 2007.

After the discussions we have had both today and previously, I believe we have come up with a sensible compromise. We will be maintaining the experience as much as possible for users who are already used to the system by ensuring functions and data are where they always were. There won’t be any disappearing or moved functions, but there will be additional opportunities to get more from the user experience. We will achieve this by mirroring established design patterns that have proved to work. By adopting patterns such as the Task Bar, Breadcrumbs and Menu patterns along with Web 2.0 practices, we can benefit from existing user experience. When a new user uses the new MIGTurbo for the first time, they will already know how to use the menus, how to navigate between screens and why the application feels the way it does because they will have already used the techniques in other applications. When an existing user uses MIGTurbo 2.0, they’ll have a strong degree of familiarity based on their previous experience.

It’s too early to show screenshots as the UI framework that will hold the functionality, data and plug-ins together is still very much in flux. However, we are looking forward to involving users in the latter stages of the development of the user experience to further build on our impressions and experience using MIGTurbo and seeing other users use it, both the user and the seasoned expert. This will provide us with a valuable opportunity to see user reactions at first hand and give users a valuable opportunity to further influence the design of a product many users spend all of their office day with.

Nathan MIGTurbo MIGTurbo 1.9, MIGTurbo 2.0, Office 2007, User Experience (UX)

(… not like I’d know of course)

Over the past few months I have been working on what was my first project involved with the MIGTurbo CRM application, the Microsoft Outlook Toolbar.

The toolbar provides access to client/contact records within MIGTurbo along with access to some of the MIGTurbo plug-ins, such as DocuMentor for attaching documents stored within MIGTurbo and TimeTracker allocating correspondence to projects. The new toolbar is built around our new MIGTurbo API, which will form the basis of MIGTurbo 2.0 and will be released later in the year.

We’ve been listening to our client’s feedback about the previous versions of the toolbar and think we have matched their expectations for reliability and performance. Although I do not agree with releasing “Beta” software out to users without a level of technical awareness, testing was going to be essential. Therefore, for the last month or so, we’ve been deploying our pretentiously titled ‘Elective Sunrise Edition’ to try and give some clients a preview of the toolbar and try to spot any issues that we wouldn’t spot until it was released “into the wild”. The response to the toolbar has been very positive and we’re pleased to say we’ve released the toolbar officially and will be installing it in the next few months.

As the developer of the toolbar, it’s a mixed time for me. I’m pleased to see it reach “Gold” status (to attach an equally pretentious title), but I’m touched by a sense of nervousness about how well it will perform in the “real world”. We’re confident in it though, having tested it in some differing networks with their own challenges (security policy, topology, organisational etc.). Although I have no idea what it would be like, I do get the sense it would be like seeing your first-born start school for the first time!

Nathan MIGTurbo DocuMentor, Outlook, TimeTracker