On Corporate IT–All That Is Bad
I’m a volunteer firefighter here in New Zealand. As well as doing all the operational firefighting stuff, I have some responsibility for administration within the brigade and externally. As part of this role I have to utilize Fire Service systems and email. Which is where the trouble begins.
Being an independent in my work-life, I have the luxury of choosing the systems I want to use. I’m pretty wedded to Google apps and having an Android device means that my email, my documents and my social engagement occurs seamlessly between devices. I use social systems extensively and dabble with point applications as and when necessary. All of which means that my life exists in a bunch of different places. It was about a decade ago that I finally gave up the idea of a portal being a viable gateway to all that I want to do. Unfortunately corporate IT hasn’t quite got that far. Below is a screen capture of the eye-wateringly bad UI that the Fire Service presents to me as an internal user. This UI is accessible from a PC at the fire station that has a locked-down DSL connection and only connects via Citrix. This same lock-down ensures that I have zero ability to actually have anything useful on the PC – Google chrome? No way. Even the latest version of Internet Explorer? Nope. Luckily I am allowed to access the portal via a standalone machine without Citrix. Feast your eyes on this;
Anyone remembering Yahoo in about 1998? At least they had the sense to introduce an “alternative menu” which removes some (but not all) of the eye bleeding components. But with this UI, not only does the UI get screwed up by my choice of browser (in Chrome the search box is unusable while many of the iFrames are inoperative), but the general layout in so mind numbingly bad that it literally makes me reluctant to interact with the system. But wait. It gets worse.
In an attempt to ensure consistency and transparency across it’s widespread organization, the Fire Service has rolled out a tool called Station Management System that is supposed to be the central hub for regular station interaction and scheduling. One of the tools within SMS is the OSM or Operational Status Management tool which ensures all members are competently trained and ongoing revalidation of core competencies occurs. OSM produces a detailed report of what skills are current and need corrective action (see below).
To which one would expect updating an overdue skill would be as simple as performing the training, clicking on the particular task and updating it to show currency. Alas not, to update a simple skill like (for example) the use of fire extinguishers, someone needs to manually create a specific task from an extensive list of pre (and often ill) defined tasks, add it to the station calendar, and then manually mark that task as complete. An incredibly time consuming and labor intensive process that is unnecessary, unfriendly and ultimately discourages use of the system
It’s a specific example, but more generally it shows just how little enterprise IT folks really think about the reality for their users. Instead of tools that allow users to do what they need to do as quickly and intuitively as possible, they seem to delight in creating barriers that stand between an actual activity, and compliance around particular systems.
The last word in all this goes to a fellow firefighter who made the following comment;
This entry was posted in Business and tagged Firefighter, google, google chrome, New Zealand, sms. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Post a comment or leave a trackback: Trackback URL.
..it seems to me we’d have been far better off sticking with the old clunky system rather than cheerfully giving whomever X-million dollars to give us a shiny-new-whiz-bang (ooooh! Silverlight!) clunky system. Woulda coulda shoulda. Guess that’s why I’m ops mgr for a fairly small network provider rather than CEO for a big national. I just don’t have the vision it takes to blow stupid large amounts of money on crap IT.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)