> For the complete documentation index, see [llms.txt](https://innowayit-1.gitbook.io/framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://innowayit-1.gitbook.io/framework/use-cases/it-strategy.md).

# IT Strategy

> IT Strategy is "is a comprehensive plan that defines how technology should be utilized to meet IT and business goals. It is a blueprint of how technology can support your overall business strategy. It encompasses all facets of technology management, including cost, hardware and software management, vendor management, and risk management."

> Essentially, the IT Strategy is the roadmap a business follows to achieve their IT goals. 

| Sponsor            | Scope       | Stakeholders                                               |
| ------------------ | ----------- | ---------------------------------------------------------- |
| COO/CIO/Head of IT | IT Function | <p>IT executives and managers<br>Business stakeholders</p> |

#### Sponsors' Concerns

1. IT simplification&#x20;
2. [Application rationalisation ](/framework/use-cases/application-rationalization.md)
3. IT modernisation&#x20;
4. IT governance&#x20;
5. Skills and resources&#x20;
6. Partnership with service providers&#x20;
7. IT operating model&#x20;
8. Management of technical debt
9. Agile vs. waterfall

### FORMULATION

<details>

<summary>PLAN</summary>

Discuss with the team leader, sponsor or CIO what the importance of having an IT Strategy is. Capture their views and opinions in order to make a comprehensive IT Strategy.&#x20;

</details>

<details>

<summary>ENGAGE</summary>

Invite stakeholders and discuss the importance of a concrete IT Strategy and the advantages it has on the organisation. Listen to their opinions, concerns and recommendations.&#x20;

</details>

<details>

<summary>DIAGNOSE</summary>

Deep dive into stakeholders' concerns and ideas and filter out the ones with the highest impact on the organisation. Which ones take precedence over the rest?&#x20;

</details>

<details>

<summary>DECIDE</summary>

Create a list or table of concerns and ideas and determine which ones are the most important. This will help with the decision/solution process.

</details>

<details>

<summary>GUIDE</summary>

After a decision(s) is made, a guiding policy is created.&#x20;

</details>

<details>

<summary>DEFINE OKR</summary>

Define the objectives and key results of the strategy. What do you want the IT strategy to achieve?

</details>

### EXECUTION

<details>

<summary>ACT</summary>

</details>

<details>

<summary>REPORT</summary>

</details>

<details>

<summary>RETROSPECT</summary>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://innowayit-1.gitbook.io/framework/use-cases/it-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.