Skip to main content
Projects are the foundation of change management in Leap Change. Each project represents a distinct change initiative and contains all related stakeholders, impacts, surveys, and communications.

​
Project creation wizard

Leap Change guides you through project creation with a step-by-step wizard.

​
Step 1: Welcome

The wizard begins with an overview of what you’ll configure. Click Get Started to proceed.

​
Step 2: Describe the change

Provide essential information about your change initiative:
  • Project name - A clear, descriptive title
  • Description - Detailed explanation of what’s changing and why
  • Change owner - Person responsible for the change
  • Sponsor - Executive sponsor supporting the initiative

​
Step 3: Classify

Categorize your project:
FieldDescription
Change typeTechnology, Process, Organizational, Policy, etc.
PriorityCritical, High, Medium, Low
DepartmentsWhich business areas are affected
Geographic scopeLocal, Regional, Global

​
Step 4: Set timeline

Define key dates:
  • Start date - When change activities begin
  • Target go-live - Expected implementation date
  • Milestones - Key checkpoints along the way

​
Step 5: Transition planning

Outline your change approach:
  • Communication strategy - How you’ll keep stakeholders informed
  • Training approach - How you’ll prepare people for the change
  • Support plan - How you’ll help during transition

​
Step 6: Launch

Review your project setup and click Create Project to launch.

​
Organizing projects with programs

For large-scale transformations with multiple related projects, use Programs to group them together.
  1. Go to Programs in the sidebar
  2. Click New Program
  3. Name and describe the program
  4. Add existing projects to the program
Programs provide portfolio-level visibility across related change initiatives.

​
Project settings

After creation, you can adjust project settings:
  • Edit details - Update name, description, timeline
  • Manage members - Add team members with specific roles
  • Archive - Archive completed projects (data is preserved)

​
Best practices

Include the year and change type in project names (e.g., “2026 ERP Migration - Finance Module”) for easy identification.
Factor in assessment, planning, and sustainment phases—not just implementation.
Define the change owner and sponsor before starting stakeholder engagement.