# Designing

## Essentials

All exercises need to consider SME - **Story, Mechanics and Environment**.

Use the Canvas in AXS to see these at a glance so you know they’re all considered together.

<img src="/files/0m2UdIjzwpcqXDrxwzQp" alt="" class="gitbook-drawing">

## Participatory Storytelling

A character in a story overcomes challenges to discover themselves.

In a crisis exercise, the player is the character – they must overcome challenges to believe in themselves and believe in the process (or reform it).

Think in terms of distinctive events which are moments in the exercise: one event = one serial.

<figure><img src="/files/qcZLtrjTohYHupmoYZ8n" alt=""><figcaption></figcaption></figure>

### Players need to do stuff

Exercises are **participatory** – we need to remember that we need to get players **doing something**, not passively reading.

A common mistake is to publish a lot of content and have players read too much.

Use the diagram below to consider possible player activities as a means to achieve your training objectives.

<img src="/files/y1H9XE3eeGN58kGBz44t" alt="" class="gitbook-drawing">


---

# Agent Instructions: 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:

```
GET https://helpdocs.conducttr.com/concepts/designing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
