Value driver trees, or VDTs, are a useful way to show the relationship between controllable business inputs
(e.g. for a factory, downtime between production runs) and desired business outcomes (e.g. profit).
I often use them to communicate the business value of an improvement idea. Showing the logic behind an estimate
of business value in a graphical format is transparent, trusted, and executive-friendly in a way that a
hand-written calculation or Excel spreadsheet is not.
However it is painfully repetitive to produce these diagrams in a workplace where Excel and Powerpoint are only
tools available for content creation.
Drawing rectangles, adding text, formatting connectors,
aligning shapes... then doing it all over again to incorporate last minute changes.
This tool shortcuts this tedium by quickly generating polished, editable VDT diagrams in Excel or Powerpoint,
based on the user's spreadsheet data and a handful of configuration settings.
There are only three inputs required to get started - the name of the worksheet containing the input data, the row in
which the data starts, and the scenarios to display on the VDT diagram.
The tool requires the input data to conform to a particular structure, described within the tool itself. The easiest way
to get started is to click the 'Generate new input' button and replace the dummy data with your own.
One thing to watch out for is the Scope column on the input data sheet. Use this to describe what portion of the tree
to include in the generated diagram, as shown below.
Note that the nodes in the generated Excel VDT diagrams can be double-clicked to toggle the display of further detail. This works by adding and removing 'Trim' entries in the input data sheet's 'Scope' column, and redrawing the tree.
There are additional configuration options to change the appearance of the generated VDTs. They should be self-explanatory,
so have a play around with them to see how they work.
Two of these configuration options are particularly useful:
This tool has served me well over the past couple of years.
If you find yourself feverishly producing similar VDT diagrams, perhaps thanklessly and under tight deadlines, please give it a go.
P.S. The VBA under the hood is not attractive. It has been cludged together by a hobbyist with scraps of VBA knowledge
retained from years ago.
Let me know if you have any improvement suggestions.