All too often our interactions with production (roll out a config change, turn down an old job, etc.), are met with unexpected, disastrous, reactions.

We revise our mental models of how the system works, repair the outage if one occurs, and pick up with our change where we left off.

One useful tool can be a dashboard that captures the scope of the whole system, with links to monitoring and other information about each component. This becomes the interactive blueprint model for the system, reducing confusion, cognitive load and improving the success rate of interactions with the system. The jumping-off point for all debugging and change planning.

This talk will look at some examples of these dashboards that represent scopes of the system. Highlight how navigating between related scopes, or components, can be more powerful than standard documentation. Finally, will end with some discussion on challenges particular to multi-tenant systems.