Requirements describe screens, not the process
Requests are captured feature by feature, without showing how work should pass between teams. We clarify the process, exceptions, ownership and decision rules.
ERP & PROJECT DELIVERY
When processes, data ownership or go-live conditions are unclear, technical implementation alone will not solve the problem. I help define a specific part of an ERP change, connect operational requirements with project delivery and prepare practical evidence for the next decisions.
WHEN SUPPORT HELPS
The purpose is not to take over an entire programme or replace the implementation partner. We focus on one stage or workstream where leadership decisions, process knowledge and supplier delivery need to come together.
Requests are captured feature by feature, without showing how work should pass between teams. We clarify the process, exceptions, ownership and decision rules.
Master-data preparation, test scenarios and sign-off move back and forth between the internal team and supplier. We clarify responsibilities, dependencies and completion criteria.
The project records many tasks, but their impact on operations and go-live is unclear. I help sort them by dependency, risk and the decision they actually require.
POSSIBLE SCOPE
Scope is agreed around a specific decision and the evidence available. It may cover:
APPROACH
We agree the process or workstream, people involved, available material and the decision the assignment needs to support. Items outside the project are stated explicitly.
We examine process requirements, the plan, open items, data and test material with the responsible people. Supported facts are separated from assumptions.
We connect tasks to their operational impact, identify the decisions required and propose owners and control points across the company and supplier.
The output summarises priorities, dependencies, decision points and completion criteria. Implementation or support for the selected stage can be agreed as a separate project.
DELIVERABLES
The exact deliverables reflect the project stage and quality of available information. They may include:
A clear link between process steps, roles, exceptions and the system capabilities needed in the selected area.
Open questions, proposed owner, decision timing and impact on dependent work.
Practical readiness criteria and the evidence needed to show that agreed work is complete.
Next steps, dependencies, risks and control points for the internal team and implementation partner.
START WITH ONE STAGE
Briefly describe the system, project stage, open issue and the outcome you need. We can define a useful scope for a consultation or a small project.