Hours Optimized


Hi All -

Anyone have experience, anecdotes, examples of way to quantify 'hours optimized' across the user community within Anaplan? The organization quantifies hours optimized to quantify the value of a project, initiative, change, etc.

This more relates to additional enhancements, add-on projects within Anaplan and the processes it supports. Not so much going from Excel (or another tool) to Anaplan from a wholesale initial implementation perspective.

thank you!


  • @adpinto,

    Quantifying "hours optimized" within Anaplan, especially in the context of enhancements and add-on projects, can be a valuable way to measure the impact and efficiency gains. Here are some approaches and examples to help you quantify hours optimized:

    1. Example: Before Anaplan, the monthly reconciliation process took an average of 20 hours. With the new enhancements, it now takes 10 hours. The optimization is 10 hours per month.
      1. Identify specific processes within Anaplan that were enhanced or added.
      2. Measure the time users spent on these processes before and after the implementation of Anaplan enhancements.
      3. Calculate the reduction in processing time and translate it into hours saved.
    2. Example: Users report that the new forecasting module in Anaplan saves them approximately 5 hours per week in data entry and validation.
      1. Collect feedback from users regarding the efficiency gains they've experienced with Anaplan enhancements.
      2. Use surveys or interviews to capture qualitative data on time saved and improved workflows.
      3. Convert qualitative feedback into quantitative metrics based on user estimates.
    3. Example: Anaplan automation reduced the time required for data entry by 2 minutes per transaction. With 1,000 transactions per month, this results in 33 hours saved.
      1. Analyze the volume of transactions or data entries before and after the Anaplan enhancements.
      2. Calculate the time saved per transaction or data entry and aggregate across the user community.
    4. Example: Before Anaplan, 5% of the budget entries had errors requiring correction. With improved data validation, error rates dropped to 1%, saving users 15 hours per month in error resolution.
      1. Measure the reduction in errors or discrepancies due to Anaplan enhancements.
      2. Quantify the time saved by users who would have otherwise spent correcting errors.
    5. Example: The new reporting dashboard in Anaplan is accessed by 20 users daily. Each user spends 30 minutes less on reporting tasks, resulting in 10 hours saved daily.
      1. Track the frequency of use of Anaplan features or modules.
      2. Calculate the time saved by users who utilize these features regularly.
    6. Example: Transitioning from a legacy financial system to Anaplan reduced the time spent on budget consolidation by 25%, resulting in 40 hours saved per month.
      1. If applicable, compare the time spent on tasks in Anaplan to the time spent on similar tasks in legacy systems.
      2. Quantify the efficiency gains by highlighting the differences.

    These examples provide a starting point for quantifying "hours optimized" in Anaplan. Customize these approaches based on your specific use cases and metrics that align with your organization's goals and objectives.