Department of Health Tasmania – Change Management solution + migration

Overview

Designed and delivered an Ivanti Change Management solution, including migration from a legacy platform, aligned to practical governance and approval controls. Partnered closely with the BA function to shape requirements that were implementable and scalable in Ivanti.

Platform: Ivanti · Focus: Change Management + migration + reporting · Engagement: Design-to-delivery implementation

The situation

Change needed stronger structure, visibility, and auditability, with a safe migration path from the legacy approach and minimal disruption to BAU operations. Requirements also needed to be translated into a design that fit Ivanti’s capabilities (and avoided recreating legacy complexity).

What I delivered

  • Change Management solution design aligned to risk, approvals, and governance
  • Worked with the BA to produce Ivanti-fit requirements, user stories, and implementation-ready acceptance criteria
  • Configuration build and rollout support through to go-live
  • Migration approach and execution support for moving from legacy platform behaviour
  • Reporting enablement to support operational visibility and compliance oversight

Approach

  • Design-first: confirm change categories, approval logic, and control points before build
  • Translate requirements into Ivanti-native patterns to reduce custom debt and improve supportability
  • Build for BAU: clear forms, states, approvals, and reporting outputs
  • Migration planned with operational safety in mind (cutover steps, validation checks, rollback thinking)

Outcomes

  • Controlled and auditable Change process ready for BAU
  • Improved visibility of change status, approvals, and compliance through fit-for-purpose reporting
  • Reduced manual overhead and ambiguity in change handling
  • Smooth migration to the new tool with minimal disruption to BAU operations

Key decisions and design choices

  • Designed a tool-fit Ivanti solution (using out-of-box patterns where possible) rather than recreating legacy behaviour through heavy customisation
  • Defined clear change categories, risk signals, and approval guardrails before build to avoid rework and inconsistent processing
  • Structured requirements with the BA into implementation-ready user stories and acceptance criteria that mapped cleanly to Ivanti capabilities

What this enabled next

  • All change captured in a single system of record with clear guardrails and auditability
  • Reliable reporting and visibility to support continuous improvement and compliance oversight

Tools and capabilities

Ivanti Change Management, workflow/approvals, requirements shaping (BA partnership), migration planning and cutover support, reporting enablement.

If you’re tackling something similar

If your Change process is inconsistent, overly manual, or hard to govern, I can help you translate requirements into a practical, tool-fit design and deliver a clean migration that improves control without slowing delivery.

Start the conversation

Scroll to Top