Manateq - Economic Zones Company, Qatar
Section 9

Governance & Enforcement

Ownership, change management, versioning, and compliance requirements for the design system.

Ownership & Responsibilities

Design System Owner

Primary steward of the design system.

  • • Maintains documentation
  • • Reviews change requests
  • • Ensures brand alignment
  • • Coordinates with stakeholders
Design System Committee

Cross-functional review board.

  • • Design Lead
  • • Engineering Lead
  • • Product Manager
  • • Accessibility Specialist
Implementation Teams

Teams building products with the system.

  • • Follow design system standards
  • • Report issues and gaps
  • • Propose new components
  • • Contribute improvements

Change Management

Versioning (Semantic Versioning)
Change TypeVersion ImpactDescriptionApproval Required
Patch1.0.xBug fixes, typo corrections, minor clarificationsDesign System Owner
Minor1.x.0New components, non-breaking additions, new tokensDesign System Committee
Majorx.0.0Breaking changes, significant redesigns, removal of componentsExecutive Sponsor + Committee

Change Request Process

  1. 1

    Submit Request

    Create a change request with detailed justification, mockups, and impact assessment.

  2. 2

    Initial Review

    Design System Owner reviews for completeness and alignment with brand values.

  3. 3

    Committee Review

    For Minor/Major changes, the committee evaluates technical feasibility and accessibility.

  4. 4

    Implementation

    Approved changes are implemented, documented, and added to the component library.

  5. 5

    Release & Communication

    New version is released with changelog and migration guide if needed.

Vendor & Third-Party Compliance

Mandatory Compliance

All external vendors and third-party developers building digital products for Manateq must adhere to this design system. Non-compliance may result in project rejection.

  • Vendors must receive a copy of this document at project kickoff
  • Design reviews must include compliance checks against this system
  • Deviations require written approval from the Design System Owner
  • Final deliverables must pass accessibility audit (WCAG 2.1 AA)

Enforcement Mechanisms

Automated Checks
  • • Linting rules for design token usage
  • • CI/CD pipeline accessibility tests
  • • Automated visual regression testing
  • • Component usage analytics
Manual Reviews
  • • Design review checkpoints
  • • Code review guidelines
  • • Quarterly compliance audits
  • • User testing feedback loops

Document Information

This Document

Version
1.0
Issue Date
December 2025
Status
Active

Source Document

Document
MNTQ-PRM-GDL-01
Revision
6
Issue Date
1 June 2023