Working Together

Today’s information and computer technology can be immensely powerful, but unless an organisation is efficiently structured in the first place, it’s unlikely to have much more than a cosmetic effect. And that’s the worst reason there could ever be to make such an investment.

So one of the first things BabelFix will want do is to have a good long look at what you do and how you do it. And typically, a good deal of what we find will confirm that your organisation is unique and that it has a great number of individual strengths. There's nothing dramatically academic here - its more to do with common sense and having the experience and space to remain objective.

At the very least, this will make sure that we really understand your business, though it may immediately suggest areas in your infrastructure with potential for improvement.

There are even times when we'll suggest that there's no point in further retaining our services. We're here to provide honest help, not to get a free ride.

Understanding our clients' businesses inside out involves looking in detail at production and management practices, logistics and systemic infrastructure. But if our ideas can't be simply expressed in straightforward plain English, and if we can't come up with something intuitive enough that its users will already find it kind of familiar, then we'll be pretty disappointed. At BabelFix we don't actually do much systems analysis - at least not in the academic sense. We find that common sense tends to work for everybody without much need for formal theory.

And that invariably establishes the principles for a good design that solves real world problems robustly and which won't need a fighter pilot with a rocket scientist in the back to drive it. That's our job - devastatingly simple isn't it?

We believe in transparent simplicity and if we really do need to produce entity relationship diagrams we'll not worry our clients with them unless they ask. After all, it's our job to take care of all that stuff and we'll always try and do it without technobabble smokescreens. Actually, about the only time we do that data modelling and flow path thing is when something is just so complicated that breaking it down into a graphic diagram might really help us work out its systemic logic. But life's quite complicated enough without egghead notations.