Monorepo Requirements Documentation
OCM Change Management Requirements — Examples

1. Personas
PERSONA-OCM-003
1.1. Senior Stakeholder / Sponsor UID: PERSONA-OCM-003 RELATIONS (Child): STATEMENT:

Provides strategic oversight of organisational change initiatives and ensures alignment with enterprise priorities. Strategic rather than operational, limited time, focused on outcomes and impact. Requires concise information and influences direction and prioritisation.

 PRIORITY:

Secondary

 TECH_COMFORT:

Medium

 FREQUENCY:

Weekly

 STATUS:

Active
  • UX-001
    3.1.1. Personalised Homepage Content UID: UX-001 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Personalisation BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 STAKEHOLDER_DEPARTMENT: OCM / IT CURRENT_STATE: No personalised experience; all users see identical content regardless of role. DESIRED_OUTCOME: Each user role sees a tailored homepage with relevant widgets, news, and quick links from first login. RELATIONS (Parent): STATEMENT:

    Platform must deliver personalised homepage content based on user roles with different widgets, news, and quick links for 3700+ users.
  • CONTENT-001
    3.2.1. News Content Management UID: CONTENT-001 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: News BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 CURRENT_STATE: News and updates distributed via email with no central archive or structure. DESIRED_OUTCOME: Administrators can create, tag, schedule, and publish news content through the platform. RELATIONS (Parent): STATEMENT:

    Platform must support creation and management of news content, including articles, images, tagging, categorisation, and scheduling.
  • CONTENT-004
    3.2.4. Network Update Publishing UID: CONTENT-004 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Reporting BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Updates shared via ad hoc email with no consistent format or central record. DESIRED_OUTCOME: Administrators publish concise updates once; all relevant user groups receive them through the platform. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must support publishing and sharing concise updates and key information to network users.
PERSONA-OCM-001
1.2. OCM Practitioner UID: PERSONA-OCM-001 RELATIONS (Child): STATEMENT:

Leads or supports the implementation of organisational change initiatives within an entity, ensuring adoption of new processes, tools, and ways of working. Works across multiple projects and stakeholder groups, delivery-focused and time-constrained. Requires practical, actionable guidance. Often lacks a consistent OCM approach and coordinates between leadership, IT, and business stakeholders.

 PRIORITY:

Primary

 TECH_COMFORT:

Medium-High

 FREQUENCY:

Daily

 STATUS:

Active
  • UX-001
    3.1.1. Personalised Homepage Content UID: UX-001 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Personalisation BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 STAKEHOLDER_DEPARTMENT: OCM / IT CURRENT_STATE: No personalised experience; all users see identical content regardless of role. DESIRED_OUTCOME: Each user role sees a tailored homepage with relevant widgets, news, and quick links from first login. RELATIONS (Parent): STATEMENT:

    Platform must deliver personalised homepage content based on user roles with different widgets, news, and quick links for 3700+ users.
  • UX-002
    3.1.2. Responsive Design UID: UX-002 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Mobile BABOK_CLASSIFICATION: Solution Requirements - Non-Functional REQUIREMENT_TYPE: Non-Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: No mobile-optimised access; users on mobile devices receive a degraded desktop experience. DESIRED_OUTCOME: Full functionality available on all device sizes without a separate mobile site. RELATIONS (Parent): STATEMENT:

    Platform must provide fully responsive design that adapts to all device sizes — desktop, tablet, and mobile — without a separate mobile site, optimised for performance.
  • UX-003
    3.1.3. Search and Filtering UID: UX-003 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Search BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: No centralised search; users browse unstructured file shares or email colleagues to find materials. DESIRED_OUTCOME: Users locate relevant content within 2-3 clicks via search and category filters. RELATIONS (Parent): STATEMENT:

    Platform must provide search and filtering functionality to enable users to quickly locate relevant content and resources.
  • CONTENT-002
    3.2.2. OCM Toolkit Repository UID: CONTENT-002 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: OCM tools and templates scattered across email, file shares, and individual drives with no consistent structure. DESIRED_OUTCOME: Practitioners find categorised templates and guidance in one place, reducing preparation time significantly. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must provide a structured OCM toolkit with categorised templates and guidance to support implementation of change initiatives.
  • CONTENT-003
    3.2.3. Cross-Entity Knowledge Sharing UID: CONTENT-003 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Accessibility BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Knowledge sharing between NATO entities is fragmented and not systematically captured. DESIRED_OUTCOME: Practitioners can browse and learn from structured examples and case-based content across NATO entities. RELATIONS (Parent): STATEMENT:

    Platform must provide access to examples, practices, and case-based content from NATO entities to support knowledge sharing.
