Skip to main content
A strong view makes the audience’s job easier, not more complicated.
  • Build one view for one decision, workflow, or audience.
  • Name shared views after the process or question they support.
  • Keep filters and grouping readable.
  • Review views after model structure or database schema changes.
  • Retire views that are no longer used.

​
Design for repeat use

The best shared views are the ones people trust enough to reuse every cycle without asking how they were built.

​
Keep the source and the view aligned

If the source keeps changing to support one fragile view, fix the model or database design instead of hiding the problem inside more saved rules.