Technology gives us immense access to the modern world.
But it comes at the cost of complexity, and we rely on modern enterprise systems to manage that complexity for us.
We want to focus on our top-level concerns - the collection and management of our enterprise information - and trust that the system underneath will take care of the details.
That it will store and safeguard our data, giving access to only those who are permitted; and prevent inaccurate or duplicate information from being acted on.
That it will exchange messages and interact reliably with other systems on our behalf; and report back to us if it encounters problems.
And above all, that it will be a comfortable and productive platform for collaboration, that allows us to get the very best achievements from our valuable human resources.
But there is danger here. Technology, and our business processes, are constantly changing.
A successful enterprise system must anticipate not only the turnover of its own platforms, but also the constant evolution and expansion of its human, legal and business operating environment.
Too often, the mechanics "under the bonnet" of a system have been thrown together to meet the original brief, but without any attention to building a flexible architecture that can adapt to changing business rules and technologies.
These systems quickly become brittle, and cannot be safely altered, for fear of disruption to operations, or of loss or exposure of data. Loathed alike by those who use them, and by management who must devise ways to work around their faults and limitations.
Eventually, they incur such intolerable cost in lost time and opportunity that they have to be abandoned and replaced with something else, in a final ordeal of turmoil and waste.
As we all know, the outward appearance of something is often very different from what lies within. This is often the case with cloud systems and other software, because their internal structures are likewise much less visible than their user interfaces.
So how can we identify a system that is blessed with a flexible architecture? There are many signs, but these are a few to look out for:
Flexible design philosophy covers all aspects of a system, making it comfortable to manage and seamless to use. Some aspects also manifest visibly, in ways that may not at first be obvious.
Flexible cloud systems have adaptive stylesheets that arrange the page layout in different ways, depending on the size of the screen. This is known as responsive design, and makes them work equally well on either desktop or mobile browsers.
Web pages should also print neatly, which may need separate styling. You must have experienced how often this is overlooked, with sites where all attention has been paid to the screen appearance, but where they preview as an unprintable mess, making them impossible to capture on paper.
At Flexis, we take all aspects of flexible design seriously, and our design of this site is a good example.
If you are using a desktop browser, make the window narrow to see how the page resizes for different resolutions and reflows for a narrow mobile screen. Use Print Preview to see how the content and text wrapping adapts perfectly for the printed page.