PERSONA-OCM-002
1.3. Central OCM Team UID: PERSONA-OCM-002 RELATIONS (Child): STATEMENT:

Designs, governs, and maintains the NATO Enterprise OCM approach and portal, ensuring consistency, quality, and scalability across entities. Responsible for enterprise-level OCM alignment. Owns methodology, tools, and governance. Balances strategic direction with practical usability and manages multiple stakeholders and priorities.

 PRIORITY:

Primary

 TECH_COMFORT:

Medium-High

 FREQUENCY:

Weekly

 STATUS:

Active
  • CONTENT-001
    3.2.1. News Content Management UID: CONTENT-001 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: News BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 CURRENT_STATE: News and updates distributed via email with no central archive or structure. DESIRED_OUTCOME: Administrators can create, tag, schedule, and publish news content through the platform. RELATIONS (Parent): STATEMENT:

    Platform must support creation and management of news content, including articles, images, tagging, categorisation, and scheduling.
  • CONTENT-004
    3.2.4. Network Update Publishing UID: CONTENT-004 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Reporting BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Updates shared via ad hoc email with no consistent format or central record. DESIRED_OUTCOME: Administrators publish concise updates once; all relevant user groups receive them through the platform. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must support publishing and sharing concise updates and key information to network users.
PERSONA-OCM-004
1.4. Network Participant (OCM Community of Interest) UID: PERSONA-OCM-004 RELATIONS (Child): STATEMENT:

Participates in the OCM network alongside primary responsibilities, with an interest in staying informed and exchanging experiences. Not dedicated to OCM full-time, limited availability, selective in engagement. Values relevance and efficiency and prefers lightweight interaction.

 PRIORITY:

Secondary

 TECH_COMFORT:

Medium

 FREQUENCY:

Weekly

 STATUS:

Active
  • UX-002
    3.1.2. Responsive Design UID: UX-002 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Mobile BABOK_CLASSIFICATION: Solution Requirements - Non-Functional REQUIREMENT_TYPE: Non-Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: No mobile-optimised access; users on mobile devices receive a degraded desktop experience. DESIRED_OUTCOME: Full functionality available on all device sizes without a separate mobile site. RELATIONS (Parent): STATEMENT:

    Platform must provide fully responsive design that adapts to all device sizes — desktop, tablet, and mobile — without a separate mobile site, optimised for performance.
  • CONTENT-003
    3.2.3. Cross-Entity Knowledge Sharing UID: CONTENT-003 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Accessibility BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Knowledge sharing between NATO entities is fragmented and not systematically captured. DESIRED_OUTCOME: Practitioners can browse and learn from structured examples and case-based content across NATO entities. RELATIONS (Parent): STATEMENT:

    Platform must provide access to examples, practices, and case-based content from NATO entities to support knowledge sharing.
  • CONTENT-004
    3.2.4. Network Update Publishing UID: CONTENT-004 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Reporting BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Updates shared via ad hoc email with no consistent format or central record. DESIRED_OUTCOME: Administrators publish concise updates once; all relevant user groups receive them through the platform. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must support publishing and sharing concise updates and key information to network users.
  • CONTENT-005
    3.2.5. Training Materials Library UID: CONTENT-005 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 2 - Enhancements SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Training materials exist in isolation per project with no shared library or consistent structure. DESIRED_OUTCOME: HR and training staff access a structured, reusable library of training materials aligned with OCM practices. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must provide structured training materials aligned with OCM practices to support capability development.
PERSONA-OCM-005
1.5. HR / Training Representative UID: PERSONA-OCM-005 RELATIONS (Child): STATEMENT:

Supports organisational change through training, people development, and capability building activities. People-focused role that supports but does not lead change. Works across multiple initiatives, needs structured guidance, and is involved in training delivery.

 PRIORITY:

Secondary

 TECH_COMFORT:

Medium

 FREQUENCY:

