Reference implementation
Apply the method with FlowSharp
M.A.G. requires continuity between need, process, real work, improvement decision and result. FlowSharp already has objects that can be linked along this path, documented in the guides.
What already exists
Understand the process and external work
- Existing FlowSharp support
- Process Maps, manual nodes, systems and documents, Procedures and flowcharts.
- Usable evidence
- Shared map and instructions, distinction between operational and represented steps.
Observe real cases
- Existing FlowSharp support
- Flows, items, tasks, statuses, outcomes and history.
- Usable evidence
- What happened, who owns the next step, times and exceptions.
Establish the starting point
- Existing FlowSharp support
- Analytics, KPIs, configured costs and Process Map baseline.
- Usable evidence
- Measures for the period, declared estimates and a reference snapshot.
Assess and choose interventions
- Existing FlowSharp support
- Candidates, What-if and Implementation Plan / Automation Backlog.
- Usable evidence
- Origin, expected saving, investment, assignment and initiative status.
Build the future process
- Existing FlowSharp support
- Human tasks, rules, AI, webhooks, events, APIs and MCP.
- Usable evidence
- Activities and exchanges with internal or external performers within the configured scope.
Prepare for operation
- Existing FlowSharp support
- Versions, publication checks, permissions, blocking tasks, timeouts and error recovery.
- Usable evidence
- Published definition, configured controls and execution history.
Verify the improvement
- Existing FlowSharp support
- Initiative verification, KPIs and Saving Challenge when enabled.
- Usable evidence
- Comparison with the baseline, origin of values and consolidated periods.
Consolidate and replicate
- Existing FlowSharp support
- Versioned procedures, flow templates, export, separate organizations and assigned access.
- Usable evidence
- Reusable configurations, handovers and work per customer.
| Method need | Existing FlowSharp support | Usable evidence |
|---|---|---|
| Understand the process and external work | Process Maps, manual nodes, systems and documents, Procedures and flowcharts. | Shared map and instructions, distinction between operational and represented steps. |
| Observe real cases | Flows, items, tasks, statuses, outcomes and history. | What happened, who owns the next step, times and exceptions. |
| Establish the starting point | Analytics, KPIs, configured costs and Process Map baseline. | Measures for the period, declared estimates and a reference snapshot. |
| Assess and choose interventions | Candidates, What-if and Implementation Plan / Automation Backlog. | Origin, expected saving, investment, assignment and initiative status. |
| Build the future process | Human tasks, rules, AI, webhooks, events, APIs and MCP. | Activities and exchanges with internal or external performers within the configured scope. |
| Prepare for operation | Versions, publication checks, permissions, blocking tasks, timeouts and error recovery. | Published definition, configured controls and execution history. |
| Verify the improvement | Initiative verification, KPIs and Saving Challenge when enabled. | Comparison with the baseline, origin of values and consolidated periods. |
| Consolidate and replicate | Versioned procedures, flow templates, export, separate organizations and assigned access. | Reusable configurations, handovers and work per customer. |
This integration is the criterion by which FlowSharp becomes the best application of the method: a consultant must be able to trace from the result to the case, to the process and to the decision that changed it, at a sustainable cost of collecting and maintaining evidence.
Existing capabilities
The table describes objects already present in the guides. It is not a full acceptance test of the product, nor a demonstration of results.
Distinctions to preserve in the implementation
- The Backlog code already distinguishes
liveandverified. The method completes this base with customer acceptance, quality criteria and periodic review. A change of status alone does not certify value. - Verifying an initiative and the monthly Saving Challenge calculation have different scopes and formulas. The M.A.G. report must declare which measure is used; the initiative's saving does not automatically equal the overall economic return.
- The current
hardandcapacitylabels in the Saving Challenge distinguish components derived from flows from estimated ones. M.A.G. also needs to distinguish the economic effect: a measured component alone does not prove a reduction in actual spending. - Representing an external system on the map does not automatically measure all of its activities. The project must set up the information returns needed. An approval in FlowSharp controls the external action only if the integration respects that constraint.
- Publication checks and governance functions support testing the process; testing with operators and with connected services remains part of the delivery.