VCDX – Enhanced Design Decisions

As a VCDX Mentor and NPX Panelist, I review many designs. During a recent review I saw an interesting twist to the design documentation that could be of benefit to all VCDX and NPX candidates.

List of articles in my VCDX Deep-Dive series (more than 80 posts)

For each design decision made, the candidate had a “note” at the end of the justification that provided an “alternative” or “Plan B” design decision (including the justification) if the driving requirement or constraint was removed. To those of you that have read my previous VCDX Deep-Dive blog posts, this could sound like the “Requirements Conflict” field in a design decision, which is only used when a conflict exists. The “alternative” design decision field would be completed for each and every design decision.

Why was this helpful to me as a reviewer? It meant that the candidate was able to demonstrate additional expertise and depth of knowledge through the submission documentation. Which means that the candidate would have additional time during the defence to spend time scoring in other areas of the blueprint.

If you want to demonstrate your expertise to maximum effect through your submission documentation and have the highest possible pre-score walking into the defence, consider using “Enhanced Design Decisions” throughout your Architecture Design documentation.

Here is an example for VCDX-NV (Enhanced Design Decision highlighted in green):

Thanks to Anthony Burke and Tim Davis for providing feedback on NSX Controller design.