[From Wrike] Workflow Analysis Basics
- You would like to perform an analysis of how tasks and projects progress over time
- You would like to challenge yourself with a more complex BI concept
- Task Status Change History Change Date (the date when the user switched the task's status)
- Task Status Change History Old -> New Status (the precise status change -- FROM this status TO that status -- that was made on that day)
Note: "Old Status" and "New Status" are also available as separate dimensions and are very useful for slicing and dicing. Give them a try as well!
- My Runzoocane project has 6 tasks.
- Tasks 04 and 05 were completed on 1/26. They were completed very quickly and workflow steps were skipped (was work actually done? why weren't all steps followed?)
- Tasks 00 and 01 were never started (still in New status) even though they were both due in January.
Explanation: When the New Status (right side) is N/A that means this Old Status (left side) is the current status. Notice that in this situation, the change date will always be the current date. - Tasks 02 and 03 were started on 1/26 but have remained in the "In Progress" state ever since.
- There are relatively few statuses that are used for tasks. Are other workflows not being used?
- Those status changes with many IDs mean this status change happens more frequently; relatively few IDs mean that this change happens less frequently.
- There are 10 cases where a task was completed and then afterward uncompleted. What happened there?
Hint: Add task name and task link dimensions to see the actual tasks involved. - It appears that Wrike has not been used in a while. Those tasks that are still waiting for action (New Status is N/A) have been waiting for a very long time.
(This is a demo database that was created several months ago) - When tasks do get action using the standard operating procedure (eg. New -> In Progress, In Progress -> Completed), these steps happen within an average of 6 hours (.25 days)
- Many tasks are going straight from New to Completed which may imply skipped or unreported steps.
- Add another dimension, such as project type field, to add further depth and insight to status changes. Does a certain project type take longer to progress than others?
- Identify which projects ever go backward in the workflow. Why do these projects suffer from backtrack/rework?
- Of those projects that reach an On Hold status, what % of them are completed vs abandoned?
Sam Alter Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices
Sam Alter Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices
I am not currently tracking my progress in Wrike, but I'll consider it for the future!
We utilized very specific workflows and custom reports to track our progress. The report is distributed on a weekly basis to internal and external users.
Great examples Sam!! I often pull workflow reports - but this is excellent that this is part of Wrike Analyze, too! I think this is very effective and showcases examples of good adoption, as well as teams that may need refreshers in process, too
Thanks for the example Sam! I have looked at a few reports in this manner and this is an area that may help us determine amount of time and effort was we refine our project plan blueprints.