# Key questions for onboarding

Regardless of the practicalities of any conversation to join an organisation, there are three dimensions we think are important to chew a bit on before hand.<br>

### Value Set

Holon finds its reason to be in our understanding of the current situation in the world, and the role design can have on it. You can check [our ideology](https://weareholon.gitbook.io/handbook/governance/ideology) to get a better grasp of what we mean. To be purpose driven is something important to consider if we feel like your cup of tea.<br>

### Project based

For several reasons as an organisation we are closer to a collective of entrepreneurs than a salary giving company. A space for people with a ryhming value set and passion to show design's impact. In practical terms at the moment money is related to projects, where a team is formed around, who then share back to the collective a part. There are collective benefits applying to different [membership roles](https://weareholon.gitbook.io/handbook/governance/membership), but anyone willing to be involved at this stage of the evolution of the collective needs to consider this too.<br>

### Skillset

It is important that you have some sort of understanding, and if not a willinging to be embrace, design as a change making culture. We are not fixed on which skills we need as it depends a lot on ongoing projects, so we are open to incorporate diverse competences. More importanly our understanding of what constitutes a collective is that each of us is encouraged to develop their own paths that contribute to the shared purpose and goals stated in our ideology.<br>

If you still think is worth going forward, then get in contact at hola at holon dot cat with a couple of time slots that would work for you to have a call :)


---

# 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://weareholon.gitbook.io/handbook/processes/onboarding/key-questions-for-onboarding.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.