---
title: "Rollout Design (Site, Function, Process)"
description: "How to choose the rollout structure for your organization"
canonical_url: "https://meingpt.com/en/docs/rollout-guide/rollout-design"
language: en
---

# Rollout Design (Site, Function, Process)

The key rollout question is usually not "which model", but "which rollout structure".

## Option 1: Site-based

Best if:

- plants/countries operate differently
- local systems and data pools dominate
- change is led by site leadership

Risk:

- duplicate effort for similar use-cases

## Option 2: Function-based

Best if:

- functions like sales, service, HR are fairly standardized
- use-cases are reusable across teams
- central templates are beneficial

Risk:

- local differences are addressed too late

## Option 3: Process-based

Best if:

- processes cross multiple teams (for example quote-to-order)
- integrations must span functions
- end-to-end impact is the priority

Risk:

- coordination overhead increases

## Recommended default: Hybrid

1. Start with 1-2 functions (fast outcomes)
2. Roll out by site using proven patterns
3. Deepen 1-2 end-to-end processes in parallel

## Practical rule

If the organization is under strong pressure to "decide and execute", start with more standardization and reduce initial custom scope.

## Next pages

- [Rollout Phases](/en/docs/rollout-guide/rollout-phases)
- [Tailoring Playbook](/en/docs/rollout-guide/tailoring-playbook)
- [Selection Learnings](/en/docs/rollout-guide/selection-learnings)