≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
pub:company:accountability_chart:start [07.06.2026 15:09] – created Predrag Tasevskipub:company:accountability_chart:start [21.07.2026 13:53] (current) – [How These Roles Support Commitments] Predrag Tasevski
Line 1: Line 1:
-~~NOTOC~~ 
 ====== Accountability Chart ====== ====== Accountability Chart ======
  
-The Accountability Chart is the EOS way of organising the company. Unlike a traditional org chart, it is organised by **function (seats)** — not by people. A seat exists regardless of who sits in it. Each seat has one accountable person.+{{tag>eos accountability-chart organization leadership}}
  
-[[pub:company:eos|← What is EOS?]] | [[pub:company:leadership|← Leadership]]+The **Accountability Chart** maps each organizational seat to its responsibilities and who fills it. It's maintained in the Unicis internal system and reviewed quarterly. 
 + 
 +[[internal:company:accountability_chart|→ View Full Accountability Chart (Internal)]]
  
 ---- ----
  
-===== How to Read This Chart =====+===== SMS & ISMS Role Assignments (October 2026) =====
  
-  * **Seat** — the function (it outlives any person) +As Unicis pursues **[[pub:trust_center:iso_20000_1_overview|ISO 20000-1:2018]]** (Service Management System) and **[[pub:trust_center:iso_27001_overview|ISO 27001:2022]]** (Information Security Management System) certification, the following role assignments are effective:
-  * **Accountable** — the person in the seat +
-  * **Reports to** — who they are accountable to +
-  * **Key responsibilities** — the 3–5 things this seat owns+
  
-> 💡 A seat can be empty (hiring) or held by someone who also holds another seat. The goal is one person per seat as the team grows.+^ Seat ^ SMS Role (ISO 20000-1) ^ ISMS Role (ISO 27001) ^ Responsibility ^ 
 +| **CEO (Predrag)** | **SMS Sponsor / Service Strategy Owner** | **ISMS Sponsor / Information Security Policy Approval** | Oversees both systems; approves policies and budgets; reviews metrics quarterly | 
 +| **CTO (Peter)** | **Service Delivery Owner, Incident Response Lead** | **Information Security Implementation, Technical Controls Lead** | Technical lead for service reliability and security; manages incidents, vulnerabilities, deployments | 
 +| **Operations (Alexander)** | **Support Manager, Change Management Owner** | **Access Control Manager, Incident Escalation Lead** | Operational responsibilities for service delivery; manages user provisioning and support escalation | 
 +| **Marketing (Ksenija)** | **Communications & Stakeholder Updates Lead** | **Security Awareness & Training Lead** | Supports communications around service updates and security awareness training |
  
 ---- ----
  
-===== Current Seats =====+===== What These Roles Mean =====
  
-===== Level 1: Leadership =====+=== SMS (Service Management System) Roles ===
  
-=== Visionary — Predrag Tasevski (CEO) === +Per **[[pub:trust_center:iso_20000_1_overview|ISO 20000-1:2018]]**, the SMS requires:
-**Reports to:** Board / Founders +
-**Key responsibilities:** +
-  * Company vision, strategy, and direction +
-  * Revenue, pricing, and partnerships +
-  * Product design and quality assurance +
-  * Legal, finance, and HR +
-  * Public representation and investor relations+
  
-=== Integrator — Peter Zlatev (CTO) === +  * **SMS Sponsor** (Predrag) — Owns the SMS as a whole; ensures it delivers value and gets resources 
-**Reports to:** Predrag Tasevski +  * **Service Delivery Owner** (Peter) — Accountable for incident response, problem management, capacity planning, deployment success 
-**Key responsibilities:** +  * **Support Manager** (Alexander) — Owns customer support interactions; escalates critical issues; manages response SLAs 
-  * Engineering management and output +  * **Communications** (Ksenija) — Communicates service updates and SLA performance to stakeholders
-  * Infrastructure, DevOps, and platform uptime +
-  * Security monitoring and incident response +
-  * CI/CD pipelines and release management +
-  * Technical architecture and code quality+
  
