Spoiler alert: there is little or no consideration for the end user.
In many IT projects that we encounter, we see that the emphasis is on technology. And I am not talking about activities that simply have to be done in the context of, for example, cyber security. But think of a technical migration, replacement of an application or the introduction of something completely new.
Doomed to fail
This emphasis on technology is literally noticeable in the type of people (or rather: the type of knowledge) that join these types of projects. From the supplier's perspective, these are roles such as architects or functional specialists. In any case, people who think very well from their own product and do that well. On the client's side, these are often the IT people and the business is not or hardly present. The end goal of the project is the technical implementation. On a given date, it works, the SLA comes into effect and then there is cake.
But what was the actual goal of this project? Who would benefit from it? And what would it yield? Is that measured? Have users actually been asked what they encounter in their daily work? Because if that is not the case, the project is ultimately doomed to fail. Despite the cake at the end of the implementation.
In the majority of all ICT projects you see that:
almost entirely focuses on implementing (read: kuwait telegram data turning on) technology
does not think enough about what the (desired) effect is and for whom
pays too little attention to the preconditions for success
How should it be done then?
In the 15 years that I have been able to work on large IT and change projects, there is one constant factor for success: do not forget the people. You have to think about the different aspects of the project and ask yourself what the preconditions are for long-term success and what steps you need to take for that. This involves things like:
Ownership: has it been clearly agreed who is responsible, what the budget is and, above all, what the outcome should be?
Coherence: has any thought been given to the coherence between this project and all other digitalisation issues that exist?
Change/adoption: it is useful to define one change approach instead of starting from scratch for each IT project (assuming that most organizations are far from finished with change/digitalization).
Content: is there a clear plan about the type of content, form, management, etc.? It's great that there is a tool, but without management of content it's asking for trouble.
