> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/disrupt-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/disrupt-playbook/disrupt-schedule.md).

# Disrupt Schedule

The following schedule is not prescriptive but descriptive, showing how the toolkit could be organised and matched to the four-week structure of the archetypal ‘Disrupt’ activity.  Whilst there is some logic built into the plan – for example, to create a Roadmap Radar, you need to run an OKR session – the spirit here is to encourage a bespoke approach to answering the client’s question(s), using novel combinations of these tools rather than following this schedule to the letter.

### **Week One: Shape the Vision**

We work with senior leaders to understand the history and the current state of the business and confirm the vision for future success.  We facilitate workshops during which long-term goals, short-term objectives, and measurable key results are collaboratively defined.  Drawing on market insights and our proprietary strategic map of the business landscape, we can identify immediate threats to the business and advise on the viability of potential divestments and diversifications.  We then work with a broader range of participants to share the resulting strategy, refine it further, and turn it into concrete actions and initiatives.  We always draw on the existing portfolio of activities, tuned or augmented as necessary to meet the defined objectives, and we help build in continuous delivery of value, supported by rapid test-and-learn experiments to validate the hypotheses.

Out of these activities, we produce the first draft of the Roadmap Radar – a tool unique to Equal Experts that lays out the client’s portfolio on a single, big picture in a way that aligns activities to objectives, informs organisation change, reduces critical path dependencies, and allows multidisciplinary teams to own and adapt as necessary.

| Day    | **Activity**                                                            | **Description**                                                                                                                       | **Who should be involved**                                                |
| ------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| Day  1 | <p>AM: “All Hands Welcome”, with feedback wall</p><p>PM: 1-2-1s</p>     | In-depth interviews with a range of stakeholders, to better understand the past, present and future                                   | <p>AM: All</p><p>PM: Senior stakeholders</p>                              |
| Day 2  | OKRs (all day)                                                          | A flexible, collaborative method that ensures activities are aligned to the strategy, across the organisation                         | 6-8 senior leaders from across functions                                  |
| Day 3  | <p>AM: 1-2-1s (ctd)</p><p>PM: Value Stream Mapping</p>                  | Mapping where value is in the organisation, to inform build, buy and borrow decisions                                                 | <p>AM: Senior stakeholders</p><p>PM: Cross- functional delivery teams</p> |
| Day 4  | <p>AM: Roadmap Radar (iteration 1)</p><p>PM: Business Evolution Map</p> | Visualise the goals and objectives of the organisation, with initiatives plotted on the radar to indicate clusters and gaps in effort | <p>AM: Delivery teams</p><p>PM: Senior stakeholders</p>                   |
| Day 5  | Office day, including weekly update to project sponsors                 | Opportunity for the team to reflect, write-up insights from the week, and plan the forthcoming week                                   | Equal Experts team                                                        |

### **Week Two: Plan the Approach**

We dig deeper into each of the objectives to identify gaps and strengthen the areas where those objectives are poorly served by current activities.  We identify initiatives that do not align with the objectives and help remove duplication and prune the portfolio as necessary.  We will also take the opportunity to further any research assumptions made during the first week, and factor the resulting insights into the strategy.  The Roadmap Radar is refined to a level that can be used to define the shape of multi-disciplinary teams required to fulfil each of the objectives, and based on those definitions, we can identify candidate participants for each of those teams.

