A well-structured project roadmap is essential for successfully implementing Q.wiki. It helps you steer your team and organization throughout the entire implementation period.
Overview
Many implementation projects follow a proven phase model. The following roadmap shows a typical 6-month rollout in a mid-sized organization – use it as a reference, but customize it for your specific situation.
You'll find the template (PowerPoint) at the end of this article. You can freely edit and adapt all shapes and text to fit your needs.
How to create your roadmap
Follow these steps:
- Start with your project end date (e.g., audit date).
- Set your final milestone to that date.
- Plan the roadmap backwards from there to your start date.
- Distinguish between phases for the project team and phases that involve all employees.
The four phases of Q.wiki implementation
Phase 1: Build the foundation
Your project team takes the lead:
- Define project structure, project team, and goals
- Develop project marketing: When and how will you communicate the launch? Which channels will you use?
- Set up process structure
Phase 2: Set the impulse
The kickoff for your entire organization:
- Conduct kick-off
- Launch internal Q.wiki marketing
Phase 3: Engage employees
Now the whole organization works with you:
- Conduct process workshops with project team members
- Train users with Q.wikinger
- Employees begin capturing content independently (you provide support but are no longer directly involved in content creation)
Phase 4: Consolidate success
Implementation concludes and Q.wiki enters continuous operations:
- Release content – until this point, all work has been on drafts. With this step, pages go through the approval workflow for the first time and receive version 1.
- Evolve Q.wiki continuously: From now on, steadily work on new content and improve existing content.
Template
Use this PowerPoint as a template for your own roadmap:
[Insert template download here]
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article