Coordination, not just scheduling
Project management in an ERP implementation is sometimes reduced to maintaining a timeline. In practice, it's closer to coordination: keeping requirements, configuration, testing and client communication moving in sync, and catching when one workstream is drifting ahead of or behind another.
Managing sequence, not just tasks
ERP implementations have real dependencies — configuration can't start meaningfully before functional specifications are agreed, testing can't validate a workflow that isn't yet configured. Part of the project manager's job is making sure the sequence is respected, even under pressure to move faster.
Client communication as an ongoing task, not a milestone
Rather than treating client communication as a series of scheduled check-ins, it works better as a continuous thread — flagging decisions that need client input as soon as they arise, rather than batching them for the next meeting. This keeps small misunderstandings from becoming large ones.
Testing and UAT are project management responsibilities too
Coordinating user acceptance testing means more than scheduling a test window. It means making sure the right people test the right scenarios, that feedback is captured in a structured way, and that issues are triaged — not all feedback requires a configuration change, some requires user training instead.
Documentation as a project management deliverable
Keeping functional specs, configuration notes and testing checklists up to date isn't just administrative overhead — it's what keeps a project auditable and lets a new team member (or the client's own staff) understand a decision made months earlier.