---
# source: src/content/services/en/it-strategie.md
# route:  /en/services/it-strategie/
title: IT Strategy
group: consulting
order: 4
tags: [strategy, architecture]
summary: How users want to consume a service, and how fast the business has to deliver, shape what the IT department needs to look like.
photo: presenting
photoNeed: "A strategy session: someone presenting to a room, slide visible"
stub: false
draft: false
---

## Why this is not a technology question

How people want to consume a service today, and the speed at which departments need to get
to market, feed straight back into how the IT department is staffed and organised. A
strategy that only describes technology answers half the question.

## What we work out together

The future operating model: who delivers what, what gets bought in, which capabilities have
to exist internally and which do not. That is the decision the architecture follows from,
rather than the other way round.

## How it runs

With you and your team, not for them. A strategy written from outside reliably describes an
organisation that does not exist.