Organizing Observatory Panels

1 min read

Well-organized panels make analytics easier to scan, discuss, and act on. A good panel answers a clear question instead of collecting every available chart in one place.

Organize By Purpose

Create panels around the reason people will open them.

Useful examples:

Release Readiness: execution progress, failures, blockers, and defect pressure
Execution Quality: pass/fail trends, skipped work, and blocked test cases
Repository Health: test case priority, severity, test type, and automation status
Requirements Coverage: linked test cases, coverage gaps, and defect pressure

Organize By Audience

Different teams need different views.

QA teams may need detailed execution and failure charts.
Engineering teams may need defect severity, priority, and affected-area signals.
Project leaders may need release readiness, completion progress, and quality risk.
Product teams may need requirement coverage and validation signals.

Audience-focused panels reduce noise and make reviews faster.

Organize By Time Period

Time-based panels work well for recurring reviews.

Weekly execution health
Sprint validation progress
Monthly quality trend review
Release sign-off dashboard

Use clear names so older panels remain easy to understand later.

Organize By Project Area

Large projects often benefit from area-based panels.

Examples:

Login and access
Payments
User management
Integrations
Mobile validation

This works especially well when ownership is split across teams.

Keep Panels Focused

Strong panels usually have:

A clear title
A short description
A small set of related charts
A mix of progress, quality, and risk signals
Charts ordered from summary to detail

If a panel becomes hard to scan, split it into smaller panels.

Next Steps

Build a dashboard with Create Panels
Add charts with Create Charts
Review chart behavior in Charts Overview
Use execution analysis with Execution Analysis