> 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/discovery/understand-as-is.md).

# Understand As-Is

#### Understand the Customer's AS-IS process

The first step is to understand the current process of strategy formulation and execution. Below are some relevant questions: 

1. Who is responsible for strategy formulation and execution? 
2. What is the time horizon of the strategy? Usually it is 3-5 years. 
3. How often is the operational plan prepared? Usually annually. 
4. What stakeholders are involved in the process and what is their role? 
5. How frequently is performance measurement reported? 
6. What is the organizational structure, including business units, roles, support functions, and product lines? 
7. What performance measurement methods are used? e.g. KPIs, SMART objectives, OKRs. 
8. What is the process for diagnosing the situation? 
9. How are strategic options identified, decisions made and documented? 
10. How are guidelines developed for execution teams? 
11. Is capability-based planning or capability maps used? 
12. What tools or techniques are used, e.g., SWOT, PESTLE, Strategy Lenses, RACI 
13. At what stage are information and technology architects involved in the process? 
14. Document the weaknesses of the above process. 
15. Some common problems are: 

    a. paper-based process,

    b. lack of framework, 

    c. lack of stakeholder involvement and collaboration, 

    d. incomplete documentation, 

    e. documentation is not shared with all stakeholders, 

    f. unclear issues, objectives, key results, and initiatives, 

    g. no diagnosis, 

    h. no strategic decisions, ​

    i. ad hoc decisions, 

    j. unclear guidelines for execution teams


---

# 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/discovery/understand-as-is.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.