Our tech expert Tim Stackpool shares the techniques that software developers use to avoid ‘feature overload’ and suggests how EAs can identify when there is too much tech in their day.
There is no chance of avoiding technology at work and in this era, with artificial technology progressing at a rapid rate, we are now confronted with even more. While this generates much excitement and future possibilities, there remains the pitfall of being swamped to the point of becoming less efficient by trying to implement ‘too much tech’.
Help or hindrance?
In simple terms it is easy to understand how significant investment in technology, without ongoing funding to keep that technology up-to-date, can eventually be a hindrance. There is also the danger in the workplace of something called techno-complexity, where you are required to upskill merely because the same job has become complicated due to the introduction of new technology. This can be extremely stressful and can create feelings of inadequacy, despair and apathy amongst users.
To remain relevant, software developers can ask themselves three general questions when creating new applications for the office:
- Does this add value?
- Is it practical?
- Is it necessary?
If the answer to any of those questions is no it is likely the software or equipment will miss the mark, cause frustration and be less productive if ever deployed.
Feature fatigue
Adding too many features to software can convolute the actual use too, and force the user to dig deeper to find what they need. An app to check-in to a flight is convenient but adding car hire, weather at the destination, packing advice, duty free offers and diary reminders easily distracts from the core function. If you find yourself scrolling back and forth through an app trying to find what you need or sighing over the number of clicks needed to achieve what you want, it is a sign of development reaching too far.
The same can be said of desktop applications, such as marketing EDM or CRM tools. Many of these have extensive features, demanded by users across many years and versions. But to avoid feature-overload, developers often break the features into modules. This can make the application more manageable – but it can appear unwieldy if the developer ‘assumes knowledge’. This is when new features are added but only appear efficient if the user has extensive knowledge of the software from previous experience.
Time to go cold turkey?
Technology overload can also manifest quietly, leading to anxiety at just the thought of launching a software application or being paralysed by trying to decide which piece of software to choose for a particular job. While you might not be in a position to make changes within your own organisation regarding the number and type of software used, you can consider your own tech detox to better manage the effect of digital overload.
Smartphones are pretty much essential in life these days, so going cold turkey is impractical. Instead:
- Consider reducing the number of notifications you receive during work time. You will generally find the controls for this under ‘Settings’.
- If you can, on your workstation, clear the desktop of non-essential items. Leave shortcuts to folders that you access most often, and your favourite Office products but remove everything else.
- Find alternatives to occupy yourself if you are waiting for a meeting or appointment. Instead of scrolling through your phone to avoid boredom, reach for a book or a magazine, or doodle with a pencil.
These are really small changes to make but can be considered part of a ‘digital diet’ to reduce the sensation of tech overload, particularly during stressful situations that might require hours of pounding the keyboard to get the job done on time.
