Why Change Management Matters

ERP implementations fail more often due to people issues than technology issues. Users who don't understand why the change is happening, weren't involved in decisions, or feel threatened by new systems will resist adoption—consciously or unconsciously.

Change Management Framework

The ADKAR model provides a useful framework for managing change.

Stakeholder Analysis

Stakeholder Categories

Executive Sponsorship

Active executive sponsorship is the single most important success factor. "Active" means visible, ongoing participation—not just signing off on the budget.

Executive Sponsor Responsibilities

• Communicate the "why": Explain strategic importance to the organization
• Remove obstacles: Clear roadblocks, resolve conflicts, prioritize resources
• Model behavior: Use the system, attend training, demonstrate commitment
• Celebrate wins: Recognize successes publicly
• Address resistance: Handle escalations with appropriate authority

Change Champions Network

Change champions are respected employees who advocate for the new system within their teams. They're not necessarily managers—often peer influence is more powerful.

Champion Selection Criteria

• Respected by peers (not just management favorites)
• Open to change (but not blindly positive)
• Good communicators
• Understand current processes well
• Willing to invest extra time

Champion Responsibilities

• Attend additional training sessions
• Provide feedback on training materials and processes
• Answer peer questions during and after go-live
• Report adoption issues to project team
• Celebrate and share team successes

Handling Resistance

Communication Plan

Training Principles

Effective NetSuite training isn't about teaching the software—it's about teaching people how to do their jobs using the software. This distinction matters.

Role-Based Training Plan

Different roles need different training. A one-size-fits-all approach wastes time and frustrates users who sit through irrelevant content.

Training Curriculum Structure

Train-the-Trainer Approach

For larger organizations, training internal trainers is more scalable and sustainable than having consultants train every user.

When to Use Train-the-Trainer

• More than 50 end users
• Multiple locations or shifts
• High turnover requiring ongoing training
• Budget constraints on consultant time

Internal Trainer Selection

• Subject matter expertise in their area
• Comfort presenting to groups
• Patience with varying skill levels
• Respected by peers
• Available for training development time

Train-the-Trainer Program

Training Materials Development

Delivery Methods

Training Schedule Planning

Session Structure

Effective training sessions follow a structured format with the key ratio being 60-70% hands-on, 30-40% instruction.

Hands-On Exercise Design

Exercise Principles

• Realistic scenarios: Use actual business situations, not abstract examples
• Progressive difficulty: Start simple, add complexity
• Safe environment: Sandbox where mistakes don't matter
• Clear instructions: Written steps users can reference
• Built-in validation: Users can verify they did it correctly

Sample Exercise Structure

EXERCISE: CREATE A SALES ORDER
═══════════════════════════════════════════════════════════════

SCENARIO:
Customer "ABC Company" calls to order:
  - 10 units of Item SKU-001 at standard pricing
  - 5 units of Item SKU-002 with 10% discount
  - Requested ship date: [2 weeks from today]
  - Ship to their warehouse address (on file)

STEPS:
1. Navigate to: Transactions > Sales > Enter Sales Orders
2. Select customer "ABC Company"
3. Add line items as specified
4. Apply discount to SKU-002 line
5. Set requested ship date
6. Verify ship-to address
7. Save the order

VERIFICATION:
Your order number should start with "SO-"
Order total should be approximately $X,XXX
Status should show "Pending Fulfillment"

CHALLENGE (if time permits):
The customer calls back to add 3 units of SKU-003.
Edit your order to add this line.

Reinforcement Techniques

Post-Training Reinforcement

• Daily tips: Email one NetSuite tip per day for first two weeks
• Office hours: Scheduled drop-in time for questions
• Buddy system: Pair experienced users with newer ones
• Quick wins: Assign simple real transactions immediately
• Gamification: Recognize power users, track adoption metrics

Documentation Types

User Guide Structure

Quick Reference Cards

Quick reference cards are desktop aids for common tasks. They should be scannable at a glance.

Quick Reference Card Design

• One page: Front and back maximum
• Top 5-10 tasks: Only the most common
• Numbered steps: Brief, action-oriented
• Navigation paths: Menu → Submenu → Option
• Visual cues: Icons, color coding
• Laminated: Durable for desk reference

Video Tutorials

Video Production Guidelines

