How to Write an Implementation Plan
The steps involved in writing an implementation plan are straightforward, but the
process is not quick or easy. Each section should be detailed, combining the information
from your strategic plan and incorporating the necessary research and data that makes
your objectives actionable. In this section, we’ll provide an ordered tutorial for writing
each component in an implementation plan.
Introduction: The introduction of your implementation plan explains the purpose,
vision, and mission statement of your project or initiative. You should identify the high-
level risk areas, include any assumptions, and describe how you will identify the value
stream in your proposed work.
Management Overview: In this section, you describe how implementation will be
managed. This includes who is managing it, the underlying roles and responsibilities,
and key points of contact. You should identify the strategy director, who is the person
that develops and steers the strategy (this may or not be the same person who is leading
implementation).
Major Tasks: This is where you list and describe the specific tasks, actions, and targets
in implementation. You should also note the status of any tasks that are already in
progress.
Implementation Schedule: You do not need to create a detailed, inflexible task
schedule in your implementation plan — we’ll talk later on about how to create a
schedule in the execution plan. At this stage, it’s appropriate to simply list the task order
and predicted phase durations to roughly outline and allot for all the many moving
pieces.
Security and Privacy: Discuss the privacy features and considerations of the software
tools, processes, or information that you may use in implementation. Address security
issues and how to handle sensitive information (personal data, medical history,
financials, etc.).
Implementation Support/Resources List: Describe the various tools, activities, and
departments that you require to support successful implementation. These might
include hardware or software tools, facilities, and additional external human resources
or services.
Documentation: In this section, you must attach any other documentation that supports
your implementation plan. This could include your strategic plan, confirmation of
adequate materials and resources, and a history of past successful projects.
Monitoring Performance: Define the metrics by which you will measure success.
How and when will you review your progress?
Acceptance Criteria: How will you define implementation “completion?” This differs
from performance monitoring because rather than defining metrics for milestones and
appropriate implementation, here, you describe how you will know when you have buy-
in from management on your implementation plan.
Glossary: Define any key terms used in your implementation plan.
References: Indicate where you received your information, or list people who support
your plan.
Project Approval: If you need management’s approval before moving into execution,
this section provides space for official signoff.
To make it easy, you can also use a template to write your implementation plan. This
will ensure that you don’t overlook any steps or sections and also provide a professional
layout that you can use to deliver to management, clients, or other stakeholders.
