I would argue that one shoots him/herself in the foot if you start on a treasury technology project WITHOUT a business case done first.
Building the business case is sothing like creating a project initiation document and defines objective, scope effort/cost, benefit and assumptions. The business case will proof itself very useful along the journey of implementation, amongst others for these reasons:
- It creates (upfront) buy in from stakeholders
- It acts as a basic document for education and communication about the project
- It acts as a reference point for other to feedback (e.g. regarding handshakes with other processes and projects and dependencies)
- It established a framework / benchmark for KPIs to measure success
- It acts as a reference point in case material changes occur
- It may help explain underperformance if certain conditions have not been met
I believe a business case is a very useful document as it can be the north star of a project.
Listen also to the discussion I had recently on this with Andreas Gefnider as part of the TIS Payments Hub Podcast.