-----+**Related Metrics:** [[pub:company:scorecard|Scorecard #6, #11, #12, #14]] (uptime, incident response, patches, deployments)
  
-===== Level 2: Functional Seats =====+=== ISMS (Information Security Management System) Roles ===
  
-=== Stakeholder & EU Projects — Alexander Eklöf === +Per **[[pub:trust_center:iso_27001_overview|ISO 27001:2022]]**, the ISMS requires:
-**Reports to:** Predrag Tasevski +
-**Key responsibilities:** +
-  * EU project deliverable tracking and submission +
-  * Community management (Discord, Matrix) +
-  * Support triage and first-line resolution +
-  * Partner communications and onboarding coordination+
  
-=== Marketing & SEO — Ksenija Jovisevic === +  * **ISMS Sponsor** (Predrag) — Owns information security direction; approves policies; allocates security budget 
-**Reports to:** Predrag Tasevski +  * **Information Security Implementation** (Peter) — Implements technical security controls; manages vulnerabilities; leads incident investigation 
-**Key responsibilities:** +  * **Access Control Manager** (Alexander) — Manages user access requests, approvals, and deprovisioning; tracks access control compliance 
-  * Website analytics (Matomo) and SEO strategy +  * **Security Awareness Lead** (Ksenija) — Delivers security training and awareness to team 
-  * Newsletter content and campaign management (Mautic) + 
-  * Social media and content publishing +**Related Metrics:** [[pub:company:scorecard|Scorecard #9, #12, #13]] (security alerts, patch deployment, access provisioning)
-  * Brand consistency and community engagement+
  
 ---- ----
  
-===== Level 3: Individual Contributors =====+===== How These Roles Support Commitments =====
  
-=== Developer, Unicis Apps — Yaroslav Bondarets === +^ Commitment ^ Owner ^ How It's Measured ^ 
-**Reports to:** Peter Zlatev +| **99% Platform Uptime** | Peter (Service Delivery) | [[pub:company:scorecard#11|Scorecard #6]] — Real-time uptime % | 
-**Key responsibilities:** +| **2-hour P1 Response** | Peter + Alexander (Incident Response) | [[pub:company:scorecard#11|Scorecard #11]] — Avg response time | 
-  * Atlassian Forge app development +| **8-hour P2 Response** | Alexander (Support Manager) | [[pub:company:scorecard|Scorecard]] — Avg response time | 
-  * Bug fixes and feature implementation +| **7-day Patch Deployment** | Peter (Security Implementation) | [[pub:company:scorecard#12|Scorecard #12]] — Days to deploy | 
-  * Code reviews and testing+| **1-day Access Provisioning** | Alexander (Access Control) | [[pub:company:scorecard#13|Scorecard #13]] — Days to provision | 
 +| **99% Deployment Success** | Peter (Service Delivery) | [[pub:company:scorecard#14|Scorecard #14]] — Success % |
  
-=== Developer, Unicis Platform — Vitaliy Nezdvetsky === +See [[pub:company:scorecard|Service Performance Scorecard]] for real-time performance.
-**Reports to:** Peter Zlatev +
-**Key responsibilities:** +
-  * Unicis Platform development (Next.js) +
-  * Feature implementation and maintenance +
-  * Code reviews and testing +
- +
-=== Developer — Yaroslav Pisarev === +
-**Reports to:** Peter Zlatev +
-**Key responsibilities:** +
-  * Development tasks as assigned +
-  * Code reviews and testing+
  
 ---- ----
  
-===== Seat Matrix =====+===== Related Documentation =====
  
-^ Seat ^ Accountable ^ Reports to ^ +**Standards & Certifications:** 
-| Visionary (CEO) | Predrag Tasevski | Board | +  * [[pub:trust_center:iso_20000_1_overview|ISO 20000-1:2018 Overview]] — Service Management System 
-| Integrator (CTO) | Peter Zlatev | Predrag Tasevski | +  * [[pub:trust_center:iso_27001_overview|ISO 27001:2022 Overview]] — Information Security Management System 
-| Stakeholder & EU Projects | Alexander Eklöf | Predrag Tasevski | +  * [[pub:trust_center:isms_policy|Information Security Policy]] — Security commitment details 
-| Marketing & SEO | Ksenija Jovisevic | Predrag Tasevski | +  * [[pub:company:service_strategy|Service Strategy & Commitments]] — Service delivery commitments
-| Developer — Unicis Apps | Yaroslav Bondarets | Peter Zlatev | +
-| Developer — Unicis Platform | Vitaliy Nezdvetsky | Peter Zlatev | +
-| Developer | Yaroslav Pisarev | Peter Zlatev |+
  
-----+**Performance & Governance:** 
 +  * [[pub:company:scorecard|Scorecard]] — Real-time role metrics and targets 
 +  * [[pub:company:traction|Quarterly Planning & Reviews]] — How roles review performance 
 +  * [[pub:trust_center:risk_framework|Risk Assessment Framework]] — How roles manage risks
  
-===== Open Seats (Not Yet Filled) =====+**Policies & Procedures:** 
 +  * [[pub:trust_center:document_control_procedure|Document Control Procedure]] — How policies are approved and maintained 
 +  * [[pub:trust_center:policies:it_security_policy|IT Security Policy]] — Detailed security procedures
  
-As the team grows, these seats will be filled:+----
  
-^ Seat ^ Priority ^ Notes ^ +===== Quarterly Accountability Review =====
-| Sales / GTM | High | Needed to scale customer acquisition | +
-| Customer Success | Medium | Currently covered by Predrag + Alexander | +
-| People Ops / HR | Medium | Currently covered by Predrag | +
-| QA Engineer | Low | Currently covered by Predrag |+
  
-----+Each quarter (Q1/Q2/Q3/Q4), role owners review:
  
-===== How Seats Are Updated =====+  * Their assigned metrics on [[pub:company:scorecard|Scorecard]] 
 +  * Performance against [[pub:company:service_strategy|Service Strategy]] commitments 
 +  * Changes needed for [[pub:trust_center:iso_20000_1_overview|ISO 20000-1]] or [[pub:trust_center:iso_27001_overview|ISO 27001]] compliance 
 +  * Updates to the [[internal:company:accountability_chart|Full Accountability Chart]] (internal)
  
-The Accountability Chart is reviewed every **Quarterly Session**. Changes are proposed by the CEO and agreed by the leadership team.+Results are discussed in [[pub:company:traction|Quarterly Planning Sessions]]. 
 + 
 +----
  
-When a seat changes: +[[pub:trust_center|← Trust Center]] | [[pub:company:scorecard|Scorecard →]]
-  1. Update this page +
-  2. Update the Org chart on [[pub:company:unicis|Unicis.Tech]] +
-  3. Announce in ''#town-square'' +
-  4. Update access permissions in OpenProject, GitLab, and Nextcloud+
  
 ---- ----
  
-[[pub:company:eos|← Back to EOS Overview]] | [[pub:company:leadership|← Leadership]] | [[pub:company:vision_traction_organizer|→ V/TO]]+//Last reviewed: October 2026 — next review: Q4 2026 (SMS/ISMS roles added)//
  
-{{tag>accountability eos org-chart leadership}}+{{tag>eos accountability-chart iso20000 iso27001 organization}}