DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | ● 0 skipped | | format
apiVersion: soultec.ch/v1kind: Servicemetadata: name: it-strategie locale: en labels: group: consulting capability/strategy: 3.54 capability/architecture: 2.93 annotations: source: src/content/services/en/it-strategie.md route: /en/services/it-strategie/ schema: /nerd/schema/services.json markdown: /en/services/it-strategie.mdspec: 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 sections: - heading:

Why this is not a technology question

 body: | 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. - heading:

What we work out together

 body: | 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. - heading:

How it runs

 body: | With you and your team, not for them. A strategy written from outside reliably describes an organisation that does not exist.status: corpus: 267 solutions: - {ref: solutions/hpe/hpe-server, score: 0.41} - {ref: solutions/ibm, score: 0.41} - {ref: solutions/ibm/ibm-power10, score: 0.41} alsoLike: - {ref: services/enterprise-architecture, score: 1.00} - {ref: services/requirements-engineering, score: 1.00} - {ref: posts/vmware-license-changes-2025, score: 0.53}
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "it-strategie", "locale": "en", "labels": { "group": "consulting", "capability/strategy": "3.54", "capability/architecture": "2.93" }, "annotations": { "source": "src/content/services/en/it-strategie.md", "route": "/en/services/it-strategie/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/it-strategie.md" } }, "spec": { "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 }, "sections": [ { "heading": "

Why this is not a technology question

", "body": "How people want to consume a service today, and the speed at which departments need to get\nto market, feed straight back into how the IT department is staffed and organised. A\nstrategy that only describes technology answers half the question." }, { "heading": "

What we work out together

", "body": "The future operating model: who delivers what, what gets bought in, which capabilities have\nto exist internally and which do not. That is the decision the architecture follows from,\nrather than the other way round." }, { "heading": "

How it runs

", "body": "With you and your team, not for them. A strategy written from outside reliably describes an\norganisation that does not exist." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.41" }, { "ref": "solutions/ibm", "score": "0.41" }, { "ref": "solutions/ibm/ibm-power10", "score": "0.41" } ], "alsoLike": [ { "ref": "services/enterprise-architecture", "score": "1.00" }, { "ref": "services/requirements-engineering", "score": "1.00" }, { "ref": "posts/vmware-license-changes-2025", "score": "0.53" } ] }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "it-strategie"locale = "en"[metadata.labels]group = "consulting""capability/strategy" = "3.54""capability/architecture" = "2.93"[metadata.annotations]source = "src/content/services/en/it-strategie.md"route = "/en/services/it-strategie/"schema = "/nerd/schema/services.json"markdown = "/en/services/it-strategie.md"[spec]title = "IT Strategy"group = "consulting"order = 4tags = ["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 = falsedraft = false[[sections]]heading = "

Why this is not a technology question

"body = '''How people want to consume a service today, and the speed at which departments need to getto market, feed straight back into how the IT department is staffed and organised. Astrategy that only describes technology answers half the question.'''[[sections]]heading = "

What we work out together

"body = '''The future operating model: who delivers what, what gets bought in, which capabilities haveto exist internally and which do not. That is the decision the architecture follows from,rather than the other way round.'''[[sections]]heading = "

How it runs

"body = '''With you and your team, not for them. A strategy written from outside reliably describes anorganisation that does not exist.'''[status]corpus = 267[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.41"[[status.solutions]]ref = "solutions/ibm"score = "0.41"[[status.solutions]]ref = "solutions/ibm/ibm-power10"score = "0.41"[[status.alsoLike]]ref = "services/enterprise-architecture"score = "1.00"[[status.alsoLike]]ref = "services/requirements-engineering"score = "1.00"[[status.alsoLike]]ref = "posts/vmware-license-changes-2025"score = "0.53"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>it-strategie</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/strategy">3.54</entry> <entry key="capability/architecture">2.93</entry> </labels> <annotations> <source>src/content/services/en/it-strategie.md</source> <route>/en/services/it-strategie/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/it-strategie.md</markdown> </annotations> </metadata> <spec> <title>IT Strategy</title> <group>consulting</group> <order>4</order> <tags> <item>strategy</item> <item>architecture</item> </tags> <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.</summary> <photo>presenting</photo> <photoNeed>A strategy session: someone presenting to a room, slide visible</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <sections> <section> <heading>

Why this is not a technology question

</heading> <body>How people want to consume a service today, and the speed at which departments need to getto market, feed straight back into how the IT department is staffed and organised. Astrategy that only describes technology answers half the question. </body> </section> <section> <heading>

What we work out together

</heading> <body>The future operating model: who delivers what, what gets bought in, which capabilities haveto exist internally and which do not. That is the decision the architecture follows from,rather than the other way round. </body> </section> <section> <heading>

How it runs

</heading> <body>With you and your team, not for them. A strategy written from outside reliably describes anorganisation that does not exist. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.41</score> </item> <item> <ref>solutions/ibm</ref> <score>0.41</score> </item> <item> <ref>solutions/ibm/ibm-power10</ref> <score>0.41</score> </item> </solutions> <alsoLike> <item> <ref>services/enterprise-architecture</ref> <score>1.00</score> </item> <item> <ref>services/requirements-engineering</ref> <score>1.00</score> </item> <item> <ref>posts/vmware-license-changes-2025</ref> <score>0.53</score> </item> </alsoLike> </status></manifest>
Service · consulting

IT Strategy

How users want to consume a service, and how fast the business has to deliver, shape what the IT department needs to look like.

Topics Strategy 3.54 Architecture 2.93
03Solutions
02Capabilities
267Corpus
Presenting to a room from a slide deck

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.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically.

Maybe you? Take a look at our open roles.

You might also like

service 1.00

Enterprise Architecture

service 1.00

Requirements Engineering

post 0.53

VMware by Broadcom – License Changes