Daily

 STATUS:

Active

2. User Stories
  • CONTENT-002
    3.2.2. OCM Toolkit Repository UID: CONTENT-002 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: OCM tools and templates scattered across email, file shares, and individual drives with no consistent structure. DESIRED_OUTCOME: Practitioners find categorised templates and guidance in one place, reducing preparation time significantly. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must provide a structured OCM toolkit with categorised templates and guidance to support implementation of change initiatives.
US-OCM-001
2.1. Access OCM Toolkit and Templates UID: US-OCM-001 PERSONA: OCM Practitioner PERSONA_PRIORITY: Primary BUSINESS_VALUE: High STATUS: Accepted RELATIONS (Parent): STATEMENT:

As an OCM Practitioner I want to quickly find relevant tools, templates, and guidance so that I can apply a consistent OCM approach without reinventing approaches across projects.

 ACCEPTANCE_CRITERIA:
  • Search functionality available with filters by category and topic
  • Relevant search results returned within 2-3 clicks
  • Resources found and downloadable in under 1 minute
  • Content structured and easy to browse
US-SS-001
2.2. High-Level Progress Overview UID: US-SS-001 PERSONA: Senior Stakeholder / Sponsor PERSONA_PRIORITY: Secondary BUSINESS_VALUE: High STATUS: Accepted RELATIONS (Parent): STATEMENT:

As a Senior Stakeholder I want to see high-level updates and key metrics related to the OCM initiative so that I can quickly understand progress and impact across NATO entities.

 ACCEPTANCE_CRITERIA:
  • Homepage displays key OCM-related updates and milestones
  • Critical announcements are highlighted
  • Content is concise and easy to scan
  • Ability to navigate to more detailed information if required
US-NP-001
2.3. Concise Network Updates UID: US-NP-001 PERSONA: Network Participant (OCM Community of Interest) PERSONA_PRIORITY: Secondary BUSINESS_VALUE: High STATUS: Proposed RELATIONS (Parent): STATEMENT:

As a Network Participant I want to receive concise updates and access key materials so that I can stay informed without investing significant time.

 ACCEPTANCE_CRITERIA:
  • Updates are concise and relevant
  • Clear structure of communication
  • Easy access to related materials
  • No information overload
  • CONTENT-005
    3.2.5. Training Materials Library UID: CONTENT-005 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 2 - Enhancements SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Training materials exist in isolation per project with no shared library or consistent structure. DESIRED_OUTCOME: HR and training staff access a structured, reusable library of training materials aligned with OCM practices. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

    Platform must provide structured training materials aligned with OCM practices to support capability development.
US-HR-001
2.4. Structured Training Materials UID: US-HR-001 PERSONA: HR / Training Representative PERSONA_PRIORITY: Secondary BUSINESS_VALUE: Medium STATUS: Proposed RELATIONS (Parent): STATEMENT:

As an HR / Training Representative I want access to structured training materials so that I can support organisational change initiatives effectively.

 ACCEPTANCE_CRITERIA:
  • Training materials available centrally
  • Content structured by topic
  • Materials reusable and downloadable
  • Clear linkage to OCM approach

3. Requirements

3.1. User Experience
UX-001
3.1.1. Personalised Homepage Content UID: UX-001 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Personalisation BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 STAKEHOLDER_DEPARTMENT: OCM / IT CURRENT_STATE: No personalised experience; all users see identical content regardless of role. DESIRED_OUTCOME: Each user role sees a tailored homepage with relevant widgets, news, and quick links from first login. RELATIONS (Parent): STATEMENT:

Platform must deliver personalised homepage content based on user roles with different widgets, news, and quick links for 3700+ users.
UX-002
3.1.2. Responsive Design UID: UX-002 STATUS: Accepted CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Mobile BABOK_CLASSIFICATION: Solution Requirements - Non-Functional REQUIREMENT_TYPE: Non-Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: No mobile-optimised access; users on mobile devices receive a degraded desktop experience. DESIRED_OUTCOME: Full functionality available on all device sizes without a separate mobile site. RELATIONS (Parent): STATEMENT:

