Get Certified for Operational Excellence’s Post

The value of your waterfall chart can slow to a trickle if your organization lacks the time and energy required to keep it updated. Keep business flowing with our contract waterfall guide. https://bit.ly/3TZIlL0

Why should I care about Effort vs Impact? So, my last post was about business improvement registers and in it I mentioned the MoSCoW methodology for prioritising tasks in a project. This is particularly suited if you have a long list and not necessarily workshopping it. Another way to prioritise tasks is the Effort vs Impact Matrix. This is particularly useful if you’re workshopping a problem and a number of solutions have emerged. Essentially you have a 2x2 grid with Impact on the y-axis and Effort on the x-axis. Everyone’s sticky notes with suggestions have already been presented and the group now decides the amount of effort and impact to assign to each. They are then placed accordingly on the grid. Immediately, you have the scale of the solutions determined: Low effort, high impact = do now Low effort, low impact = task for later High effort, high impact = project High effort, low impact = forget for now From here, if there are several solutions to be selected, they can be voted on to prioritise.

Hi folks! I am glad to share with you my achievements during bench time. Just finished the course “Business Process Improvement” by Eddie Davila and even took an exam for it!  #businessprocessimprovement #AdvancedBusinessAnalysis #continuousStudy #continuousSelfDevelopment

If the work comes into your workflow faster than it leaves it, this is a clear indication that your system is unstable. From a predictability perspective, this is disruptive, because a constant increase in your work in progress inevitably leads to a constant increase in your delivery times. How could you be predictable in a world when your delivery times are constantly increasing? You can’t. When evaluating the arrival and departure rates of your workflow, the Cumulative Flow Diagram comes into play. The top line of the graph represents the arrival rate of tasks while the bottom line shows their departures. In order to maintain a stable delivery system, we need to monitor how these lines move over time. To maintain a stable process strive to keep your WIP as consistent as possible. If the WIP is consistent, arrival rate and departure rate lines will grow in sync and the distance between them will stay equal. To learn more about how to read the Cumulative Flow Diagram, how to recognize the most common CFD patterns and what they mean for your workflow, download our ultimate guide to reading the Cumulative Flow Diagram → https://bit.ly/3rMNEMN #NavigateYourFlow #Kanban #Flow #PerformanceImprovement #AgileManagement

I just finished the course “Business Process Improvement” by Eddie Davila! #businessprocessimprovement.

If the work comes into your workflow faster than it leaves it, this is a clear indication that your system is unstable. From a predictability perspective, this is disruptive, because a constant increase in your work in progress inevitably leads to a constant increase in your delivery times. How could you be predictable in a world when your delivery times are constantly increasing? You can’t. When evaluating the arrival and departure rates of your workflow, the Cumulative Flow Diagram comes into play. The top line of the graph represents the arrival rate of tasks while the bottom line shows their departures. In order to maintain a stable delivery system, we need to monitor how these lines move over time. To maintain a stable process strive to keep your WIP as consistent as possible. If the WIP is consistent, arrival rate and departure rate lines will grow in sync and the distance between them will stay equal. To learn more about how to read the Cumulative Flow Diagram, how to recognize the most common CFD patterns and what they mean for your workflow, download our ultimate guide to reading the Cumulative Flow Diagram → https://bit.ly/3rMNEMN #NavigateYourFlow #Kanban #Flow #PerformanceImprovement #AgileManagement

The Fine Art of Creating Winners, in a Business Process Improvement Effort. Are you a “glass half full” kind of person? There’s much to be said for seeing business process improvement (BPI) opportunities through optimistic eyes. https://ow.ly/WRa150RPUUg

Just wrapped up an insightful course “𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬 𝐅𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧𝐬: 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐌𝐨𝐝𝐞𝐥𝐢𝐧𝐠 ” by Haydn Thomas! 🔍 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐌𝐨𝐝𝐞𝐥𝐬: Process models help visualize the sequence of activities within an organization, whether it's mapping out current workflows (as-is models), envisioning future states (to-be models), capturing detailed interactions between departments (cross-functional flow diagrams), or documenting step-by-step processes at the lowest level (flowchart process maps). 📊 𝐓𝐲𝐩𝐞𝐬 𝐨𝐟 𝐃𝐢𝐚𝐠𝐫𝐚𝐦𝐬: 1. 𝐂𝐨𝐧𝐭𝐞𝐱𝐭 𝐃𝐢𝐚𝐠𝐫𝐚𝐦: Provides a high-level view of how our organization interacts with external entities, crucial for understanding project scope and impacts. 2. 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐅𝐥𝐨𝐰 𝐃𝐢𝐚𝐠𝐫𝐚𝐦: Illustrates how different internal stakeholders interact to achieve specific outcomes, ideal for conceptualizing workflows without diving into detailed steps. 3. 𝐂𝐫𝐨𝐬𝐬-𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐅𝐥𝐨𝐰 𝐃𝐢𝐚𝐠𝐫𝐚𝐦: Maps out end-to-end processes across various departments or stakeholders, identifying inefficiencies and opportunities for improvement. 4. 𝐅𝐥𝐨𝐰𝐜𝐡𝐚𝐫𝐭 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐌𝐚𝐩: Documents detailed step-by-step processes performed by a single actor, helpful for identifying inefficiencies and supporting continuous improvement efforts. 🔄 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐈𝐦𝐩𝐫𝐨𝐯𝐞𝐦𝐞𝐧𝐭: By analyzing these diagrams, BA can identify inefficiencies, streamline workflows, and ultimately enhance our operations for better outcomes. 📈 𝐈𝐦𝐩𝐚𝐜𝐭 𝐨𝐧 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬: These models serve as foundational tools for project planning, stakeholder communication, and ensuring alignment with strategic objectives. #businessprocessmanagement #businessanalysis #BABOK #Chapter10.35

Deep business understanding is pivotal. We dive into client operations to grasp not just the technical requirements but also the business context. This thorough understanding enables us to tailor solutions that are technically sound and strategically aligned with your goals. #BusinessUnderstanding #ClientFocused #ProjectManagement

If the work comes into your workflow faster than it leaves it, this is a clear indication that your system is unstable. From a predictability perspective, this is disruptive, because a constant increase in your work in progress inevitably leads to a constant increase in your delivery times. How could you be predictable in a world when your delivery times are constantly increasing? You can’t. When evaluating the arrival and departure rates of your workflow, the Cumulative Flow Diagram comes into play. If WIP is increasing then the distance between the lines will expand. This means that the arrival rate is higher than the departure rate, and it denotes that there is a bottleneck in the system, which means your team is struggling to deliver results. As WIP increases over time, our delivery times increase as well. To maintain a stable process strive to keep your WIP as consistent as possible. If the WIP is consistent, arrival rate and departure rate lines will grow in sync and the distance between them will stay equal. To learn more about how to read the CFD and how to recognize the most common CFD patterns, download the ultimate guide to reading the Cumulative Flow Diagram → https://bit.ly/3rMNEMN #NavigateYourFlow #Kanban #Flow #AgileManagement #ContinuousImprovement