At inMotionNow, we like to eat what we cook. Our marketing department has been using Project Organizer since its release, but when our team expanded it was more important than ever to manage our projects and track statuses so we were all in synch. We naturally turned to Project Organizer for help.
Here is how we are using Project Organizer:
Redefining Projects
Previously, we were using Project Organizer to group similar types of work into “buckets”. For instance, all blog posts were uploaded for review as part of a project titled (you guessed it) “Blog Posts”. When a blog post was completed, the reviewed proof would be archived but the project would always remain in an Open status – after all, we don’t plan on being done with blog posts anytime in the foreseeable future!
This worked fine when we were a smaller team but as we grew, we needed to be able to track the status of our work beyond just when content was reviewed. After all, a blog post isn’t complete when it’s approved, it’s complete when it’s published.
Now, we upload every blog post as its own project, with its own Project Dashboard. Because project statuses are set manually, this allows us to share more accurate information about the state of our blog post projects – plus our print collateral projects, website projects, video projects, or anything else we may be working on.
Now our marketing team members can share more accurate project information, and the team leader can get an overview in their Project Workspace of what’s completed and what’s in progress.
The best part? We can still keep all of our blog posts in the same “bucket” by using Project Filter Groups. Each blog post project is assigned to the project filter group of “Blog”. When we want to get a snapshot of all our pending blog posts, it’s easy to filter our Project Workspace view to see just the projects associated with the Blog group.
Check back next week for Part 2, when we talk about how we’re using the Project Dashboard for organizing our team members, tasks, and milestones.
Share this postdata-via=”" >
