In this task you and other team members will review the following formula for implementation success.
How to Guarantee Success
Guarantee your success with self-implementation by following this simple formula:
1.Complete Tasks in Sequential Order
2.Perform Each Task to Full Completion
3.Do Not Skip Tasks
4.Do Not Rush Startup Day
5.Apply Time and Effort
1. Complete Tasks in Sequential Order
It is essential that you perform the tasks in the Startup Wizard in the exact order listed. This has three major benefits:
•You save time and get much better results when supporting tables are populated in correct order prior to importing or entering associated master tables.
•You achieve a “building block” effect where each task builds on the tasks that preceded it.
•Users learn the workflow structure because implementation task sets are performed in “Total Control” workflow order.
If you choose to work with a consultant
If you choose to work with a consultant, it is essential that you require the consultant to work within the Startup Wizard task structure and conforms to its sequential order and startup day activation.
2. Perform Each Task to Full Completion
It is essential that you perform each task to full completion before moving on to the next task.
Spending time now saves much more time later
Spending time now completing each task thoroughly and in full, no matter how long it takes, saves much more time later. This is because it is inefficient and much more time-consuming to perform setup tasks after-the-fact on a live system.
Three "super tasks" are the most time-intensive
Three "super tasks" may each require several days or even weeks to complete, but are absolutely required for the process workflow and cannot be skipped or partially completed.
•BOM Routings
•Locations Setup and Assignments
•Item MRP Settings
3. Do Not Skip Tasks
Never skip an implementation task unless it is clearly described as optional. Most optional tasks are minor in nature, such as sales reps and commission codes, but the vast majority consists of required tasks that must be completed to guarantee implementation success.
Total Control only works when all processes are fully deployed
DBA is not designed for partial control in which you can selectively use some processes and ignore others. It is a fully integrated system that only works successfully when all processes are fully deployed. Therefore, you cannot skip particular tasks because doing so will disable the process workflow.
Your users will become DBA experts
When each task is completed exactly as directed, by the time the final task is completed your users will be DBA experts who are thoroughly familiar with the system data structure and workflow processes.
4. Do Not Rush Startup Day
The final phase of self-implementation is to activate all workflow processes on a single system startup day. If you and your team have completed all tasks in sequential order, including all tasks in the rehearsal phase, you should be fully prepared for system startup day.
If any setup task is not fully completed or any users are not rehearsed and fully prepared to go live, postpone system startup day.
Startup day can occur on any calendar day
System startup day can occur on any calendar day during the year. It is not tied to the start of your fiscal year or any accounting period start date. Therefore there are no artificial time constraints to compel anyone to cut corners or take half measures to meet a deadline. It is wise to set a target date to motivate your team, but make it a flexible date that gets pushed back whenever any tasks are not yet fully completed.
5. Apply Time and Effort
If you follow the Startup Wizard to the letter and use the “building block” approach to prepare for system startup day, you cannot fail at self-implementation.
The only impediment to success is lack of effort. Apply time and effort to the steps above and your success is guaranteed.
Extra time must be allocated beyond normal activities
You must allocate extra time to the implementation project beyond the time it takes to perform normal everyday activities. Implementation will languish and fail to get completed unless management compels users to devote appropriate time to the project.
Consider weekly progress meetings
It is human nature to resist change and use normal workloads as an excuse not to devote time to the implementation project. You should expect this and make a plan to deal with it. We suggest that you have weekly progress meetings and hold people accountable for their progress.
