Skip to content
Operating System
Lock reference · Draft
v0.1.0

Redesign Work and Workflow

Redesign how work moves before adding capacity, automation, or organizational complexity.

Adopt · export.mdAdopt · export.jsonDraft reference — not a fitted standard

Profile

Purpose

Create a controlled future-state workflow that improves an explicit operating outcome while preserving necessary quality, safety, regulatory, and human guardrails.

Intended outcome

An approved and tested workflow specification with clear ownership, interfaces, controls, measures, systems changes, and a transition plan.

Accountable
Business process owner
Operator
Process architect
Use when
  • — A workforce decision identifies redesign or automation as part of the response.
  • — Handoffs, queues, rework, exceptions, or unclear decisions impede delivery.
  • — A process depends on tribal knowledge or a single person.
  • — A systems implementation would otherwise automate an undefined workflow.

Entry gate

  • The work, customer, operating outcome, and accountable owner are identified.
  • The scope boundaries and triggering need are explicit.
  • People who perform and receive the work can participate.

Exit gate

  • The future-state workflow, decisions, roles, interfaces, controls, data, and systems are approved.
  • Baseline, outcome, quality, cycle-time, adoption, exception, and guardrail measures are defined.
  • A pilot or proportionate validation shows the workflow can operate.
  • Transition ownership, training, support, rollback, and review points are assigned.

Flow · 6 controlled steps

  1. 01

    Frame the outcome and design criteria

    Make the reason for redesign and the conditions of a good solution explicit.

    • — Name the customer and outcome the workflow must produce.
    • — Set scope boundaries, demand profile, constraints, and assumptions.
    • — Define success, quality, safety, regulatory, human, cost, and timing criteria.
    • — Record the current baseline and consequence of no change.
    Responsible
    Business process owner
    Output
    Design Brief
    Decision
    Is the problem worth solving and bounded well enough to redesign?
  2. 02

    Map the current flow

    Make actual work, decisions, waits, interfaces, data, systems, and exceptions inspectable.

    • — Observe and map representative work from trigger to outcome.
    • — Record inputs, outputs, roles, decisions, handoffs, queues, rework, exceptions, controls, and systems.
    • — Separate the documented process from actual practice.
    • — Validate the map with people who perform and receive the work.
    Responsible
    Process architect
    Output
    Current-State Workflow Map · Exception and Interface Log
  3. 03

    Diagnose constraints and causes

    Find where the mechanism fails instead of treating every visible symptom as the problem.

    • — Compare the current flow with each design criterion.
    • — Locate bottlenecks, failure demand, unclear decisions, duplicate entry, unmanaged interfaces, and control gaps.
    • — Distinguish common process causes from isolated events or individual variation.
    • — Prioritize causes by effect on the stated outcome and guardrails.
    Responsible
    Process architect
    Output
    Constraint and Cause Assessment
    Decision
    Which causes must the future state change to produce the intended outcome?
  4. 04

    Design and compare future states

    Generate coherent alternatives before committing to a favored tool or structure.

    • — Remove unnecessary work, decisions, approvals, transfers, and duplicate data.
    • — Clarify ownership, decision rights, interfaces, exception paths, and escalation.
    • — Allocate work among people, systems, automation, and external parties.
    • — Compare alternatives against design criteria, implementation effort, risk, and reversibility.
    • — Specify measures and signals needed to operate each viable design.
    Responsible
    Process architect
    Output
    Future-State Options · Recommended Workflow Specification
    Decision
    Which future-state design best satisfies the full set of criteria?
  5. 05

    Validate and authorize the design

    Test the mechanism at proportionate scale before irreversible implementation.

    • — Walk representative normal, edge, failure, and recovery cases through the design.
    • — Prototype or pilot high-uncertainty elements where practical.
    • — Obtain risk, quality, safety, regulatory, data, and systems review appropriate to context.
    • — Resolve defects and record approval, conditions, version, and decision authority.
    Responsible
    Business process owner
    Output
    Approved Workflow Specification
    Decision
    Is the future state operable, controlled, measurable, and safe enough to implement?
  6. 06

    Transition, measure, and improve

    Put the workflow into operation without losing control of the old-to-new passage.

    • — Assign implementation work, readiness criteria, training, communications, support, and rollback.
    • — Connect systems and publish the authoritative workflow and operating materials.
    • — Monitor outcome, quality, cycle time, adoption, exceptions, and guardrails against baseline.
    • — Stabilize defects, review assumptions, and route material redesigns through version control.
    Responsible
    Process architect
    Output
    Operational Workflow · Performance and Improvement Record
    Decision
    Has the new workflow met the stabilization and outcome criteria?

