Enterprise ITSM & ServiceNow Workflow Design
Turning service requirements into workflows, access rules and testable acceptance criteria.
- Context
- Academic/personal solution design, separate from BMO
- My role
- Requirements, workflow and solution design; test planning
- Status
- Design and prototype release plan completed
- Deliverable
- Process maps, user stories, access rules and acceptance criteria
Decision & evidence
Make approval a testable gate
Routing, access and approvals need to agree with the process requirement. The walkthrough below makes the approval state explicit so that a test can distinguish a valid handoff from premature fulfillment.
Designed scope: forms, routing, script logic, integrations and release packaging. The public walkthrough illustrates that design; it is not a deployed ServiceNow application.
Illustrative design walkthrough · fictional access request
From request to verified fulfillment
- 1Request
Capture requester, service and business justification.
- 2Validate
Check required fields and requester permissions.
- 3Approve
Record an authorized approver’s decision.
- 4Route
Create a fulfillment task only after approval.
- 5Verify & close
Record completion evidence and notify the requester.
Acceptance criterion
Given a valid request awaiting approval, when an authorized approver approves it, then one fulfillment task is created for the assigned group and the approval decision is recorded. Rejection creates no fulfillment task; a repeated approval must not create a duplicate.
- Approved → one task
- Rejected → no task
- Unauthorized approver → denied
- Repeated approval → no duplicate
Overview
Mapped As-Is and To-Be ITSM workflows and designed a ServiceNow solution covering data, forms, service-catalog concepts, routing, approvals, notifications and reporting.
Objective
Translate service-management requirements into a coherent solution design with clear acceptance criteria, controlled access and a testable prototype implementation approach.
My contribution
- Mapped current-state and future-state workflows and designed tables/forms, routing, approvals, notifications and role-based access.
- Defined reporting and dashboard requirements, JavaScript business-rule / client-script logic, and REST API integration points.
- Created user stories, acceptance criteria, test cases and defect-remediation steps.
- Defined an update-set and release approach for a prototype implementation.
Technical approach
- Connected workflow requirements to platform concepts, making the relationship between process steps, data and access explicit.
- Used user stories and acceptance criteria to guide test cases, then defined how prototype changes would be packaged and released.
Scope & considerations
Role-based access, approval ownership, testability and release discipline are part of the solution design. This academic / personal work is separate from the operational dashboard built at BMO.
Outcome
Demonstrates ServiceNow and ITSM solution design, workflow automation concepts, requirements analysis, integration planning and structured testing.