> For the complete documentation index, see [llms.txt](https://deep-work.gitbook.io/organizational-design-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deep-work.gitbook.io/organizational-design-playbook/introduction-to-organizational-design-for-a-web3-native-economy/organizational-mapping-2-hours.md).

# Organizational Mapping \[2 hours]

By following this workflow, organizations can gain a comprehensive understanding of their workforce and improve efficiency among team members.

{% embed url="<https://miro.com/app/board/uXjVPHt9obk=/?share_link_id=966724089596>" %}

## Brainstorm Work

Start by gathering a group of individuals involved in the organization. Together, brainstorm and list all the different types of work being performed, whether it's teamwork or individual tasks.

<figure><img src="https://2059771044-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fcl43mnU5rrHpeVTbf7YG%2Fuploads%2FJUVUkke0nqD5pCc6YZdp%2F20230802_1626102.jpg?alt=media&amp;token=7cfbc02b-0d42-4d94-95ab-2ca4b2523699" alt=""><figcaption><p>You can do it remotely in Miro or in person with a whiteboard</p></figcaption></figure>

## Categorize Work

Once the work items are identified, categorize them into context-based teams or groups. These categories should be based on common themes or shared contexts for efficient collaboration.

## Identify Leads and Goals

Within each context-based category, assign specific responsibilities to individuals. Start with assigning a lead to each category and together define the mission and goals of each category. These can be seen as context-based teams.

## Visualise time-based projects

Each context-based team should have more defined time-based initiatives and projects. Discuss and note down all time-based projects together with the lead.

<figure><img src="https://2059771044-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fcl43mnU5rrHpeVTbf7YG%2Fuploads%2FMrOjaG5l0g6gKBQ7vDoE%2FDappnode%20-%20Organizational%20Map%20-%20Legend.jpg?alt=media&amp;token=16da6852-e3fd-4b6b-b33d-f52f3be209db" alt=""><figcaption></figcaption></figure>

## Define Responsibilities and Job Titles

For each of the time-based projects, ask the team to add their name to visualise their involvement.&#x20;

For each assigned responsibility, allow individuals to choose or create appropriate job titles that reflect their roles and areas of expertise within the organization.

<figure><img src="https://2059771044-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fcl43mnU5rrHpeVTbf7YG%2Fuploads%2FSSKz11Z5LjuYh0RoV80q%2FDappnode%20-%20Organizational%20Map%20(1).jpg?alt=media&amp;token=64181ab3-645e-41d9-8f33-f7401e41820d" alt=""><figcaption><p>Example from a workshop with DappNode</p></figcaption></figure>

## Review and Revise

After completing the mapping exercise, review the results periodically. Conduct reviews to ensure that the categorization and assignments remain accurate and aligned with the organization's goals.

## Update and Adapt

As the organization evolves, adapt the mapping accordingly. Integrate new work items or adjust responsibilities to accommodate changes in the organization's structure and objectives.

## Document

Maintain clear and accessible documentation of the organizational mapping. This documentation should include the categories, assignments, job titles, and any updates made during the review process.
