Phase 1

IT Strategy and Steering

By Redaktion techport.ai, IT-Beratung · Last updated on 21 August 2026

Most IT decisions in mid-sized companies are made under time pressure and one at a time. A system reaches end of life, a department pushes, a vendor makes an offer. Each decision is defensible on its own, and the sum is a landscape nobody would have designed. Steering does not mean producing more paper. It means answering a few questions early enough that all the individual decisions afterwards become faster and better.

In this field we clarify what IT should deliver for the business, what it costs, who decides and in which order the work happens. That is the basis for everything in the other seven fields.

Typical problems

There is a list of projects but no order that anyone can justify.
IT costs appear as one line in the accounts and cannot be attributed to any area.
Management sees IT as a cost centre, IT sees management as a brake.
There are expectations around AI, pilots in three departments and no rule about who approves what.
External providers have accumulated over the years, contracts renew automatically, and nobody reviews performance.

What we do in this field

We develop an IT strategy with you that is derived from business goals and translated into concrete initiatives with effort and sequence. We make IT costs transparent and attribute them to the areas that cause them. We clarify roles and decision paths so it is clear who decides what. We build a project portfolio that weighs capacity against benefit. And we help with the question of what you do yourselves and what you buy, including how you steer your providers.

Topics in this field

Focus topicPutting AI to workHow AI delivers value instead of prototypes: assess use cases by value and risk, check the data basis, define approval and rules, and make results measurable.IT costs and value contributionWhat your IT really costs and what for: make cost blocks visible, attribute effort to the areas that cause it, separate run from change, and evidence the contribution IT makes.IT organisation and rolesWho decides what in IT: define roles and responsibilities, reduce dependence on individuals, and organise the work with departments and external providers.Focus topicDeveloping an IT strategyHow business goals become an IT strategy that departments understand and management supports: target picture, fields of action, sequence, effort and measurable results.Prioritising IT projectsHow a wish list becomes a portfolio: assess initiatives by benefit, effort and risk, plan capacity realistically, recognise dependencies and justify decisions.Steering IT providersWhat you do yourselves and what you buy: make the sourcing decision, steer managed services, measure performance, limit dependency and negotiate contracts that hold at the exit.

Häufige Fragen

Does a mid-sized company really need an IT strategy?

You do not need an eighty page strategy document. You need a written answer to four questions: what IT should deliver for the business over the next three years, which systems carry that, what you do yourselves, and how you measure whether it works. That fits on a few pages and saves time in every project that follows.

Who should own the IT strategy when there is no CIO?

Management, supported professionally by IT leadership and the key departments. If IT writes the strategy alone it becomes technical. If the business writes it alone it becomes unrealistic. In companies without their own IT leadership we take this role for the duration of the project and hand it over afterwards.

Let us talk about your situation

In a thirty minute first call we work out where your biggest lever sits and whether we are the right people for it.

Arrange an initial call Our consulting