Final | October 2018 | v1.0.0 | OFFICIAL-Public | QGCDG


Roadmaps assist the agency to transition from development to implementation of a digital or ICT vision and target state architecture. Roadmaps are abstract plans for business, information or technology change, operating across multiple disciplines over multiple years. They provide a graphic visualisation of the potential activities, capabilities and outcomes required to support the agency’s digital or ICT strategic direction and vision.


A practitioner in the context of this guideline can include one or more of the following roles:

  • Digital or ICT strategic planners
  • Agency and service strategic planners
  • Enterprise architects
  • Information managers.


Sharing and collaborating on a roadmap with stakeholders, including representatives from the business provides visibility of different perspectives and enhances the co-design process. Adopting this co-design approach also improves the chances of choosing an optimal pathway. The development of roadmaps can be achieved using a workshop approach.

Depending on the planning objectives identified in the Initiate workstream, more than one roadmap may be required.

The timeframes included in roadmaps should reflect the timeframe of the strategic document to which it relates, however a greater level of abstraction may occur in the outer years of the roadmap.

There is no single template for a roadmap, however common elements on a roadmap visualisation include:

  • details of potential work packages, solutions or deliverables including a name and description or domain
  • identification of the dependencies or relationships between the work packages, solutions or deliverables
  • demonstration of how the implementation of the work packages, solutions or deliverable will contribute to the incremental achievement of outcomes and delivery of benefits
  • workstream or swim lanes.

Roadmaps should not just depict the technology changes required, although these are the most commonly accepted or identifiable roadmaps. Roadmaps can include details relating to:

  • business or organisational changes required
  • changes to the way information is created, used, shared or managed
  • changes required to deliver strategic changes in the workforce including the reskilling of staff or the recruitment or sourcing of staff
  • changes required to bring about the application and technology target state architecture
  • a summary of the timing and estimated level of investment required.

These themes can be represented as workstreams or swim lanes or as separate roadmaps.

The development of roadmaps is iterative and my need to undergo several rounds of consultation in accordance with the communications plan developed in the Initiate workstream.

It is recommended practitioners seek the assistance of marketing and communications specialists within the agency to conduct an editorial review and assist with the overall presentation of roadmaps.

Next steps

All strategic documents and roadmaps should be endorsed by the planning sponsor. For agency wide strategic documents and roadmaps, it may be necessary to seek approval from the executive officers of the agency including the Director General or equivalent. Where a public launch of the strategic documents including roadmaps is proposed, Ministerial approval may also be required.

Roadmaps will form the basis for the development of initiative proposals.




Tips for effective technology roadmaps

Video - Five tips for effective technology roadmapping

Guide to roadmapping

Video - Guide to roadmapping

Last Reviewed: 24 October 2018