> For the complete documentation index, see [llms.txt](https://management.lunr.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://management.lunr.tech/how-we-make-decisions/leadership.md).

# Leadership

We have seen that by setting **the right context,** e**mployees can understand the company's mission and vision** and create a great product. However, the leadership style in the companies need to support this. Regardless of your role, to ensure effective people management and growth, **you should strive to shift away from "controlling activities" towards a synergistic relationship** between team members. Within complex organizations, leaders need to ensure that the team is heading in the right direction and that any changes throughout the organization will be handled effectively, with minimum disruption to our performance.&#x20;

What makes a good leader is a concept that can vary per team, organization and people's personal opinion. However, in a[ "Context, not Control"](/how-we-make-decisions/strategy/context-not-control.md) environment, you still need people to coach and provide directions, but this is not the traditional role of a leader. That’s why we believe that they key to success is to always l**ook for the ones that can embrace the core principle of caring for others and giving up control rather than seeking control.**

At LUNR, we have two types of leaders: [Managers](/how-we-make-decisions/leadership/managers.md) and [Tech Leads](/how-we-make-decisions/leadership/tech-leads.md). Learn more about them and what do you need to become one in the next chapters.


---

# 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://management.lunr.tech/how-we-make-decisions/leadership.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.
