You may be familiar with Wrike Discover - Wrike’s award-winning e-learning platform that provides interactive training for Wrike’s clients. We develop learning plans, courses, certification programs, and much more. In this post, I wanted to share insights into how our team uses Wrike to deliver great learning content. More specifically, I will talk about how we create courses and hopefully, you can grab some tips from here when working on your repeatable projects.
Currently, Wrike Discover has an extensive catalog of courses and our course development process is very streamlined. It was not always like this. When our team started working on creating courses, we very quickly realized that it is a repetitive process. Our courses go through the same phases and each phase requires specific steps to be completed so we can move on to the next one. So, creating a blueprint was only natural. For us, each course is a project that starts with activating a blueprint.
Here’s what we do:
Our courses go through several phases that we call Design, Develop and Implement. In our “Discover Course” blueprint, we created high-level tasks that represent each of those phases.
Each phase or parent task also contains subtasks that show exactly what needs to be done within that phase. This means the blueprint contains all the information we need to keep track of when developing a course.
For us it makes sense to keep certain tasks unassigned, however, you can assign team members to your blueprint tasks if you know that they will always be the ones working on those tasks.
A blueprint is also where you set task durations and dependencies when necessary so that you don’t have to do it over and over again for your repeatable projects. Once you schedule your project, all the durations and dependencies set in your blueprint will roll up to the new due date.
Once we launch a blueprint and start an actual project dedicated to course development, we can easily track all the work using different Wrike views depending on what we need at any given moment.
I open my new project from the “In Development” subfolder of our “Courses” folder.
From this point on, I prefer to work from the Gantt Chart. I put my project manager hat on, and assign all the necessary tasks to our multimedia designers from the Table portion of the chart, and edit durations and dependencies using the Gantt chart’s timeline.
So the process has been started and the project is in progress.
Another feature that we rely on heavily is Approvals. For example, once the assigned multimedia designer finishes version 1 of the course, it is time for the managing stakeholders to review and approve the delivery. Here, it is time to use the Approval functionality in Wrike. The multimedia designer starts an approval process and assigns the task to the Instructional Designer (who is generally the project owner) for approval. I receive the notification in my Inbox and I review the course, provide feedback, and potential edit suggestions. Based on the task, additional approvals might be required before we go live with the course. In Wrike, you can add more than one approval to a task or phase.
This is obviously a very quick overview of the process and it does have more complexity and detail to it. I would be happy for us to continue the conversation so feel free to comment with either your questions to me or by showing how you deal with repeatable projects in your work.
Want to try out these functionalities? Check out these Discover courses:
- Blueprints (Templates) in Wrike
- Project Management: Scheduling and Data
- Marketing: Research and Writing
Vlad G Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online