 <h1>Congratulations! 🎉 </h1>
    <p style="color:#637381;">All done! You’ve completed another milestone.</p>

To continue, enter your details to log in.

We’ve sent a 6‑digit code to #MAIL_ADDRESS#\nPlease check your inbox or spam folder and enter the code below to continue.

Verification code sent

Thank you for the payment. You can now access {collectionName} by simply clicking the button below.

Yes, you’ve successfully ordered! 🎉

Unlock This Exclusive Course

It seems that your email address is not currently on the authorized access list. Please ensure you are using the email address that was invited, or contact the content owner for assistance.

Verification Required for Access

Increase your
 Manufacturing Velocity (tm)

1) - Why do GAPS happen? 
No software package is likely to fulfill all your requirements. 
This alone leaves Gaps of functionality that may be critical to your business.
Gaps and errors in the implementation of ERP systems can happen for a number of reasons.
1.	There is some needed functionality that the program does not have or
2.	The user doesn’t know how to use it.
In any case, if the system lacks a capability that is needed or if it is not being used correctly then gaps can occur.
We should also consider that, from a human interaction perspective, there might be some training needs as well as an incomplete understanding of what your ERP software can do. For example, if someone with limited knowledge on how to use ERP were to train someone else without basic knowledge on how to use these tools then they would likely not be using them in the correct way and gaps would happen as well.
2) - Identify the GAPS
Paper documents, spreadsheets and private databases may indicate GAPS
Many companies and professionals still use paper documents and spreadsheets to keep track of their tasks and deadlines. This makes it difficult to collaborate on projects with other people, as well as manage responsibilities from different offices.
•	Personal databases are usually not sophisticated enough for the needs of your organization. They often do not cover all the needs that a company has, such as complex workflows or managing multiple teams.
•	There are also many software packages which cannot integrate with one another - for example, a CRM system cannot import data from a project management system - making data input time consuming and laborious to maintain.
3) - Plan your Transition
A planned approach is critical
In this section, we will cover how to identify gaps that most impact the velocity of your business. It is important to be honest with yourself about where you need to improve so you can work on those areas correctly.
The first step
Identify gaps in your knowledge and skills resulting from lack of training and list them in the data-flow order of your ERP software.
The second step
Understand which gaps (not resulting from lack of training) are most responsible for slowing the velocity of your business or being filled by substitutes such as:
•	Spreadsheets
•	Paper Documents
•	Personal Databases
•	Other software not integrated with your ERP package
The third step
Analyze and produce the integration of the gap substitutes above in the order of “best bank for the buck” and in the order of the data-flow of your ERP software.
4) - Execute Your Transition Plan
Execution based on data flow is paramount
Rank gaps according to which one is the most urgent and act on that one first.
Lastly, we can identify what resources are required to close that gap and execute our plan.
5) - Document Your Results and Learnings
Document each GAP from it's original state to it's final state
One common mistake that GAP participants make is that they do not document the process of their transition. They fail to record what they learned, what went well and what didn't go as planned. This provides a valuable lesson to the next iteration of continuous Gap improvement


Increase your Manufacturing Velocity (tm)