Beyond Spreadsheets: Choosing the Right Business Systems

Welcome. In this lesson, we will explore recognising the trigger for change.

Separate a genuine system need from a desire for new software.

Look for repeated entry, conflicting versions and fragile approvals. Define the business impact of the current limitation. Consider whether a process improvement can solve the issue first.

Spreadsheets remain useful for analysis and small controlled tasks. The trigger for a new system is a recurring business limitation that process discipline cannot reasonably solve. Quantify rework, delayed decisions and control failures where possible. Consider simpler improvements first, then define the scope of a system evaluation around the remaining problem.

Consider this example. A finance team merges six spreadsheets every month and repeatedly corrects inconsistent customer codes. The decision begins with the cost and control impact of that work.

Pause here and try this activity. List three spreadsheet problems. For each, describe the business impact and an alternative process improvement.

Here is one possible response. Three problems: duplicate customer codes delay consolidation; conflicting price lists create corrections; emailed approvals lack a clear status. First standardise codes, define one price owner and clarify approval rules. Evaluate a shared system if coordination and traceability still cannot meet the business need.

Before moving on, think about this question. Which is the strongest reason to evaluate a shared business system? The best answer is: Repeated data conflicts and control gaps affect operations. A business impact provides a stronger basis for investment than fashion or presentation.

Welcome. In this lesson, we will explore requirements that describe the work.

Write requirements in terms of outcomes and constraints.

Describe a business scenario, the user and the required result. Separate essential needs from preferences. Include access, reporting, integration and data migration needs.

Write a requirement that a vendor can demonstrate and a user can accept. Include the actor, event, rule and expected evidence. Distinguish business necessity from a preferred way of implementing it. Include exceptions, permissions and integration needs. Keep a reference number and owner so the requirement can be traced through demonstration, scope and testing.

Consider this example. Instead of requiring a particular screen layout, a buyer asks for approval by value, traceable changes and a clear urgent-order exception.

Pause here and try this activity. Write five requirements. Mark which ones are essential and explain why.

Here is one possible response. REQ-01: when a purchase request exceeds the agreed threshold, route it to an authorised approver and retain the decision history. Acceptance: an unauthorised user cannot approve; approval and rejection are recorded; an approved deputy can act under the agreed policy.

Before moving on, think about this question. Which requirement is most useful for evaluation? The best answer is: It must support value-based approvals with an audit trail. A specific, testable requirement helps vendors demonstrate the needed capability.

Welcome. In this lesson, we will explore the selection team.

Include the people who understand operations and implementation constraints.

Name a decision owner and a business process owner. Include users, finance and technical representation as appropriate. Agree how conflicting requirements will be resolved.

Define who recommends, who decides and who can veto a failed mandatory requirement. Ask users to bring concrete scenarios rather than personal feature wish lists. Finance evaluates cost assumptions, IT checks integration and security, and process owners assess practical fit. Resolve conflicts before vendor scores are combined, and retain a written decision record.

Consider this example. Finance favours reporting depth while operations needs reliable stock transactions. A cross-functional team agrees priorities before comparing vendors.

Pause here and try this activity. Identify the people who should evaluate your next system and the decisions each person can make.

Here is one possible response. Sponsor: approves investment and resolves priorities. Operations owner: validates stock and fulfilment scenarios. Finance: checks controls and cost. IT: assesses integration, access and support. Users: run task demonstrations. The team records mandatory gaps and recommends an option with conditions.

Before moving on, think about this question. Who should participate in selecting a cross-functional system? The best answer is: Relevant business users, decision-makers and technical representatives. A cross-functional team helps evaluate the system against real work and constraints.

Welcome. In this lesson, we will explore demonstrations with evidence.

Evaluate vendors using comparable business scenarios.

Give each vendor the same priority scenarios. Ask to see exceptions, corrections and role permissions. Record evidence and gaps instead of relying on impressions.

Ask vendors to show a transaction end to end using the same sample data. Record whether each capability is demonstrated, configured, custom, third-party or unproven. A roadmap promise is not a delivered capability. Compare evidence using agreed criteria, and follow up unresolved gaps in writing before treating them as included scope.

Consider this example. Two vendors demonstrate the same order-to-cash scenario, including a partial delivery and a credit note. Evaluators score the evidence independently before discussion.

Pause here and try this activity. Prepare a demonstration script with one normal transaction and one exception.

Here is one possible response. Scenario: receive a sales order for ten units, deliver six, invoice the delivered quantity and handle a return. Test role permissions and trace the documents. Score only what was shown; list any work promised for later as an unresolved gap with an owner.

Before moving on, think about this question. What makes vendor demonstrations easier to compare? The best answer is: Using the same business scenarios and scoring criteria. Common scenarios make functional differences and gaps more visible.

Welcome. In this lesson, we will explore fit, risk and total cost.

Compare the complete commitment rather than the licence price alone.

Include implementation, migration, training and ongoing support. Distinguish standard features, configuration and custom development. Check references, data export and contractual responsibilities.

Use the same term, users, entities and transaction assumptions for every proposal. Separate one-off and recurring costs, and show uncertainty for custom work. Check who owns maintenance, upgrades, data export and exit support. An aggregate score must not hide failure of a mandatory control. Clarify exclusions before comparing headline totals.

Consider this example. One proposal has lower licence fees but requires extensive custom work. The team compares several years of operating costs and the responsibility for maintaining changes.

Pause here and try this activity. Build a comparison with cost, fit, delivery risk and exit considerations.

Here is one possible response. Illustrative three-year comparison: setup RM20,000 plus subscription RM1,000 per month plus support RM500 per month totals RM74,000 before tax and other costs. Add migration, internal time, integrations, upgrades and contingency where relevant. These are exercise figures, not market prices.

Before moving on, think about this question. Which proposal comparison is most useful? The best answer is: Total cost, functional fit, delivery risk and support obligations. The full commitment includes implementation and operating risks as well as software fees.

Welcome. In this lesson, we will explore a controlled transition.

Plan how people and data will move to the chosen system.

Clean and validate essential data before migration. Use role-based training and realistic acceptance tests. Agree cutover, fallback and post-launch support arrangements.

Treat go-live as an evidence-based business decision. Define acceptance criteria, unresolved-issue severity, migration reconciliation and a cutover owner. Specify when to pause or roll back and how to reconcile transactions created during transition. Arrange named support and a review after launch. A pilot reduces uncertainty, but later branches still need readiness checks.

Consider this example. A company pilots one branch, validates opening balances and checks real transactions before expanding. Named support owners handle early issues.

Pause here and try this activity. Draft a go-live checklist with data, users, testing, support and a decision owner.

Here is one possible response. Go-live evidence: sample end-to-end tests accepted, opening balances reconciled, role access confirmed, users practised, support contacts available and cutover steps rehearsed. The sponsor signs the decision after reviewing open issues. A fallback trigger and reconciliation owner are recorded before switching.

Before moving on, think about this question. What should be agreed before go-live? The best answer is: Data validation, user readiness, cutover and support arrangements. A controlled transition needs verified data, prepared users and clear operational arrangements.