In the Proggio solution, we use an innovative project chart called the “Projectmap”. At first glance the projectmap may appear as just another block diagram. However, it is far, far more than that.
Projectmap is a revolutionary approach to project management, starting from a clear project presentation through critical project operations and into project analytics.
Here is an insight into the magic of projectmap and the patent behind it.
Your project like never before – Projectmap layers
Following the concepts contained in street maps, Google, and many others, Projectmap introduces several project information layers. The upper layer provides a high level view of all Team projects. Moving one level down, it takes you into a high-level view of a single project, then a planning layer, and finally individual tasks.
Drilling down reveals more and more detail, while moving upstream enables a wider view. A concept of top-down planning is maintained throughout the use of the solution, making sure that details are presented in context and in line with a higher level timeline.
Project team assimilation – the Projectmap workstreams
Project management tools evolved for years through tasks and task management tools. In retrospect, diving further into the detail didn’t yield any operational advantages. In fact, it had the opposite effect. The more task details were added, the more complicated and unusable the chart became.
Projectmap is breaking out of task structure, presenting Workstreams for the first time – and introducing project charts that are headed by teams and functional areas. This change is not a nuance, it is a revolution! Real projects are managed through people that operate workstreams – whether the team leader, the individual contributor, or managers of functional areas. By placing these workstreams at the head of the Projectmap chart, we easily integrate the operational function of the project, and enable project operation based on the real life accountability matrix.
Step out of the dependencies noise – the Links podium
Existing project management tools keep all dependencies at the same level. A minor dependency between 2 sequential activities and a monster dependency holding the riskiest coordination of the project appear exactly the same. A project with 300 tasks is likely to have at least double the number of dependencies than a smaller one. How can we step out of this noise? Which dependencies are important for the Project’s coordination plan?
Projectmap’s Workstreams are designed to resolve this issue. It’s a known fact that a project’s weakest point is the handshake between teams. Along the same lines, links are more critical if they represent a connection between activities on different workstreams. Links between activities of the same workstream are important to project structure, but less important to project operation, since people among the same team are likely to manage these links internally.
Highlighting that link across multiple teams, opens a world of operation opportunities and project analytics – expect more in this area from Proggio in the near future!
Work less, get more – with Projectmap automation
Tired of maintaining Excel files, Powerpoint diagrams and task reporting tools? That hassle comes from working with different data sources and lack of cross-view automation.
Proggio automation is a byproduct of the Projectmap layered approach, all using the same data source – no extra effort, no data manipulation. Transparency and efficiency at its best.
While you’re planning using the Projectmap Planning layer, Proggio calculates and creates the higher layers and the Project Portfolio for you. In a similar way, reporting progress on tasks is represented all the way up to Project Portfolio view. Adjusting activities on the Planning layer will also adjust all related tasks that are sitting in the activity container.
Less is more – thoughtful project planning
Last, but by no means least – as sophisticated as the project management solution can be, if garbage is going in, garbage is very likely to come out. Preventing garbage requires the project team to think with a thought process unlikely to produce garbage.
Planning with Projectmaps requires you to think deeply about the project structure: what goes into my workstreams? What goes into my planning layer?
The answer to the first question reveals the project’s main stakeholders and teams involved. The answer to the second question reveals the activities that are more critical to project structure, and leaves tasks to a more detailed layer underneath.
With these two critical questions answered and presented in the Projectmap chart, the project’s challenges are now transparent to the entire team. When team members understand, they engage. When they are engaged, you are already halfway to project success.
After reviewing the tremendous value of Projectmaps and its implementation in Proggio, you can now understand what makes it more than just another block diagram. Experience Projectmaps by signing into Proggio today! You will see the difference in just five minutes.