Platform must provide fully responsive design that adapts to all device sizes — desktop, tablet, and mobile — without a separate mobile site, optimised for performance.
UX-003
3.1.3. Search and Filtering UID: UX-003 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: User Experience SUB_CATEGORY: Search BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: No centralised search; users browse unstructured file shares or email colleagues to find materials. DESIRED_OUTCOME: Users locate relevant content within 2-3 clicks via search and category filters. RELATIONS (Parent): STATEMENT:

Platform must provide search and filtering functionality to enable users to quickly locate relevant content and resources.

3.2. Content
  • PERSONA-OCM-002
    1.3. Central OCM Team UID: PERSONA-OCM-002 RELATIONS (Child): STATEMENT:

    Designs, governs, and maintains the NATO Enterprise OCM approach and portal, ensuring consistency, quality, and scalability across entities. Responsible for enterprise-level OCM alignment. Owns methodology, tools, and governance. Balances strategic direction with practical usability and manages multiple stakeholders and priorities.

     PRIORITY:

    Primary

     TECH_COMFORT:

    Medium-High

     FREQUENCY:

    Weekly

     STATUS:

    Active
  • PERSONA-OCM-003
    1.1. Senior Stakeholder / Sponsor UID: PERSONA-OCM-003 RELATIONS (Child): STATEMENT:

    Provides strategic oversight of organisational change initiatives and ensures alignment with enterprise priorities. Strategic rather than operational, limited time, focused on outcomes and impact. Requires concise information and influences direction and prioritisation.

     PRIORITY:

    Secondary

     TECH_COMFORT:

    Medium

     FREQUENCY:

    Weekly

     STATUS:

    Active
CONTENT-001
3.2.1. News Content Management UID: CONTENT-001 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: News BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request SOURCE_REF: US-SS-001 CURRENT_STATE: News and updates distributed via email with no central archive or structure. DESIRED_OUTCOME: Administrators can create, tag, schedule, and publish news content through the platform. RELATIONS (Parent): STATEMENT:

Platform must support creation and management of news content, including articles, images, tagging, categorisation, and scheduling.
CONTENT-002
3.2.2. OCM Toolkit Repository UID: CONTENT-002 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: OCM tools and templates scattered across email, file shares, and individual drives with no consistent structure. DESIRED_OUTCOME: Practitioners find categorised templates and guidance in one place, reducing preparation time significantly. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

Platform must provide a structured OCM toolkit with categorised templates and guidance to support implementation of change initiatives.
  • US-OCM-001
    2.1. Access OCM Toolkit and Templates UID: US-OCM-001 PERSONA: OCM Practitioner PERSONA_PRIORITY: Primary BUSINESS_VALUE: High STATUS: Accepted RELATIONS (Parent): STATEMENT:

    As an OCM Practitioner I want to quickly find relevant tools, templates, and guidance so that I can apply a consistent OCM approach without reinventing approaches across projects.

     ACCEPTANCE_CRITERIA:
    • Search functionality available with filters by category and topic
    • Relevant search results returned within 2-3 clicks
    • Resources found and downloadable in under 1 minute
    • Content structured and easy to browse
CONTENT-003
3.2.3. Cross-Entity Knowledge Sharing UID: CONTENT-003 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Accessibility BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Knowledge sharing between NATO entities is fragmented and not systematically captured. DESIRED_OUTCOME: Practitioners can browse and learn from structured examples and case-based content across NATO entities. RELATIONS (Parent): STATEMENT:

