Skip to content
RESET Enterprise architecture team ES Contact us

Home / Columns / Enterprise Reset / Process design

Enterprise Reset · Process design

Meetings that exist only to transfer information.

Processes grow by adding steps, rarely by removing the ones that no longer serve a purpose. We design the flows that sustain daily operations, with an explicit owner for each one.

Contact us

The challenge

Processes no one designed, everyone inherited.

An organization's processes rarely get designed all at once. They accumulate, one step at a time, whenever something went wrong and someone added a control. Years later, no one remembers why a step exists or who is responsible for reviewing it.

The result is predictable: meetings that exist only to transfer information that should flow on its own, and processes that survive because no one has the mandate to redesign them.

What's included

Flows with an owner, not inherited steps.

The flows that sustain daily operations, with explicit owners and no steps that exist just because they always have.

Each process gets documented with its real sequence, where it starts and ends, and the person responsible for keeping it current as the operation changes.

How we work

Operating architecture in action.

Enterprise Reset operates as RESET’s operating-architecture system. Process design follows the same method as the rest of RESET: review, evaluation, solution, execution, and traceability.

Other columns

Other systems in the operating model.

Close

What needs a RESET in your operating processes?

Describe the problem in context. A team lead will review the message and define the next step.

Contact us