lestones as success metrics — especially for long-term projects — to keep everyone motivated by measuring how much work they’ve accomplished versus what’s left.
5. Assign work
Create a RACI chart or leverage project management software to delegate roles and responsibilities and clarify assignment expectations. Use whichever method you choose as an assessment tool to monitor progress and performance.
Be sure to explain your assignment choices and use this decision-making process to profile the team’s strengths and abilities.
6. Allocate resources
Allocate and delegate resources, including:
Then, determine project resourcing based on:
- Task priority
- Staffing requirements
- Available funds and tools
- Additional resource requirements
7. Share broadly
Once fellow project leaders approve, save and share this document in a centrally-located workspace every teammate can access. Reflect on this plan often to better understand how reality differs from initial planning and make adjustments when necessary.
An implementation plan example
To further illustrate how to fill out this plan type, here’s an implementation example for a team that’s making website updates.
Project goal: Updating website.
Project objectives: Update website to incorporate responsive design, include the latest user experience best practices, and refresh the look.
Success criteria: New website delivered in 12 weeks. Increase average time spent on site by 20% and revenue by 30%. Decrease bounce rate by 10%.
Scope statement: The website update project will require wireframes to outline updated navigation architecture and layout. The graphic design team will generate new visual assets to reflect current branding. The team will reuse existing website copy and functionality in this project.
- An internal team of graphic designers, UX specialists, and web developers
- Space on the preview server for testing
- Stock imagery for updated graphics
- Volunteers to conduct end-user testing and generate feedback
Risk analysis: Graphic designers and website developers will be reassigned to higher-priority projects. Existing website functionality will break when integrated with the new, responsive framework. The production server will not be able to keep up with post-launch demand.
Day 1: Kick-off meeting.
Day 3: Website layout and wireframe development begins.
Day 14: First review of wireframes and feedback delivered to designers.
Day 18–20: Staff holidays.
Day 28: Final review and edit of website wireframes.
Day 30: (milestone) Wireframes delivered to developers. Visual asset creation begins.
Day 40: 50% of website pages created and populated.
Day 50: (milestone) Developers complete website population.
Day 51: Content review. First round of edits delivered.
Day 62: (milestone) Website uploaded to preview server. User testing phase begins.
Day 70: Edits based on user testing delivered to developers.
Day 85: Final user acceptance testing.
Day 88: (milestone) Final approval for launch.
Day 90: (milestone) Website goes live at noon; team party at 3 p.m.
Set your project up for success with Roadmunk by Tempo
Take your implementation plan to the next level with Roadmunk by Tempo, a road-mapping platform that creates stunning visuals you can easily customize to suit your project. Pair this tool with Timesheets by Tempo to track staffing and performance, and you have everything you need to efficiently and effectively complete project deliverables.