Project Process Plan

The Purpose
This Project Process Plan is prepared during Phase 1: Design Risk Management for internal use only. The first stop after the project process plan is completed is to first receive the review and approval by Senior Management. Then it’s part of the initial stakeholder meeting agenda so all team members see how their content contributions and time commitments are integral parts and need to align into the process so the project stays on-track.  The plan is process oriented, defining how the project will move from content discovery through design, development, review, revision tweaks, and final approval.

What This Plan Is For

This document creates operational clarity for the project team, stakeholders, management, and SMEs.  It establishes:

• The project workflow.

• Roles and responsibilities.

• SME involvement.

• Review and approval checkpoints.

• The handoff path from one phase to the next.

Who Has Access & Why Do They Need It

Project Manager / Instructional Lead

Uses the plan to manage the workflow, hold the timeline, and oversee handoffs across the project lifecycle.

Stakeholders / Management

Uses the plan to understand how decisions will be made, where approvals are needed, and who owns final signoff.

SMEs

Uses the plan to see when they are needed and what kind of input is expected from them.

Design / Development Team

Uses the plan to work from an agreed process instead of reacting to shifting expectations.

Process Plan Structure

Phase 01: Internal Planning Before Stakeholder Kickoff

Draft the project process, define roles, identify SME touchpoints, map review gates, and establish the approval chain before the first formal stakeholder session.

Phase 02: Initial Stakeholder Meeting

Present the internal process plan, confirm expectations, validate roles and responsibilities, and gain agreement on how the project will run.

Phase 03: SME Content Research and Discovery

Gather source content, clarify business context, confirm accuracy needs, identify gaps, and capture the decisions required for learning design.

Phase 04: Design and Blueprint Development

Translate confirmed content into a structured design approach, learning flow, assessment logic, media direction, and storyboard or prototype path.

Phase 05: Development and Build Execution

Create the approved deliverables according to the design blueprint while managing version control, technical standards, and production checkpoints.

Phase 06: Review, Revision, and Final Approval

Move deliverables through agreed review rounds, collect consolidated feedback, complete revisions, conduct QA, and secure final stakeholder approval for release.

Core Message

The process needs to be visible before production starts.

If the team sees the process upfront, the meeting becomes about alignment. If they do not, the meeting becomes about assumptions.

Simple Positioning Statement

This is an internal process plan for the eLearning project, prepared before the initial stakeholder meeting so the team can align on roles, workflow, review cycles, and approvals.