Free planning tool
Put a boundary around your workflow.
Already have a task in mind? Answer six questions about its systems and owners. You will get a suggested scope, unresolved approval points and a CSV to use in your build discussion.
0 of 6 answered
Choose one answer in each group. Your result appears below after all six.
Turn the outline into a testable scope
Review the outline with the workflow owner. Add the actual system names, allowed actions and people who handle exceptions. An assessment is optional, depending on the engagement.
How the scope rules work
Coverage and system count add zero, two or four points. Mixed records, partial approval rules and several exceptions each add two. Managed technical support adds one. Totals of zero to three suggest a contained workflow, four to eight a connected workflow and nine or more a broader scope. Missing records, approval rules, a normal path or an owner always produce an unresolved-boundary warning. These rules describe a starting scope. They have not been validated against build effort or production readiness.
Start here
Show us the workflow.
Tell us what starts it, who owns the result, which tools carry it, and where it stalls. We will tell you whether it is ready to map.
The workflow repeats
One person owns the result
The records exist
Several tools carry the work