Architect a People Management System

Flow · 6 controlled steps

1. 01

   Frame the system and architecture decision

   Establish the actual system problem rather than beginning from a preferred program or tool.

   • — Resolve the PMS-NN identity and accountable sponsor.
   • — State required business/workforce outcomes, affected populations, decisions, constraints, consequence, and time horizon.
   • — Identify qualified-review requirements and explicit non-goals.
   • — Define architecture acceptance and stop conditions.

   Responsible

   People-system architect

   Output

   System Architecture Charter

   Decision

   Is system architecture the right level of intervention?

2. 02

   Diagnose the current system

   See how policy, process, practice, roles, data, systems, controls, measures, and interfaces behave together.

   • — Trace representative work and decisions end to end.
   • — Inventory formal and informal policies, processes, practices, roles, records, technologies, controls, measures, variants, and exceptions.
   • — Map upstream/downstream contracts and qualified specialist interfaces.
   • — Identify current outcomes, friction, failure modes, workarounds, risks, strengths, and uncertainty.

   Responsible

   People-system architect

   Output

   Current System Model · Architecture Problem Statement

   Decision

   Is the current-state evidence sufficient to design the target architecture?

3. 03

   Define target purpose and operating model

   Set coherent design direction before specifying components.

   • — Define target purpose, outcomes, principles, service boundary, populations, variants, ownership, and decision rights.
   • — Choose client, Lock, shared, partner, and system operating responsibilities.
   • — Define required experiences, risk posture, economics, capability, capacity, and transition assumptions.
   • — State what the system will not do.

   Responsible

   Executive system sponsor

   Output

   Target System Profile · Target Operating Model

   Decision

   Does the target operating model fit strategy, context, authority, resources, and professional boundaries?

4. 04

   Architect components and interfaces

   Specify how the complete mechanism must fit together.

   • — Define required policies, processes, practices, roles/capabilities, data objects, systems/integrations, controls, measures, feedback, and governance.
   • — Map inputs, outputs, decisions, services, records, and failure handling across connected systems.
   • — Classify components as retain, improve, redesign, build, buy, partner, automate, or retire.
   • — Identify shared components and context-specific variants.

   Responsible

   People-system architect

   Output

   Target System Architecture · Connection and Component Register

   Decision

   Is the proposed architecture complete, internally consistent, and connected?

5. 05

   Evaluate options and establish the roadmap

   Convert architecture into an executable, risk-aware sequence.

   • — Assess gaps, dependencies, economics, risks, readiness, technical constraints, capacity, and change burden.
   • — Define design and implementation increments that deliver coherent capability.
   • — Sequence policy, process, practice, role, data, system, control, measure, and partner work.
   • — Define validation, acceptance, rollback, ownership, and measurement for each increment.

   Responsible

   People-system architect

   Output

   System Gap and Roadmap · Investment Decision

   Decision

   Which roadmap delivers the needed capability with acceptable risk and dependency?

6. 06

   Transfer and govern the architecture

   Keep downstream work coherent and update architecture through controlled learning.

   • — Issue component design charters and connection requirements.
   • — Establish architecture decision, exception, version, and review governance.
   • — Review downstream proposals for fit and cross-system impact.
   • — Update the architecture only through evidence, authority, and versioned rationale.
   • — Transfer accepted capability into system-health review.

   Responsible

   People-system architect

   Output

   Design Charters · Architecture Decision Record · Versioned System Architecture

   Decision

   Does downstream design or learning require an architecture decision?

Connections

Seams · 10 hops within 2 steps

Upstream and downstream neighbourhood over public reference processes only. Each hop shows the trigger, carried objects, and what the receiving process loses if the producing step is skipped.

Roles

Systems + Data

Measures

Evidence + judgment

Draft horizontal method. Validate through one complete PMS-NN demonstration and practitioner/system architecture review before publication.