WORKFLOW DESIGN AND QA 360 DIGITAL ACADEMY | FREE STARTER WORKSHEET Time: 60 minutes Outcome: A workflow brief, test plan, and launch decision. Name / team: ____________________ Date: ____________________ 1. UNDERSTAND AND ASSESS Choose one automation. Document the intended behavior before building it. Use a safe test environment or approved test records, and prevent unintended customer messages or production changes during testing. Key idea: Enrollment determines who enters. Re-enrollment determines whether someone can enter again. Branches and delays change the path. Exit and suppression rules prevent inappropriate actions. Inspect related automations for conflicts. Example: Route a consultation request only when the request is valid and an owner can be assigned. Missing territory follows an exception route to an operations owner. A repeat submission follows an explicit duplicate-handling rule. What event starts this workflow, and what result should it produce? Your response: __________________________________________________ Which records are eligible, excluded, or allowed to re-enter? Your response: __________________________________________________ Who owns approval, ongoing monitoring, and incident response? Your response: __________________________________________________ 2. BUILD YOUR WORKING PLAN Write expected outcomes before testing Add one case for every branch and external action. Include timing, time zone, owner availability, and failure handling. Verify final record values and notifications, not just whether the workflow ran. Test scenario | Input / starting state | Expected action / exit | Actual result / evidence Eligible record | __________________ | __________________ | __________________ Ineligible record | __________________ | __________________ | __________________ Missing required value | __________________ | __________________ | __________________ Each branch / delay | __________________ | __________________ | __________________ Repeat entry / update | __________________ | __________________ | __________________ Suppressed record | __________________ | __________________ | __________________ What other workflows or integrations write to these same fields? Your response: __________________________________________________ What happens if an action fails, an owner is unavailable, or a record changes during a delay? Your response: __________________________________________________ How will we pause the process and repair affected records if behavior is wrong? Your response: __________________________________________________ 3. VALIDATE AND TAKE ACTION [ ] Enrollment, re-entry, exclusions, and exits are written clearly. [ ] Every branch and external action has passed an approved test. [ ] Test sends and changes cannot reach unintended recipients. [ ] Circular updates and conflicting automations have been checked. [ ] Evidence, unresolved defects, approval, and launch time are recorded. [ ] A monitoring owner and a practical recovery plan are assigned. Measure what changes: Track exceptions and incorrect actions / eligible executions during the pilot. Review actual affected records. Pausing automation does not undo actions already completed. Our baseline / target / source / review date: ______________________ Suggested implementation rhythm Before launch: resolve critical defects and record the approver. At launch: use a limited approved cohort and inspect results. After launch: review the first cycle and schedule recurring checks. First action / owner / due date: __________________________________ Open issue / decision / approver: _________________________________ Practical education by 360 Marketing Solutions | 360digitalacademy.us