Connections

Seams · 16 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.

downstream · hop 1

Open process

Design and Validate a Recurring Human Practice

Trigger · An approved or candidate workflow depends materially on a recurring human interaction.

Carries · Workflow Specification · Practice Design Need

If the handoff from Redesign Work and Workflow is skipped, Design and Validate a Recurring Human Practice loses Workflow Specification · Practice Design Need.

downstream · hop 1

Open process

Implement a Business System

Trigger · The approved workflow requires system configuration, integration, or automation.

Carries · Approved Workflow Specification

If Validate and authorize the design is skipped, Implement a Business System loses Approved Workflow Specification.

downstream · hop 1

Open process

Select a Business System

Trigger · The approved design requires a new system or material replacement decision.

Carries · Approved Workflow Specification

If Validate and authorize the design is skipped, Select a Business System loses Approved Workflow Specification.

upstream · hop 1

Open process

Approve Workforce Need and Headcount

Trigger · The approved response includes redesigning, reallocating, stopping, or automating work.

Carries · Workforce Decision · Capacity and Capability Assessment

If Assess capacity and capability is skipped, Redesign Work and Workflow loses Workforce Decision · Capacity and Capability Assessment.

upstream · hop 1

Open process

Architect a People Management System

Trigger · The roadmap authorizes workflow or operating-process design.

Carries · Design Charter · Target System Architecture

If Architect components and interfaces is skipped, Redesign Work and Workflow loses Design Charter · Target System Architecture.

upstream · hop 1

Open process

Design and Govern a People Policy

Trigger · Policy implementation requires a new or revised operating process.

Carries · Approved Policy Version · Policy Operating Map

If Design policy and operational architecture; Review, test, and approve the policy is skipped, Redesign Work and Workflow loses Approved Policy Version · Policy Operating Map.

upstream · hop 1

Open process

Discover and Synthesize Process Evidence

Trigger · The evidence packet is accepted for synthesis.

Carries · Process Evidence Packet · Synthesis Handoff

If Transfer to synthesis and improve discovery is skipped, Redesign Work and Workflow loses Process Evidence Packet · Synthesis Handoff.

upstream · hop 1

Open process

Manage Team Capacity and Priorities

Trigger · Capacity review identifies work or process design as a material cause.

Carries · Capacity and Priority Review · Improvement Handoff

If Review outcomes and improve capacity design is skipped, Redesign Work and Workflow loses Capacity and Priority Review · Improvement Handoff.

upstream · hop 1

Open process

Operate and Improve a Process

Trigger · The redesigned workflow meets stabilization criteria.

Carries · Operational Workflow · Performance and Improvement Record

If Transition, measure, and improve is skipped, Operate and Improve a Process loses Operational Workflow · Performance and Improvement Record.

upstream · hop 1

Open process

Review Manager-System Health

Trigger · The diagnosis identifies work or process design as a material cause.

Carries · Improvement Handoff

If the handoff from Review Manager-System Health is skipped, Redesign Work and Workflow loses Improvement Handoff.

downstream · hop 2

Open process

Build and Operate a Development Plan

Trigger · Development is an approved response to a capability finding.

Carries · Development Handoff

If the handoff from Review Manager-System Health is skipped, Build and Operate a Development Plan loses Development Handoff.

downstream · hop 2

Open process

Define Role and Success Profile

Trigger · Response type is Employee role or a combination containing Employee role.

Carries · Workforce Decision · Business Need

If Frame the business need is skipped, Define Role and Success Profile loses Workforce Decision · Business Need.

downstream · hop 2

Open process

Establish the Manager Operating Role

Trigger · A health-review point or material signal occurs.

Carries · Manager Operating Charter · Manager Role Health Review

If Approve and launch the operating charter; Review role health and adapt is skipped, Review Manager-System Health loses Manager Operating Charter · Manager Role Health Review.

upstream · hop 2

Open process

Enable Decisions and Escalation

Trigger · The review examines manager and team decision conditions.

Carries · Decision Outcome Review · Decision-System Improvement Record

If Review outcome and improve decision flow is skipped, Review Manager-System Health loses Decision Outcome Review · Decision-System Improvement Record.

upstream · hop 2

Open process

Onboard the New Hire

Trigger · The manager accepts transition to normal operation.

Carries · Onboarding Transition Record · Improvement Inputs

