ceos-dashboard

To create a read-only dashboard for EOS health, you need a tool that aggregates data from vision, rocks, scorecard, issues, people, and accountability sources. This dashboard surfaces the current organizational status to guide leadership decisions without allowing direct modifications.

Preparing for an L10 meeting using EOS data involves generating a current-state snapshot across all organizational data sources. A read-only dashboard provides a quick pulse check on scorecard metrics and open issues to ensure leadership reviews focus on accurate, aggregated data.

Yes, a leadership scorecard can aggregate rocks and issues data by pulling from their respective data directories. The dashboard enforces a read-only workflow, gracefully degrading for any missing data to present a concise status without altering the underlying files.

An EOS dashboard supports cross-skill coordination by surfacing exactly when to run targeted skills like ceos-rocks, ceos-scorecard, or ceos-ids. It identifies the area needing attention and guides users to the appropriate action-oriented skill to affect change.

When dashboard data aggregation encounters missing accountability files, the system gracefully degrades. It continues to surface the available organizational health data from other sources like vision and rocks, ensuring the read-only snapshot remains functional for leadership review.

You should not use a read-only dashboard when you need to modify, update, or resolve open EOS data. It is designed strictly for viewing organizational health; you must transition to specific action skills like ceos-ids or ceos-rocks to execute any operational changes.