• Length: 2-5 minutes maximum per video
• Scope: One task or concept per video
• Audio: Clear narration, minimal background noise
• Screen: Clean desktop, zoom to relevant areas
• Pacing: Slow enough to follow, but not tedious
• Captions: Include for accessibility

Recommended Video Tools

• Loom: Quick recording, easy sharing
• Camtasia: Professional editing, zoom effects
• Screencast-O-Matic: Simple, affordable
• OBS Studio: Free, powerful (steeper learning curve)

Knowledge Base Setup

A searchable knowledge base becomes the long-term home for all documentation and FAQs.

Knowledge Base Structure

KNOWLEDGE BASE ORGANIZATION
═══════════════════════════════════════════════════════════════

HOME
├── Getting Started
│   ├── Login and Security
│   ├── Navigation Basics
│   └── Personal Preferences
│
├── By Process Area
│   ├── Order to Cash
│   │   ├── Sales Orders
│   │   ├── Invoicing
│   │   └── Payments
│   ├── Procure to Pay
│   │   ├── Purchase Orders
│   │   ├── Receiving
│   │   └── Vendor Payments
│   ├── Inventory
│   └── Finance
│
├── By Role
│   ├── Order Entry
│   ├── Accounts Receivable
│   ├── Warehouse
│   └── Administrator
│
├── FAQs & Troubleshooting
│   ├── Common Errors
│   ├── How Do I...?
│   └── Who Do I Contact?
│
└── Video Library

Knowledge Base Platforms

• Confluence: Popular, integrates with Jira
• SharePoint: If already using Microsoft 365
• Notion: Modern, flexible, affordable
• Document360: Purpose-built knowledge base
• NetSuite File Cabinet: Simple option, limited search

Documentation Maintenance

Maintenance Schedule

Documentation Ownership Model

• Assign owners by functional area: Finance docs owned by Controller, Sales docs by Sales Manager, etc.
• Central coordinator: One person tracks versions, sends review reminders, maintains the knowledge base structure
• User feedback loop: Every document should have a "Was this helpful?" mechanism or a way to submit corrections
• Version control: Date-stamp every document, maintain a changelog, archive old versions

Support Transition

The support model evolves from intensive post-go-live hypercare to steady-state operations. Planning this transition prevents gaps and user frustration.

Support Tier Structure

Escalation Paths

ESCALATION FLOW
═══════════════════════════════════════════════════════════════

USER HAS ISSUE
      │
      ▼
┌──────────────────────────────────────────────────┐
│ Check Knowledge Base / Documentation             │
│ Can you find the answer?                         │
└──────────────────────────────────────────────────┘
      │                              │
     YES                            NO
      │                              │
      ▼                              ▼
  RESOLVED              ┌──────────────────────────┐
                        │ Ask Change Champion      │
                        │ / Power User             │
                        └──────────────────────────┘
                              │              │
                             YES            NO
                              │              │
                              ▼              ▼
                          RESOLVED  ┌──────────────────────────┐
                                    │ Submit Support Ticket    │
                                    │ (Internal Admin)         │
                                    └──────────────────────────┘
                                          │
                                          ▼
                                    ┌─────────────┐
                                    │ Can Admin   │
                                    │ resolve?    │
                                    └─────────────┘
                                     │         │
                                    YES       NO
                                     │         │
                                     ▼         ▼
                                 RESOLVED  ESCALATE TO
                                           TIER 2/3
            

Internal Admin Role

A capable internal NetSuite administrator is essential for long-term success.

Admin Responsibilities

• User Management: Create users, assign roles, manage access
• Basic Customization: Custom fields, lists, saved searches
• Report Creation: Build and maintain reports
• Issue Triage: First-line support, escalation decisions
• Release Management: Test new releases, communicate changes
• Vendor Coordination: Work with partner and NetSuite support

Admin Time Requirements

Ongoing Enablement

Post-Go-Live Training

• New hire onboarding: Standard training program for new employees
• Role changes: Cross-training when responsibilities change
• Advanced training: Power user development, admin skills
• Release training: New features with NetSuite updates

Continuous Improvement

• Quarterly reviews: Assess system usage, pain points
• Enhancement requests: Track and prioritize improvements
• User feedback: Regular surveys, suggestion box
• Metrics tracking: Adoption rates, error rates, support tickets

NetSuite Support Resources