Why are roles and permissions important?

Roles and permissions are how NetSuite controls what functions or records a user can or can't access.  A role is defined as a compilation of permissions or restrictions; permissions and restrictions are usually given around the functional role of each user.  Each user is granted access to NetSuite with a specific role(s).  From an administration point of view, permissions can be changed at a role level instead of for each individual user, making it easy to manage permissions for groups of users.

A great way to reduce manual efforts is to use the standard Electronic Bank Payments function in NetSuite.  Instead of manually entering in the ACH payments in your bank's interface, you can generate a standard NACHA file that can be uploaded to your bank. This is a free and easy bundle installation and setup.  

In my experience, people generally hate to escalate. Many team members think escalation is snitching on a fellow team member or will reflect bad on their own performance.  To a project manager, escalation is just another method of communication; it's how we can foresee and manage situations, and all projects have "situations" that impact scope, budget, or time.

Yup, you read it correctly.  NetSuite is offering access to free training videos. This may be for a limited time due to COVID-19.  Take advantage while you can.

Congratulations! You just bought NetSuite and are now ready to implement. 

You can create child project records or subprojects in NetSuite. The concept is very similar to child customers.  Most customers that use this feature have projects with large scopes and want to break it down into manageable bites.  For instance, creating of a new product involves design, development, and marketing - all of which have their own subset of tasks. 

Regardless if you are on time and on budget, people make or break a project.  What I’m going to discuss today is not managing scope and change orders, but rather managing changes that team needs to go through.

As humans, we are creatures of habit. When new systems are brought in, it requires the systems adopters to not only to learn a new system, but also change their processes. If change is not properly managed, a seemingly smooth project can be easily thrown off the tracks.  

In any project, models or mock ups are the best way for Client’s to validate and communicate with the Project Team.  Written requirements and use cases are a great start and the next best step is to be able to see the functionality.  As a Project Manager, I have seen plenty of situations where Client’s expectations were not met, and development was already completed. This often results in frustration and wasted work.

Project management is both a science and an art form. There are many project management methodologies and tools out there to help a project manager, but without the human touch, you are less likely to be successful in pushing your projects through on time, on schedule, and within budget.  A good project manager is how efficient and effective they are at getting things done. However, there are many project managers who go through the motions without the “people” aspect that really makes a project manager successful.