1. Agree the outcome before the product
Start with a concrete business problem. “We need a new system” describes a solution; “staff enter the same customer details into three tools” describes something you can investigate.
Write down who is affected, where the problem happens and what would change if it were resolved. Decide how you will judge success. A measure might be the number of duplicate entries, the time from request to approval or the proportion of requests returned for missing information. Establish a baseline if the data is available.
Do not promise a percentage improvement before understanding the process and measuring its current performance.
A useful starting statement
“Our service team re-enters customer details when transferring work to delivery. We want one agreed customer record and a hand-off that does not require re-keying. We will assess whether duplicate entries and correction requests fall after the change.”
2. Understand how work happens today
A system rarely operates in isolation. Follow a real request from its starting point to completion. Include the people, spreadsheets, emails, approvals and systems used along the way. Ask the people doing the work where exceptions occur and which informal workarounds keep it moving.
- Who starts the process, and what information do they provide?
- Which steps require a decision or approval?
- Where is information copied, checked or corrected?
- What happens when a request is incomplete or unusual?
- Who owns the process when it crosses teams?
Bring example forms, reports and anonymised records. Remove personal or confidential details before sharing them. Process improvement consulting can help turn this evidence into current- and future-state maps.
3. Define what the system must do
Separate essential needs from preferences. A feature list is more useful when each item has a business reason, an owner and a way to check whether it works.
For example, “approval workflow” is broad. A clearer requirement describes which requests need approval, who can approve them, what information they must see, and what happens when the approver is unavailable.
Include acceptance criteria
An acceptance criterion might be: “When a complete request is submitted, the assigned approver can review the required fields and record an approval or return it with a reason; the requester can see the resulting status.” Real criteria should reflect your business rules.
Also discuss non-functional requirements: access permissions, performance during busy periods, availability, accessibility, auditability, reporting, support and relevant security or privacy expectations. Bring specialist advice into the project where needed.
Business analysis consulting helps organise these needs into prioritised requirements, user stories and testable acceptance criteria.
4. Prepare data and integration questions
List the information the system needs and where it comes from. Identify a data owner who can explain definitions and resolve issues. Check for duplicates, missing values and inconsistent formats before planning a migration.
- Which records need to move, and which should be retained elsewhere?
- Which system is the source of truth for each important field?
- Which systems need to exchange data, and how often?
- What happens if an integration fails or information does not match?
- Who validates migrated records and confirms reconciliation?
Do not assume an integration exists because two products advertise that they connect. Confirm the exact data, direction, frequency, limits and responsibilities with the relevant providers during evaluation.
5. Agree scope, ownership and decision points
Name the business sponsor, process owner, delivery lead and the people responsible for accepting the solution. Agree who can change scope and how new requests will be assessed.
Record the constraints that affect options: budget, timing, contract renewals, team availability and dependencies on other initiatives. Distinguish a genuine deadline from a preferred date.
A staged approach can keep decisions manageable. For example, discovery may establish requirements before vendor evaluation, with a separate decision on implementation after the options and costs are understood. Digital transformation consulting can help connect these stages into a practical roadmap.
6. Plan testing and adoption early
Testing should show that the solution supports the way your business needs to work. Ask users to help define realistic scenarios, including exceptions and relevant access roles. Connect test scenarios to the agreed requirements.
Plan who will train users, update procedures, provide support and make the final readiness decision. Discuss cutover, contingency arrangements and how issues will be handled after launch. These plans should be proportionate to the system and operational impact.
Once the change is in use, revisit the measures agreed at the start. A system can be technically live while the underlying process still needs attention.
7. Bring a practical discovery pack
You do not need every answer before seeking help. Gather the following items and mark the gaps so the first conversation can focus on the decisions that matter.
System implementation preparation checklist
- A short problem statement and intended business outcomes.
- The affected teams, decision owners and process owners.
- A current workflow sketch, including exceptions and hand-offs.
- Example forms, reports and anonymised records.
- Essential requirements and known business rules.
- Data sources, owners and integration questions.
- Budget, timing and external dependencies.
- Initial testing, training and readiness responsibilities.
- Baseline measures and a plan for reviewing outcomes.
- Open questions, assumptions and decisions still to be made.
For a first engagement, this pack provides a starting point rather than a fixed specification. The discovery work should validate the assumptions and identify what needs further investigation.
Related guides: Business Analyst Services in New Zealand, Digital Transformation Consultant NZ and Process Improvement Consultant NZ.
Talk to Krypton Digital about your system initiative. We support discovery, requirements and planning in Auckland and online across New Zealand.