Certainty in decision making with our Aligning Business and IT -offering

The notion that everything affects everything is not wrong. On the contrary. Everything should affect everything else, because the different parts of the IT landscape in a company integrate in the same manner business processes are interconnected. Investment decisions should be based on a thorough and complete plan, in which a goal for IT development has been set as well as smaller steps for reaching that goal have been defined.

Insight, not sloppy platitudes

To support your decision making, we deliver an outside expert's view on what should be done and in which order. Starting from the the business vision and strategic targets, on through business processes, information flows, systems and infrastructure, we give you concrete recommendations on inormation technlogy development areas for the next 5 years.

A personal approach and commitment

Critically important in this project is taking the point of view of all stakeholders into account. Only after that can decisions regading what will be done and in which order be made. This can be though of as a kind of development time out, where the situation is re-assessed and new plans are made.
Because we want everyone to be able to tell us their version of the truth, we use face to face interviews instead of generic web forms. Through the interviews we collect requirements from many different areas: business applications, information flows, platforms and user support. The focus areas can also be decided upon in the beginning of the project.
In order for this project to succeed, broad participation from different process areas and organizational levels is needed. The implementation of the project results is usually much easier if they are based not only on the management vision, but on the organizations needs as a whole.

End result

From the great number of requirements gathered, a finite number of "themes" or development areas are distilled. These themes are described in greater detail at the end of the project. The priorities and relationships of themes are evaluated and based on these the final development roadmap is drawn.
Briefly

  • You need to stop and get an overview of current and future needs.
  • You must listen to the whole organization and ponder the different angles for development needs
  • You need to create a roadmap for 3-5 years in order to know what should be done next year.