Question
Why does workflow review process fail?
Quick Answer
Never reviewing at all, letting your workflow portfolio accumulate dead weight — workflows for projects that ended, tools you no longer use, processes that were patched so many times they no longer resemble their original design. Or reviewing too frequently at too granular a level, spending more.
The most common reason workflow review process fails: Never reviewing at all, letting your workflow portfolio accumulate dead weight — workflows for projects that ended, tools you no longer use, processes that were patched so many times they no longer resemble their original design. Or reviewing too frequently at too granular a level, spending more time maintaining your system than doing actual work. The review is periodic maintenance, not continuous monitoring. It operates at a different cadence and altitude than the per-execution iteration of L-0814.
The fix: Make a list of every workflow you currently run — formal or informal, work or personal, daily or quarterly. For each one, answer three questions: When did I last execute this? Is there a step that no longer makes sense? Is there a recurring task I do that has no workflow at all? Based on your answers, retire one workflow, update one workflow, and draft a skeleton for one missing workflow. This is your first workflow review. Schedule the next one for thirty days from now.
The underlying principle is straightforward: Periodically review all your workflows to retire outdated ones and improve active ones.
Learn more in these lessons