Platform must provide access to examples, practices, and case-based content from NATO entities to support knowledge sharing.
  • PERSONA-OCM-002
    1.3. Central OCM Team UID: PERSONA-OCM-002 RELATIONS (Child): STATEMENT:

    Designs, governs, and maintains the NATO Enterprise OCM approach and portal, ensuring consistency, quality, and scalability across entities. Responsible for enterprise-level OCM alignment. Owns methodology, tools, and governance. Balances strategic direction with practical usability and manages multiple stakeholders and priorities.

     PRIORITY:

    Primary

     TECH_COMFORT:

    Medium-High

     FREQUENCY:

    Weekly

     STATUS:

    Active
  • PERSONA-OCM-003
    1.1. Senior Stakeholder / Sponsor UID: PERSONA-OCM-003 RELATIONS (Child): STATEMENT:

    Provides strategic oversight of organisational change initiatives and ensures alignment with enterprise priorities. Strategic rather than operational, limited time, focused on outcomes and impact. Requires concise information and influences direction and prioritisation.

     PRIORITY:

    Secondary

     TECH_COMFORT:

    Medium

     FREQUENCY:

    Weekly

     STATUS:

    Active
  • PERSONA-OCM-004
    1.4. Network Participant (OCM Community of Interest) UID: PERSONA-OCM-004 RELATIONS (Child): STATEMENT:

    Participates in the OCM network alongside primary responsibilities, with an interest in staying informed and exchanging experiences. Not dedicated to OCM full-time, limited availability, selective in engagement. Values relevance and efficiency and prefers lightweight interaction.

     PRIORITY:

    Secondary

     TECH_COMFORT:

    Medium

     FREQUENCY:

    Weekly

     STATUS:

    Active
  • PERSONA-OCM-005
    1.5. HR / Training Representative UID: PERSONA-OCM-005 RELATIONS (Child): STATEMENT:

    Supports organisational change through training, people development, and capability building activities. People-focused role that supports but does not lead change. Works across multiple initiatives, needs structured guidance, and is involved in training delivery.

     PRIORITY:

    Secondary

     TECH_COMFORT:

    Medium

     FREQUENCY:

    Daily

     STATUS:

    Active
CONTENT-004
3.2.4. Network Update Publishing UID: CONTENT-004 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Reporting BABOK_CLASSIFICATION: Stakeholder Requirements REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Must Have BUSINESS_VALUE: High PHASE: Phase 1 - Go Live SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Updates shared via ad hoc email with no consistent format or central record. DESIRED_OUTCOME: Administrators publish concise updates once; all relevant user groups receive them through the platform. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

Platform must support publishing and sharing concise updates and key information to network users.
  • US-SS-001
    2.2. High-Level Progress Overview UID: US-SS-001 PERSONA: Senior Stakeholder / Sponsor PERSONA_PRIORITY: Secondary BUSINESS_VALUE: High STATUS: Accepted RELATIONS (Parent): STATEMENT:

    As a Senior Stakeholder I want to see high-level updates and key metrics related to the OCM initiative so that I can quickly understand progress and impact across NATO entities.

     ACCEPTANCE_CRITERIA:
    • Homepage displays key OCM-related updates and milestones
    • Critical announcements are highlighted
    • Content is concise and easy to scan
    • Ability to navigate to more detailed information if required
  • US-NP-001
    2.3. Concise Network Updates UID: US-NP-001 PERSONA: Network Participant (OCM Community of Interest) PERSONA_PRIORITY: Secondary BUSINESS_VALUE: High STATUS: Proposed RELATIONS (Parent): STATEMENT:

    As a Network Participant I want to receive concise updates and access key materials so that I can stay informed without investing significant time.

     ACCEPTANCE_CRITERIA:
    • Updates are concise and relevant
    • Clear structure of communication
    • Easy access to related materials
    • No information overload
CONTENT-005
3.2.5. Training Materials Library UID: CONTENT-005 STATUS: Proposed CLASSIFICATION: NATO UNCLASSIFIED CATEGORY: Content SUB_CATEGORY: Database BABOK_CLASSIFICATION: Solution Requirements - Functional REQUIREMENT_TYPE: Functional MOSCOW_PRIORITY: Should Have BUSINESS_VALUE: Medium PHASE: Phase 2 - Enhancements SOURCE_SYSTEM: Stakeholder Request CURRENT_STATE: Training materials exist in isolation per project with no shared library or consistent structure. DESIRED_OUTCOME: HR and training staff access a structured, reusable library of training materials aligned with OCM practices. RELATIONS (Parent): RELATIONS (Child): STATEMENT:

Platform must provide structured training materials aligned with OCM practices to support capability development.
  • US-HR-001
    2.4. Structured Training Materials UID: US-HR-001 PERSONA: HR / Training Representative PERSONA_PRIORITY: Secondary BUSINESS_VALUE: Medium STATUS: Proposed RELATIONS (Parent): STATEMENT:

    As an HR / Training Representative I want access to structured training materials so that I can support organisational change initiatives effectively.

     ACCEPTANCE_CRITERIA:
    • Training materials available centrally
    • Content structured by topic
    • Materials reusable and downloadable
    • Clear linkage to OCM approach