The importance of road-maps

Maybe our kids' might be lucky to see flying cars, but today we still have cars, that drive on roads and as a result we often need to refer to a map to know how to get to our destination.

Similarly, if you are involved in any sort of projects work, or working on a transformation project that is likely to run beyond 12 months, you will almost certainly need to reference an IT road-map, or systems road-map, or a data-migration road-map etc.

Good operators will almost always create one and will proactively own and update;
- as and when projects complete milestones,
- or when a change in direction is required due to some unforeseen circumstances or opportunities, risks etc.

Unfortunately there are many projects out there that don't have road maps defined.
- This means, there is no long-term vision on what the organisation is trying to achieve.
- In systems projects, a road-map can greatly assist with the sequencing of integrations, what systems to bring online first and which ones to decommission as required.

For BAs, and those who are keen to get into solution architecture,
- Put up your hand to help create one if you don't already have one
- Proactively work with SMEs and project leads, have that those discussions and workshops

A road map is your guide and a key reference source for what it is you are trying to achieve.