If Transition to normal operation and improve is skipped, Operate and Improve a Process loses Onboarding Transition Record · Improvement Inputs.

upstream · hop 2

Open process

Run the Team Operating Cadence

Trigger · The review assembles manager-system evidence.

Carries · Cadence Health Review

If Review and improve the cadence is skipped, Review Manager-System Health loses Cadence Health Review.

Roles

Business process owner

Owns the operating outcome, tradeoffs, approvals, and sustained performance.

Process architect

Operates the redesign method and maintains coherence across workflow, ownership, systems, controls, and measures.

People who perform the work

Provide operating reality, test alternatives, and validate usability.

Upstream and downstream owner

Defines and accepts the contracts at process boundaries.

Systems owner

Tests feasibility, data integrity, integration, automation, access, and support.

Risk, quality, or safety owner

Sets required controls and approves relevant changes within their authority.

Systems + Data

Data object

Design Brief

Controls the outcome, scope, baseline, constraints, and design criteria.

System of record · Process repository

Data object

Workflow Specification

Defines the future operating mechanism.

System of record · Process repository

Data object

Performance and Improvement Record

Connects observed operation to controlled changes.

System of record · Measurement and improvement system

Versioned process repository

Required

Stores maps, specifications, ownership, controls, connections, and change history.

Workflow event or operational data

Required

Provides demand, time, quality, exception, and outcome evidence at proportionate granularity.

Workflow or case-management system

Contextual

May execute and instrument the workflow after the mechanism is defined.

Integration and automation layer

Contextual

Moves data or performs decisions only where requirements and exception handling are controlled.

Measures

outcome

Operating outcome

Is the redesigned workflow improving the outcome named in the Design Brief?

The context-specific outcome measure, compared with its baseline and interpreted with other influences made explicit.

At the natural operating interval

quality

First-pass quality

How often does work meet the receiving specification without correction?

Items accepted at the defined exit gate without rework divided by all items reaching the gate.

Weekly or monthly

cycle-time

End-to-end cycle time

How long does demand take to become the intended outcome?

Elapsed time from defined trigger to accepted exit, with work and wait time separable where feasible.

Weekly or monthly

adoption

Workflow adoption

Is the approved workflow being used?

Eligible work following the controlled workflow version divided by all eligible work.

During transition; then monthly

exceptions

Exception demand

Where and why does work leave the normal path?

Exception events by type, cause, step, and disposition per unit of demand.

Weekly during stabilization; then monthly

guardrail

Human and operating risk guardrail

Did the redesign shift cost or risk into workload, safety, quality, privacy, or customer harm?

Context-specific review of workload, overtime, safety, quality, privacy, accessibility, customer complaints, and control failures.

At each transition review

Evidence + judgment

The Five Milestone Design Process

source-derived

Supports business-case discovery, explicit design criteria, integration mechanisms, transition planning, measurement, and adjustment.

bicycle-guide · build-a-people-analytics-function · the-five-milestone-design-process

Strategic HR Process Maturity Framework

source-derived

Supports current-state assessment, target-state definition, gap analysis, roadmapping, implementation, and measurement.

bicycle-guide · tool-strategic-hr-process-maturity-framework · build-a-people-analytics-function.artifact.json

Business-outcome measurement loop

cross-source-synthesis

Supports beginning with critical business outcomes, checking measure ownership and quality, implementing, measuring impact, and iterating.

bicycle-guide · six-step-process-of-implementing-hr-analytics · build-a-people-analytics-function.artifact.json

Embedded analytics and automation in operational workflow

cross-source-synthesis

Supports embedding decisions in workflow while recognizing that automation also scales failures and therefore requires measurement and controls.

bicycle-guide · analytics-craft-and-delivery · embedded-analytics-and-automation

Lock situational design principle

lock-judgment

Lock judgment: workflow design must fit the company’s strategy, work, values, systems, capabilities, budget, and constraints.

lock · what-lock-is

Lock inspectable-process principle

lock-judgment

Lock judgment: a process must make actual workflow, ownership, decisions, data, systems, controls, measures, and connections inspectable.

lock · lock-method

Lock whole-system redesign principle

lock-judgment

Lock judgment: recurring operating failures are diagnosed across the mechanism rather than assigned reflexively to individual people.

lock · what-lock-is

Lock connected-process design principle

lock-judgment

Lock judgment: interfaces, data, systems, measurement, and feedback are designed objects rather than seams left to operators.

lock · what-lock-is

Draft reference standard. Requires practitioner and context-specific systems, risk, quality, safety, regulatory, and worker-impact review before client deployment.