Skip to content
English
  • There are no suggestions because the search field is empty.

Impact Reasons

  1. Whenever a team member makes a change to a task in Playbook that impacts the milestone date, they are prompted to capture the reason for the change. Since the buffer chart displays every shift to the milestone, you can see what caused the change when you hover over each data point.

  2. Impact reasons can be used to explain milestone slips...
    Impact Reason - 39 Day Slip

  3. As well as milestone gains...Impact Reason - 27 Day Gain
  4. You can also categorize reasons and show a summary of their impacts/gains.Summarized Delay Categories

  5. You can also export a report of every Impact Reason along with the amount of delay/gain they caused so you can plan future kaizen events based on actual level of importance.

  6. After all, how can you solve future problems if you can’t quantify what is causing them?

  7. Impact Reasons are defined in the Tracking Milestone's description using the format...

    date1 <space> reason1
    date2 <space> reason2

    For example...
    • 5/30/22 Supplier delivery later than expected
    • 6/8/22 Joe J. unavailable for one week due to production issues
  8. To define categories in your Impact Reasons... add ##Category

    For example...
    • 5/30/22 Supplier delivery later than expected ##Supplier
    • 6/8/22 Joe J. unavailable for one week due to production issues ##Resource Availability
  9. Need a hand? Contact a Customer Success Engineer today!