Organization and capability: Two target states for CREM
Many CREM transformations begin with an organizational chart. Decision rights are shifted, services are bundled or outsourced, and new roles are defined.
Whether the organization then actually performs its tasks better often remains unclear. This is because the organizational design and professional capability are two different dimensions of a CREM target state.
The Ambition Designer therefore consistently distinguishes between target configuration and target maturity.
Target configuration: How should CREM be organized?
The target configuration profile describes the desired organizational design of CREM. It defines, among other things:
- Decision rights,
- mandate,
- service depth,
- user autonomy,
- sponsorship.
This determines, for example, which tasks are performed centrally or decentrally, which services remain in-house, and which are outsourced.
The future role of CREM is also defined: should the function primarily provide operational services, manage across functions, or be involved early in corporate decisions as a strategic partner?
These decisions determine the structure and scope for action of the organization. However, they do not yet indicate whether CREM has the necessary competencies, data, and processes.
Target maturity: What must CREM master?
The target maturity profile describes which capabilities CREM needs for its future role, the pressure for change, and the risk profile.
This includes in particular:
- strategy and governance,
- defined and robust processes,
- portfolio and space transparency,
- data and financial competence,
- service and provider management,
- operator responsibility,
- ESG reporting capability.
Not every capability area needs to be developed to the highest possible level. The required degree of maturity depends on the pressure for change, the desired value contribution, the risk profile, and the role CREM is to assume in the future.
A heavily outsourced organization, for example, requires strong client and management competence. A decentralized model needs clear minimum standards, reliable data, and effective overarching governance. A strategically positioned CREM requires stronger portfolio, financial, and analytical capabilities.
Two typical mistakes
The separation of configuration and maturity prevents two typical misdevelopmentsThe first is a reorganization without capability building. Roles, responsibilities, and reporting lines are changed while the necessary capabilities, data, and management tools are lacking. The organization then looks different, but in substantive terms it still works largely as before.
The second is a capability program without governance clarification. Processes, systems, or data models are improved even though mandate, decision rights, and responsibilities remain unclear. The developed capabilities can then only have a limited effect.
A new organizational chart does not create maturity. At the same time, a capability program cannot replace structural clarity.
A robust ambition combines both profiles
The Ambition Designer does not automatically prescribe how far CREM must develop. It structures the conscious management decision on role, organizational form, and required capabilities.
This defines:
- which role CREM is to assume in the future,
- how the organization is designed,
- which capabilities are required for this,
- which target levels are realistic and meaningful,
- and which limits or conscious trade-offs are part of the ambition.
The target configuration can be decided. Target maturity, by contrast, does not arise from a decision, but must be developed deliberately.
Only when both profiles are aligned does a CREM target state emerge that is organizationally plausible and professionally robust.
Configuration is decided. Maturity is developed deliberately.