> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/the-company/culture/management.md).

# Management

## Management

### You are not a boss <a href="#you-are-not-a-boss" id="you-are-not-a-boss"></a>

The purpose of management is to serve the team. You are there to ensure that your team can work at their best, and that obstacles to the best possible work are removed.

So, your main aim should be to help make the individuals that make up your team the best they can be.

### Help to reduce meta work <a href="#help-to-reduce-meta-work" id="help-to-reduce-meta-work"></a>

Management should ensure that meta-work is reduced as much as possible, and should review processes regularly to ensure that we do not creep into a bureaucracy.

### Absolutely No Status Symbols <a href="#absolutely-no-status-symbols" id="absolutely-no-status-symbols"></a>

Regardless of your position at Mad, there are no status symbols or special perks.

### Quarterly Meetings <a href="#quarterly-meetings" id="quarterly-meetings"></a>

Three weeks prior to the start of a new quarter there is a management planning meeting.\
This includes:

* Financial Review
* Estimated P/L for the current quarter
* Current Cash Flow analysis for next quarter
* Discussion on main successes/failures of the current quarter.
* Any changes that are required.
* Review all team member scorecards and discuss any issues.

### Board Meetings <a href="#board-meetings" id="board-meetings"></a>

Mäd’s board is made up of the following members:

* Emanuele Faja
* Morten Bech
* Dung Dinh


---

# 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://process.mad.co/the-company/culture/management.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.