ItTakesTooLong

From CAM-I Wiki
Jump to: navigation, search

It takes too @*!%?# long!** 01TooLong.jpg

Each pain expressed in the survey implies different situations and concerns to different people. These implications, in turn, imply yet more situations and concerns. These implications have been organized and grouped into issues now showing as headings below. What additional implications do these call to your mind? Please feel free to add your implications to this page.

Then, follow the heading link to a page that discusses each issue. The page includes viewpoints and recommendations pertinant to the issue. You can also add your input to the issue page.


Analysis

  • Has too much detail
  • Too much analysis
  • Too little analysis

Assumptions

  • Assumptions not documented

Budget Bashing

  • Too many levels of development and review
  • Viewed as low priority
  • Too much rework

Data Management and Relevance

  • Too much effort
  • Too little value
  • Forward pricing rates/frequent updates
  • The appearance of value being added
  • Lack of consumption rates
  • Lack of demand data / customer forecast
  • Too little data
  • Too little relevant detail
  • Access to data is difficult
  • Multiple versions of the truth
  • Lack of translation from high level driver to low level driver

Decisions

  • Too long to formal decision
  • No clear stopping rule

Disconnect Operations and Financials

  • Creates feelings of self importance
  • Creates shadow staffs outside the P&B organization
  • Detracts from daily operational business
  • Deals with issues/baggage that are not budget issues
  • May not change annual budget for performance measurement
  • Redefinition of products and services

Events

  • Winds of change blow
  • Implies accuracy in far future periods

Framework

  • Too many annual accounting structure changes
  • Too many drivers and / or activities

Noise

  • Creates noise in the organization
  • Noise creates insentivity in organization
  • Too much customer affordability variance

Organization Component

  • Too many organization changes

People

  • Too many people in the process

Process

  • It is continuous and does not stop
  • The process is dynamic
  • The process is important
  • There is no process
  • Requires more coordination across stakeholders
  • Individuals experience downtime

Relevance

  • Perceived lack of relevance

Roles

  • Requires more dedicated & specialized staff
  • Lack of clear roles and Responsibilities
  • Overly rigid roles & responsibilities
  • Unclear rules

Time Concern

  • Implies accuracy

Tools

  • Poor/inappropriate modeling tools

Back to 10 Pains