With the drive to implement initial solutions quickly, it is often tempting to “keep things simple” by selecting and implementing solutions that are only capable of meeting the immediate or limited requirements.
Clearly tactical solutions of limited scope and or capability have their place. If nothing else, they may be the only practical way to meet short term legislative deadlines in some cases.
We have experienced several instances where initially selected tactical solutions become the company standard by default over time, despite the fact that these solutions were not originally selected for a broader capability and or geographical scope. This often creates significant issues to subsequent implementations which could have been avoided.
We therefore recommend resisting the temptation to rush into implementing short term tactical solutions wherever possible. Where this is necessary, some mechanism should be put in place to review their suitability in the face of expanding requirements and allow switches to more appropriate solutions if necessary in a timely manner.
I hope you enjoyed this installment on Things we wish we had known before starting a serialisation program or project. Please check back in next week for the continuation in this series.
Should you have any questions about this or any other of my blogs, or would simply like to request a copy of my booklets, please don’t hesitate to contact me at Andrew.firstname.lastname@example.org.
Available for request: