The Method
The Method
Measure. Automate. Grow. A method for continuous improvement of business processes that starts from real work, introduces governed automation and turns verified results into capability, quality and growth.
Definition and promise
M.A.G. is a method for continuous improvement of business processes that starts from real work, introduces governed automation and turns verified results into capability, quality and growth.
The operating promise: make visible how work gets done, decide where to intervene, deliver the improvement and verify that it produces value over time.
Its natural field is recurring processes that cross people, documents, business systems, applications, integrations and AI. You can start from a single customer need: handling contacts collected at a trade show, assessing a technical case, approving an order, completing an onboarding.
FlowSharp is the reference implementation of the method: it connects the representation of the process to its execution and to the evidence of improvement. The method defines the questions, decisions and proof required; FlowSharp provides an environment in which to keep them connected during daily work.
The preference for FlowSharp rests on this verifiable continuity. The principles remain understandable to anyone who has yet to choose a platform.
The cycle: three phases
- Phase MMeasureHow do we work today, and where is it worth intervening?Three steps: Make visible; measure; choose.Outcome: Shared process, baseline and a reasoned priority.Open the phase
- Phase AAutomateHow do we build a better process that can be used every day?Three steps: Simplify; orchestrate; put into operation.Outcome: An operating improvement with controls, owners and active measures.Open the phase
- Phase GGrowWhat value did we obtain, and how do we make it last?Three steps: Verify; put value to use; replicate.Outcome: Documented results, use of the freed capacity and the next cycle.Open the phase
The cycle restarts from measuring the improved process. During Automate you keep measuring; during Grow you keep governing execution and exceptions.
What growth means
Grow covers three forms of growth:
- sustainable economic results;
- the ability to serve more customers, or serve them better;
- the organization's autonomy.
An increase in revenue remains a result to observe and explain: freed time alone does not prove it.
The units of the method
The unit of observation is the real case: a contact, an order, a file. The unit of governance is the process that manages its life cycle. The unit of change is the improvement initiative, linked to the process and to the original need.
This distinction makes it possible to follow both the customer's work and the consultant's work. The number of automations delivered is a delivery figure; the outcome of the cases handled is the evidence of the service rendered.
Responsibilities
Customer sponsor
- Role in the method
- Chooses the business objective, approves the investment and the use of the value obtained.
Process owner
- Role in the method
- Validates the map and baseline, accepts the operating process and verifies the results.
Operators and domain experts
- Role in the method
- Describe the work, test the solution, handle cases and report exceptions.
Consultant or partner
- Role in the method
- Leads the M.A.G. cycle, explains the choices, builds or coordinates the interventions and documents the evidence.
Technical service owner
- Role in the method
- Looks after integrations, availability, maintenance and problem handling.
| Responsibility | Role in the method |
|---|---|
| Customer sponsor | Chooses the business objective, approves the investment and the use of the value obtained. |
| Process owner | Validates the map and baseline, accepts the operating process and verifies the results. |
| Operators and domain experts | Describe the work, test the solution, handle cases and report exceptions. |
| Consultant or partner | Leads the M.A.G. cycle, explains the choices, builds or coordinates the interventions and documents the evidence. |
| Technical service owner | Looks after integrations, availability, maintenance and problem handling. |
Methodological roles
In small businesses one person may hold several responsibilities. These are methodological responsibilities: software permissions are configured separately, using the available roles and functions.
