¶01 What a green project status can hide
A NetSuite build can keep moving while unresolved decisions, testing and training accumulate behind a green status report. Check the substance of progress before go-live gets close.
Oracle’s Release Preview test plan is for upgrades to an existing account and includes a matrix and worksheets for testing business workflows. For a pre-go-live decision, apply the same discipline to a process your team has to run on day one. Ask the people who will use it to show the workflow and record what passed, what failed and who owns the next decision. See Oracle’s suggested test plan.
These five experience-based warning signs warrant investigation. None alone establishes failure, and there is no validated number of signs that diagnoses a project. Several unresolved together deserve a closer assessment.
¶02 Sign 1: Scope keeps expanding, but the timeline doesn't
New requirements are normal. The warning is repeated additions, such as integrations, saved searches or workflows, while budget and go-live remain fixed.
Check what has been deferred to phase two. Order-to-cash gaps, tax handling and core reporting may be necessary for phase one. Ask how each addition changes scope, testing, training or the date.
A scope change needs a visible decision. If the date and budget remain fixed, ask which other work is being replaced and who accepted the consequence. If nothing is removed, establish where the extra capacity comes from. Otherwise testing and training may absorb the pressure without an explicit decision.
¶03 Sign 2: Core process decisions are still open
Configuration should follow documented decisions on the chart of accounts, subsidiaries and consolidation, inventory, revenue recognition and integration flows.
If those are still being debated near go-live, late rework becomes likely. Ask for the agreed design decisions for your three or four core processes. “It is in the system” does not explain why the configuration was chosen.
¶04 Sign 3: Communication has gone thin or defensive
Watch for vague updates, risks that roll forward without resolution and reassurance that replaces answers. Ask what has been completed since the last report.
"Configuration 80% complete" three weeks running does not demonstrate progress without evidence of what has been completed.
Check unexplained changes to senior project staff and who now owns their decisions. A green status needs evidence underneath it.
¶05 Sign 4: Testing and data migration are still theoretical
Testing and migration are easy to defer when a build is late. Check completed evidence against this list:
Has the business, not just the partner, run real end-to-end transactions in a test account, using your own scenarios?
Has data been migrated into a test environment at least once, with the results reconciled against your existing system?
Do you have a written list of test cases tied to your actual processes, with pass/fail results, rather than ad-hoc clicking around?
Is there an agreed cut-over plan covering opening balances, in-flight orders, and what happens if something breaks on day one?
Has anyone defined what "good enough to go live" actually means, in measurable terms?
If most answers remain “planned” near go-live, revisit the date and readiness decision.
Ask to see the test cases and results, not only the test schedule. A migrated record count is useful, but it does not establish that opening balances reconcile or that orders pass through the intended process. Readiness should connect the evidence to the actual work the business must perform on day one.
¶06 Sign 5: Nobody has prepared the business to use it
The business needs role-based training, current process documentation and internal users who have practised in the system and can support colleagues.
Check whether training time is protected and whether finance and operations understand changed processes. Major changes introduced in the final week leave little time to practise or resolve adoption gaps.
Ask the people who will use the system to demonstrate their own role’s work. Have they practised the changed process, and do they know where to find instructions and support? A training appointment in the diary does not establish that this has happened. Record remaining gaps and who will address them before the readiness decision.
¶07 What to do if you recognise several of these
Assess unresolved signs together, especially near go-live. Compare the consequences of a planned delay with those of launching before core processes, data and users are ready.
An independent assessment should cover scope, design decisions, test results, migration reconciliation and business readiness. Use it to decide what must change and whether to proceed.
For risks that begin when systems are connected, see what to check before integrating NetSuite.
Basis for this piece
Five years inside a NetSuite consultancy, watching implementations from the marketing side of the same business. It is experience rather than a survey, and the warning signs are presented as experience rather than Oracle-published rules.
