<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" />
This Notion template includes three key components: a company structure diagram, a list of roles with assigned team members, and a RASCI responsibility matrix.
These elements help establish clarity around team organization and task ownership.
The purpose of this page is to clarify who is responsible for what in the company, to understand the scope of work in each area, and to identify areas without assigned ownership. This brings clarity and unambiguity. Otherwise, there are situations where processes stall, become unsynchronized, or are implicitly expected to be handled by people who do not consider it their responsibility, since no agreement was made. This often leads to team misalignment and reduced cohesion, which directly impacts efficiency and, at times, the very survival of the project.
Below is a typical example for a product-focused IT company at an early stage. The goal is not to cover everything, but to set a direction you can adapt and refine to fit your organization.
Edit the company structure diagram
In the dropdown of the codeblock, select Split
instead of Preview
, to edit the diagram directly here, or copy the code and paste it into https://www.mermaidchart.com/, where you can edit it using the UI editor, then paste the updated code back here. After that, select Preview
to hide diagram code.
Keep only the entries relevant to your company’s current structure or growth direction. Assign someone in the Assigned Person
field.
If you currently have only 3 team members, e.g. CEO, CTO, CPO, then all subordinate roles should be assigned to one of them. For example, Engineering Director, Infrastructure Lead, DevOps Engineer, SRE, Software Developer, etc., should all be assigned to the person, who is assigned to CTO. If you’re alone for now - assign everything to yourself.
Edit the RACI matrix
Keep only the tasks that are actually performed or should be performed in your company.
Fill in the R, A, S, C, and I fields with roles from the .
Make sure to use roles, not individuals. The assigned people will be automatically shown via rollups in the Persons
view.
As your team grows or roles change, update the Assigned Person
field in the roles table, and the data in the RASCI matrix will update automatically and stay current.
This ensures clear ownership and improves visibility and efficiency of internal processes.
</aside>
graph TD
STK[**Stakeholders**] --> CEO
subgraph "Executive Leadership"
CEO[CEO] --> CTO[CTO]
CEO --> CPO[CPO]
end
subgraph "Product"
CPO --> PRODMAN[Product Manager]
CPO --> F[Business Analyst]
CPO --> PA[Product Analyst]
CPO --> DA[Data Analyst]
PRODMAN --> UXUI[UX/UI Designer]
end
subgraph "Engineering & Technology"
CTO --> ED[Engineering Director]
subgraph "Technical Leadership"
ED --> TECHLEAD[Tech Lead]
end
subgraph "Development"
ED --> PM[Project Manager]
ED --> TEAMLEAD[Team Lead]
TEAMLEAD --> FRONTENG[Frontend Developer]
TEAMLEAD --> BACKENG[Backend Developer]
TEAMLEAD --> QA[QA Engineer]
end
subgraph "Infrastructure"
ED --> INFRALEAD[Infrastructure Lead]
INFRALEAD --> DEVOPS[DevOps Engineer]
INFRALEAD --> SRE[SRE]
end
end
subgraph "Marketing"
CEO --> MM[Marketing Manager]
MM --> SMM[SMM Manager]
MM --> DESIGNER[Creative Designer]
MM --> SEO["SEO/ASO Specialist"]
end
subgraph "Sales"
CEO --> SM[Sales Manager]
subgraph "Support"
SUP[Customer Support Specialist]
end
SM --> SUP
end