> 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/workflows/manage-strategy-tree.md).

# Manage Strategy Tree

### Purpose

To manage the strategy tree of the organization and view key information related to every strategy 

### Performed By

* Lead Facilitator

### Steps

1. Navigate to Strategy Tree ![](/files/cBQl8sGnIUzLRaFnJWzA)
2. When you first create a strategy tree, there are no strategies in the tree yet. Click the +Add button to create the corporate strategy which is the level 1 strategy. Subsequently, all strategies are managed as follows.
3. Click on the ellipsis at the top right corner of any strategy to add a child or edit the strategy ![](/files/ELGvnA3GttVCgXfKywmh). Child strategies can be created only for level 1 and level 2 strategies. 
4. Add strategy by clicking Add Child or edit the strategy by clicking Edit. 
5. Enter or edit the information of the strategy, e.g. name, the scope of the strategy, description, strategy cadence etc. 
6. Click Save

{% hint style="info" %}
The strategy tree has three levels. The top-level of the strategy tree sets the guardrails for all other strategies of the organization. 
{% endhint %}


---

# 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/workflows/manage-strategy-tree.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.