Issue tree

Hi there,

A driver tree is literally a different thing to buckets and a framework! 

A framework is 3 buckets which a bunch of things to look at. A driver tree is essentially all the pathways a case could take…

For example (this is overly generic/simplified, but the easiest way to explain this):

1. Are revenues down?
   1. If yes, are certain products down?
      1. If yes, investigate the largest down products
         1. Are volumes down?
            1. If yes, xxx
            2. If no, have we changed our prices?
      2. If no, assess the market overall (or other splits like geography, business units, etc.)
   2. If no, are certain geographies down?
      1. If yes, investigate the largest down products.
         1. xxx
      2. xxx

^Please don't interpret this as what you always have to do for profitability, but it's an example of a possible line of questioning (i.e. driver tree)

Honestly, the best strategy is to not have a single generic issue tree that you will stick in every case.

A good caser always creates a customized and relevant issue tree that is tailored to the specific case and specific client and specific industry.

Hi!

If you have a specific case in mind post it here with a tentative structure so that we could give you more accurate feedback.

Best,

Anto