> For the complete documentation index, see [llms.txt](https://docs.7ft10.com/flow-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.7ft10.com/flow-system/change-management-3c-change-model/conduct/plan.md).

# Plan

The **Plan Phase** is a critical step in the change process where you establish the groundwork for your experiment. Initially, you will base your approach on assumptions regarding the change, but this phase emphasises the importance of validating those assumptions by consulting with individuals who will be impacted. Setting a clear **Due Date** for implementation creates accountability and ensures everyone stays focused on achieving the objectives.

Utilising **checklists** can simplify the planning process, helping to ensure that all necessary tasks are accounted for. Developing a more comprehensive implementation plan for high-risk changes is crucial, and it may require input from various stakeholders to capture a broader perspective.

This phase involves logistical planning, as well as leading and energising the team. A thorough assessment of the change's impact and complexity is essential to creating a strategy that maximises the likelihood of success.

**Activities**

1. **Change Impact Analysis**: This activity examines how the change will affect different groups within the organisation. By quantifying the potential impacts on stakeholders, you can effectively inform necessary change management actions.
2. **Change Complexity Analysis**: This assessment provides an overview of the change's nature and scope. It considers both the scale of the initiative and the organisation's capacity to absorb the change, especially to past experiences.
3. **Change Activities Assessment**: To fully understand the implications of the change, it's important to evaluate its effects on people, processes, and technology. This assessment helps identify the complexity of the change and determine the tools and documentation needed for a smooth transition.
4. **Change Activities Matrix**: This matrix serves as a guide for prioritising key activities based on their individual impact and complexity ratings, facilitating a more strategic approach to change management.
5. **Change Management Canvas**: This tool engages stakeholders in discussions about the change, clarifying key messages and facilitating change management strategies. It captures important information to inform stakeholder management and communication efforts.
6. **Change Management Plan**: This strategic document prepares stakeholders for the changes—whether business, technical, or cultural—due to the initiative. It highlights the positive aspects of change and aligns stakeholders with the desired future state by identifying their interests and outlining communication strategies.

## Example Workflow

<figure><img src="/files/1d8XqpZv2D5aFF5uZi8T" alt=""><figcaption></figcaption></figure>


---

# 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://docs.7ft10.com/flow-system/change-management-3c-change-model/conduct/plan.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.