Choose business systems around the decisions people make

List the activities that matter most and who carries them out. For finance, that might include preparing budgets, comparing forecasts, reviewing workforce assumptions and tracking capital projects. Other teams may depend on the same information in different ways.

Choose a few representative scenarios and describe the required result. A scenario is more useful than a broad requirement such as “easy reporting”. For example, ask how a manager would compare an approved budget with a revised staffing assumption and explain the difference to the people responsible for a decision.

A central business application rarely works alone. Teams may use spreadsheets and specialist tools to fill gaps. Record what each supporting tool does, who uses it and which information must move between systems.

Avoid assuming every additional tool should disappear. Some have a clear purpose and work well. Others duplicate records or create fragile handovers. The aim is to understand the whole operating picture before comparing improvement options, rather than treating replacement of the main product as an automatic solution to every surrounding problem.

An options assessment can include improving the current arrangement, replacing selected functions or undertaking a broader change. Test each option against the same practical scenarios, required capabilities and dependencies.

Include implementation effort, staff training, ongoing maintenance and the ability to retrieve useful information. A lower headline price does not settle the decision if essential work is excluded. Equally, a large feature list does not prove that the organisation needs every feature. Make the assumptions visible so decision-makers can understand what the comparison does and does not establish.

Identify which information needs to move, how it will be checked and which team can confirm it is fit for use. Work through the effect on reporting cycles and day-to-day services. A staged approach may allow the organisation to test an important function before changing the rest.

For budgeting tools, the finance team must validate accounting treatment, policy and any formal reporting obligations. Project staff can support requirements and testing, but professional approval belongs with the people authorised to make those decisions.

The first useful outcome may be an agreed scope rather than a purchase or build. A requirements catalogue, options paper and tested scenario prototype can give the organisation a stronger basis for deciding what to do next.

If implementation proceeds, define the first usable stage and the evidence needed to accept it. Include the people who will maintain the system after launch. A clear roadmap explains how the organisation moves from today’s work to the proposed arrangement, including what will stay in place during the transition.

Explore our Business systems, ERP and financial planning, related services and Map your applications before planning a replacement.