> For the complete documentation index, see [llms.txt](https://wiki.oikos-international.org/leaptools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.oikos-international.org/leaptools/guidebook/design-your-leap-journey.md).

# 3. Design your LEAP journey

## STEP 01

\
**Think about who are the people in your chapter you want and need to involve to be part of your LEAP journey :**

|                                   <mark style="background-color:blue;">**Initiator(s)**</mark>                                   |                <mark style="background-color:green;">**Facilitators**</mark>               |
| :------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------: |
| <p></p><p>The person/core group that identified the need of having a LEAP journey & that will take care of the coordination.</p> | <p></p><p>People who step up to prepare & host a workshop session on the topic chosen.</p> |

|       <mark style="background-color:purple;">**Participants**</mark>       |               <mark style="background-color:orange;">**Coach**</mark>               |
| :------------------------------------------------------------------------: | :---------------------------------------------------------------------------------: |
| Your chapter community that commits & actively takes part in the sessions. | A support person for the initiators who has experience with the oikos LEAP program. |

{% hint style="info" %}
People joining the LEAP can have several roles throughout the program.
{% endhint %}

## STEP 02

\
**Get in contact with your coach and invite people to form a team (initiator(s), coach(es) and facilitator(s)).**&#x20;

\
Host a meeting to think together about the questions below and to organise a strategy.

## STEP 03

\
**Together with the group you formed, answer these questions:**

(These are tips from previous experiences)<br>

### Clarifying the purpose

{% tabs %}
{% tab title="What is the need and purpose of your LEAP ?" %}
What issues do you want to address in your community or what areas do you see as opportunities for personal and team/collective development?
{% endtab %}

{% tab title="What do you want to learn? " %}
On which topics does your community want to have sessions? \
\&#xNAN;*Are you asking your community what they wish to learn? How can you gather their insights? Should you organise a doodle or a form, are you asking them during a meeting?*\
\&#xNAN;*<mark style="background-color:green;">--> Check the LEAP TOPICS for insights</mark>*
{% endtab %}
{% endtabs %}

### Clarifying the format

{% tabs %}
{% tab title="In which format could the LEAP serve your needs?" %}
*Are you planning an in-person or online journey?*
{% endtab %}

{% tab title="How many sessions? 1, 3, 5, 10 sessions?" %}
See with your members/colleagues planning. For students examples, a semester is ideal
{% endtab %}

{% tab title="When is your LEAP journey happening?" %}
Defining clear dates and times maximises comitment
{% endtab %}
{% endtabs %}

### Clarifying the commitment

{% tabs %}
{% tab title="How often do you meet?" %}
We recommend one session a month, maximum two to allow time for reflexion between sessions
{% endtab %}

{% tab title="How long will the sessions be? " %}
From our experience, sessions last at least 90minutes and shouldn't exceed 120 minutes
{% endtab %}

{% tab title="What is happening between the meetings? " %}
Be very clear on this to maximize engagement. Are you engaging in more conversations? Is there a feedback form so people can express their thoughts and feelings about the session?
{% endtab %}

{% tab title="How will you encourage and ensure commitment of the group?" %}
Find here guiding questions to help clarify it : \
° What commitments & principles are required for your group?\
&#x20;    ° E.g. commitment of all participants to being open to learn together; attend all sessions, practicing between sessions.\
&#x20;     ° E.g. certificate of the end of the LEAP journey&#x20;
{% endtab %}
{% endtabs %}

### Clarifying the start & end

{% tabs %}
{% tab title="Is there a kick off meeting to explain the LEAP and involve everyone? " %}
Experience highlighted a kickoff attracts more members and increases external communication
{% endtab %}

{% tab title="Is there a celebration and reflection meeting ?" %}
Sharing the learnings and opening reflexions for a next LEAP journey ahead increases involvment for the next edition :wink: \
E.g. certificate at the end of a LEAP for Chapter journey
{% endtab %}
{% endtabs %}

### Clarifying responsibilities

{% tabs %}
{% tab title="Who from the team will be responsible for what?  " %}
Set roles and an agenda to coordinate
{% endtab %}

{% tab title="How will you communicate to your participants about and during the journey?" %}
Make sure to stick to what fits your group the best \
E.G. email, doodle, slack, google calendar, ...&#x20;
{% endtab %}
{% endtabs %}


---

# 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://wiki.oikos-international.org/leaptools/guidebook/design-your-leap-journey.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.
