Skip to main content
Large People ModelHuman Operating Architecture

Advanced practitioner depth

Layer 05 · Platforms · Platform Structure

Rationalization Roadmap

Executive summary

Create quarterly roadmap decisions for every tool and platform capability. This advanced practitioner guide places that work inside Platform Structure. It helps leaders turn a broad concern into a specific operating decision without treating the topic as a stand-alone transformation. Use the detailed model below to clarify the current state, make trade-offs visible, and assign ownership for the next move. Apply it when the platform inventory reveals duplication, obsolete systems, poor adoption, or capabilities needing redesign. The practical result is a rationalization roadmap classifying tools to retain, consolidate, deprecate, or redesign. Keep that output connected to adjacent layers so upstream constraints remain visible and downstream execution can show whether the design is working.

Use this when

the platform inventory reveals duplication, obsolete systems, poor adoption, or capabilities needing redesign.

Practical output

Leave with a rationalization roadmap classifying tools to retain, consolidate, deprecate, or redesign.

Detailed model

How to apply rationalization roadmap

Use the practitioner material below after the executive orientation establishes the job, trigger, and expected output.

Rationalization Roadmap

Every tool gets a quarterly operating decision.

Platform rationalization is not a one-time cleanup. It is a recurring decision system for retaining, consolidating, deprecating, or redesigning capabilities.

Roadmap Decision

Retain

The tool has clear purpose, ownership, domain fit, adoption, and workflow relevance.

Roadmap Decision

Consolidate

The tool overlaps with another capability and should be merged into a smaller platform footprint.

Roadmap Decision

Deprecate

The tool no longer has strategic or operational justification and should be removed on a timeline.

Roadmap Decision

Redesign

The platform capability is needed, but current ownership, workflow fit, data model, or integration design is wrong.

Choose the next path

Return to the layer or apply this topic to the operating model.

The layer overview restores context. The recommended action turns this practitioner model into the next piece of work.