BPMN and before and after
Take the map into your process tool as BPMN, and prove a change worked by running the same analysis again.
Export BPMN
Section titled “Export BPMN”On the Process page, in Classic view, select Export BPMN. You get a BPMN 2.0 process-diagram file with the layout included, so it opens as a diagram rather than a pile of boxes.
- The file contains the steps and arrows you can see. Set Map detail first: export the main flow for a clean diagram, or more detail for a full picture.
- In Subway view the button says Switch to Classic to export as BPMN.
- Use the file in any tool that reads BPMN 2.0, to document the current process or to start a redesign.
Import BPMN
Section titled “Import BPMN”To check work against a BPMN diagram, put the BPMN file in your folder and say: “Use this BPMN as the expected process.” The agent imports it and tells you about any part it could not use. See Check.
Before and after
Section titled “Before and after”The best proof that a change worked is the same analysis, run again on new data.
- Before. Your project keeps its current analysis. Note the numbers you care about, such as median time from invoice to payment.
- Make the change. Run the pilot for long enough to get a fair sample.
- After. Export the same data again, for the new period. Ask your agent to refresh the project with it.
- Compare. Ask your agent: “Compare the last two months with the two months before the pilot.” Or, on the Process page, open Measure time between steps, select Compare groups, choose two non-overlapping time periods (before and after), and read the difference.
Things to keep fair:
- Use the same filters for both periods.
- Leave out incomplete items, or the newer period will look faster than it is.
- A difference is not proof the change caused it. Different volumes, work mix or missing data can explain part of it. glasstarn says so next to every comparison.