| Day   | **Activity**                                                                      | **Description**                                                                                                                                                             | **Who should be involved**                              |
| ----- | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| Day 1 | <p>AM: Customer Journey Mapping</p><p>PM: Finalise and send out online survey</p> | Map the customer journey process from end-to-end, starting with requirements through to an agreed definition of ‘done’, looking for pain points, duplication and redundancy | <p>AM: Delivery teams</p><p>PM: All stakeholders</p>    |
| Day 2 | <p>AM: 1-2-1s (ctd)</p><p>PM: Roadmap Radar (iteration 2)</p>                     | Visualise the goals and objectives of the organisation, with initiatives plotted on the radar to indicate clusters and gaps in effort                                       | <p>AM: Senior stakeholders</p><p>PM: Delivery teams</p> |
| Day 3 | Lean Value Tree (all day)                                                         | Organise your bets to make effective interventions, and measure the results                                                                                                 | Delivery teams                                          |
| Day 4 | Bet canvas (iteration 1)                                                          | Highly structured bets, outlining how the experiment will be designed, measures of success, and any challenges and risks                                                    | Delivery teams                                          |
| Day 5 | Office day, including weekly update to project sponsors                           | Opportunity for the team to reflect, write-up insights from the week, and plan the forthcoming week                                                                         | Equal Experts team                                      |

### **Week three: Make the First Move**

Once the client is ready to make the first strategic move, we will help form the first exploratory teams and establish ways of working aligned to the bets derived from the Roadmap Radar.  We will work with those teams to ensure activities are appropriately prioritised and improve them further as necessary to ensure that the first tasks are “good to go.”  We can also work to shape the communication approach and ensure there is a proper understanding of and buy-in to the strategic plan.

| Day   | **Activity**                                                                        | **Description**                                                                       | **Who should be involved**                         |
| ----- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Day 1 | <p>AM: Team Health Check</p><p>PM: Bet Canvas (iteration 2)</p>                     | Assess all aspects of team health, confirm strengths and explore issues               | <p>AM: Delivery teams</p><p>PM: Delivery teams</p> |
| Day 2 | <p>AM: Team Health Check</p><p>PM: Bet Canvas (iteration 2)</p>                     | Assess all aspects of team health, confirm strengths and explore issues               | <p>AM: Delivery teams</p><p>PM: Delivery teams</p> |
| Day 3 | <p>AM: Team Health Check</p><p>PM: Bet Canvas (iteration 2)</p>                     | Assess all aspects of team health, confirm strengths and explore issues               | <p>AM: Delivery teams</p><p>PM: Delivery teams</p> |
| Day 4 | <p>AM: Chase and close online survey</p><p>PM: Analyse results of online survey</p> | An online survey allows everyone to contribute to the process                         | All stakeholders                                   |
| Day 5 | Office day, including weekly update to project sponsors                             | Opportunity for the team to reflect, write-up insights, and plan the forthcoming week | Equal Experts team                                 |

### **Week Four: Deliver the Insights**

The team reflects on the gathered evidence, workshops the best interventions, and prepares for the final presentation to the Board. Typically, during the final playback session, we start with our headline observations and recommendations, before inviting questions and having a non-linear discussion about those topics that the Execs identify as the most important.

| Day   | **Activity**                                                                      | Description                                                                                                                                              | Who should be involved                             |
| ----- | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Day 1 | <p>AM: Current Reality Tree</p><p>PM: Future Reality Tree</p>                     | See beyond intermediate effects to understand the root causes of observed undesirable effects, and devise injections that will make a lasting difference | <p>AM: Delivery teams</p><p>PM: Delivery teams</p> |
| Day 2 | <p>AM: Roadmap Radar (final iteration)</p><p>PM: Bet Canvas (final iteration)</p> | Visualise the goals and objectives of the organisation, with initiatives plotted on the radar to indicate clusters and gaps in effort                    | <p>AM: Delivery teams</p><p>PM: Delivery teams</p> |
| Day 3 | Final report write-up                                                             | Team reflects on evidence gathered, workshops the best interventions, and prepares the final presentation to the Board                                   | Equal Experts team                                 |
| Day 4 | Final report write-up                                                             | Team reflects on evidence gathered, workshops the best interventions, and prepares the final presentation to the Board.                                  | Equal Experts team                                 |
| Day 5 | Final report write-up                                                             | Team reflects on evidence gathered, workshops the best interventions, and prepares the final presentation to the Board.                                  | Equal Experts team                                 |


---

# 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://playbooks.equalexperts.com/disrupt-playbook/disrupt-schedule.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.