> 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-build-processes-and-a-great-product/operations-and-roles/our-responsibility-assignment-matrixes-raci-and-code-ks.md).

# Our Responsibility Assignment Matrixes: RACI & CODE-KS

To **maintain clarity and accountability**, we utilize the **RACI matrix for cross-department processes and the CODE-KS matrix for in-department processes.** These matrices help us track roles, responsibilities, and progress efficiently.

### RACI MATRIX

<div align="center"><figure><img src="/files/7tNvepxp0ggSAx7JdBbQ" alt="" width="330"><figcaption></figcaption></figure></div>

The RACI matrix is a snapshot of all the roles within a cross-department process. It allows us to track accountability and visualize who is responsible for tasks and make sure all assignments are running effectively. This way every member of a project can be informed and easily updated on the progress. It usually contains only 4 roles people can be assigned to, but in LUNR we have 6. They are:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td> <mark style="color:blue;"><strong>R</strong></mark><strong>esponsible</strong><br>The person responsible for completing a task or project.</td><td></td><td></td></tr><tr><td><mark style="color:blue;"><strong>A</strong></mark><strong>ccountable</strong><br>The individual accountable for the overall execution of the task and final approval.</td><td></td><td></td></tr><tr><td><mark style="color:blue;"><strong>C</strong></mark><strong>onsulted</strong><br>Experts whose opinion is sought during the project.</td><td></td><td></td></tr><tr><td><mark style="color:blue;"><strong>I</strong></mark><strong>nformed</strong><br><strong>I</strong>ndividuals who need to be updated on the project's progress.</td><td></td><td></td></tr><tr><td><mark style="color:purple;"><strong>S</strong></mark><strong>upport</strong><br>This is someone who offers support with some specific process or concept on the task.</td><td></td><td></td></tr><tr><td><mark style="color:purple;"><strong>K</strong></mark><strong>nowledge-Lead</strong><br>This is someone who's responsible for documenting and delivering training regarding a specific process.</td><td></td><td></td></tr></tbody></table>

### CODE-KS MATRIX

The CODE-KS matrix is used for in-department processes and it defines the accountability of each team member in every part of every process. An employee can be accountable for the process:

<figure><img src="/files/8jlps4a90barNMd5A7lR" alt=""><figcaption></figcaption></figure>

&#x20;

**Benefits of RACI & CODE-KS Matrixes:**

* &#x20;**Increased Productivity**: Clearly defining roles reduces confusion and stress, enabling team members to focus on their responsibilities.
* **Targeted Training:** Proper role allocation ensures employees receive relevant training.
* **Streamlined Communication:** Knowing whom to approach for help reduces frustration and saves time.
* **Efficient Meetings:** Inviting only relevant individuals to meetings eliminates unnecessary attendance.
* **Alignment with Strategy:** The matrixes tie individual tasks to the organizational strategy, fostering a collective sense of purpose.
* **Enhanced Performance:** Empowering employees with clear expectations leads to higher performance.

We believe that by trusting high-performing teams and employing empowering processes, we can navigate growth and complexity while maintaining our agility and innovative spirit.


---

# 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-build-processes-and-a-great-product/operations-and-roles/our-responsibility-assignment-matrixes-raci-and-code-ks.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.
