Is it the name or the alias that matters?

imageBusiness people, not IT, make technology work to focus the business. The general IT role is more strategic to maintain and improve competitive positions of the business infrastructure to make people’s lives easier, It is not the other way around. Ask any CIO, he knows that. especially when he asks for a sign off on what is installed.

So why when changing a process do people go straight to IT to set up technical processes. When they do IT have no choice to do it their way, Then  they give things names that are either functional, relate to the software or are way too obscure?

There is no way this should happen in the public domain as things like product names and branded access URLs are always cleared by marketing. Then image and branding are so important. But internally that does not happen as all too IT often gets little business help or involvement.

It is like having two standards, one rule for customers and other those who service them. And that make no sense at all. Setting the service delivery culture starts with teaching people the supply chain in not about them but their suppliers and customers. So why do we still insist being too lazy to put some effort into more marketing rather than functional or geeky names.

To paraphrase from another well-known idiom.

If you feed them peanuts they will look like monkeys.

So why not give internal process the same respect you give your customers and suppliers so they will be more likely to perform and respond the way you expect. That of course needs a business person to own and manage the change process. And all too often they are missing or busy.

Most often too as learning is done in the development stage where the die is cast. “A habit of one” it is often called. When you show people something that continues to work for them they may never change even if it is improved the very next day. The process and a systems life is therefore limited by the language and thought we give it when it starts. Never mind people whom may struggle later once the initial support is gone.

http://Image076/ or some such useless ellipsis name embedded in key process URLs is unlikely to move your business forward. So why use language that you don’t understand or is not service related?

As for IT infrastructure and everything upwards it is vital for management to get involved. Once instances are set and business teams take over any plea to start where we want to end up is then forlorn and lost.  It is often too hard and too detailed for managements to consider, especially in the “lets get it done urgency” cultures to have something working and adding value yesterday. So it gets underway without good thought on the impact of a later change.

Using and understanding how to set names and use aliases in not an IT role, It is vital for business managers to break this nexus so the language of technology more natural to focus the business.

4 thoughts on “Is it the name or the alias that matters?

  1. @Buy Tramadol
    I looked up the answer

    A transfers money from his account to B’s account (another bank), A does this via his bank, his bank mistakenly takes sum of money twice from his account. A speaks to his account and they refund the money to him as well as compensation for the mistake. In the meanwhile B has received 2 payments from A. A is now asking for sum of money from B even though he has received money back from bank. What are the legal implications for B?

    One answer I like is this one:
    B has to pay back the money. He knew it was a mistake. He could be arrested for fraud and so could A

Leave a Reply