Start with a business workflow
Choosing an application before defining the work makes it easy to reproduce the same problem in a new interface. Start with a transaction that crosses teams: an enquiry becoming an order, a purchase becoming available stock, or approved employee information becoming a payroll input.
Write down the current steps, the records involved and the points where somebody has to re-enter information or ask for clarification. Include unusual cases. Those examples make a more useful discovery input than a list of desired screens.
Agree who makes each decision
A project needs people who can approve the process as well as people who can configure it. Identify a business owner for finance, sales, stock, HR and reporting where those areas are in scope. Record who owns source data and who can approve a change to a shared record.
Make the approval route practical. If the project team cannot get a decision about a field, report or exception, configuration and testing will wait. Availability for workshops and user acceptance belongs in the delivery plan.
Choose an application mix and a boundary
Books, Inventory, CRM, People, Payroll, Creator and Analytics address different needs. Do not assume every application belongs in the first phase. Agree the workflow to be improved, the local editions needed and which existing systems will remain.
List each proposed connection with its source record, required information, owner and expected outcome. Treat custom development as a defined workstream with acceptance criteria, rather than an open-ended request to make the applications work together.
Prepare data before the first trial
Ask where customer, supplier, employee, item and accounting records currently live. Identify duplicates, missing fields and inconsistent codes. Decide how much transaction history is required and who approves the opening position.
Use trial loads to expose mapping problems. Reconcile counts, balances and representative records against the agreed source. Record issues and decisions so the final migration follows a controlled version of the process.
Define what ready means
Write test scenarios that follow actual business events, including rejection, correction and restricted access. Agree expected results and the person responsible for reviewing each scenario. A successful login is not a user-acceptance test.
Before cutover, confirm data approval, user access, training, open issues and escalation responsibilities. Your launch decision should be supported by evidence that the business can perform its essential work.
Bring a useful workshop pack
Prepare your current application list, sample transaction documents, approval matrix, reporting pack and data sources. Add the business outcome you want from the first phase and any timing dependencies that affect the operation.
Use this pack to discuss scope with an implementation partner. A good proposal should make deliverables, responsibilities, assumptions and acceptance visible—not simply repeat the names of the software products.
Put the guide to work.
Bring your current systems, sample records and priority workflow to a discovery discussion. We’ll help identify the decisions and preparation needed for your next implementation step.
Explore the delivery approach