[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7E39ZK3YAVGXJFSGVCXSN":3,"skill-same:01M7F7E39ZK3YAVGXJFSGVCXSN":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F7E39ZK3YAVGXJFSGVCXSN","creating-management-dashboards",null,"Designs management reporting dashboards with KPI selection, visualization, and drill-down structure. Use when building financial dashboards, selecting KPIs, or designing management reports.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fcreating-management-dashboards\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: creating-management-dashboards\nlanguage: en\ndescription: Designs management reporting dashboards with KPI selection, visualization, and drill-down structure. Use when building financial dashboards, selecting KPIs, or designing management reports.\ntags:\n  - drafting\n  - financial-planning-and-analysis\nmetadata:\n  author: casemark\n  practice_areas:\n    - FP&A\n    - Management Accounting\n    - Business Intelligence\n  document_types:\n    - New Document\n  skill_modes:\n    - Drafting\n    - Planning\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fcreating-management-dashboards\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Creating Management Dashboards\n\n## When To Use\n\n- Designing a new executive or departmental dashboard from scratch\n- Selecting and structuring KPIs for a specific business unit, function, or management audience\n- Rebuilding or rationalizing an existing reporting pack that has grown unwieldy\n- Translating a CFO or controller's reporting wish-list into a concrete dashboard specification\n- Creating drill-down hierarchies so users can move from summary to root-cause detail\n\n## Inputs To Gather\n\n- **Audience & decision context**: Who will use the dashboard (C-suite, department heads, board)? What decisions does it support (resource allocation, performance reviews, forecasting)?\n- **KPI candidates**: Existing metrics already tracked, plus any new metrics requested. For each, confirm definition, data source, refresh frequency, and owner.\n- **Data sources & availability**: ERP\u002FGL system, CRM, HRIS, budgeting tool, or data warehouse. Note any gaps or manual feeds.\n- **Reporting cadence**: Real-time, daily, weekly, monthly, quarterly. Determine whether the dashboard replaces or supplements existing reports.\n- **Benchmark & target context**: Internal targets (budget, prior year, rolling forecast) and external benchmarks (industry peers, analyst consensus) to display alongside actuals.\n- **Constraints**: BI platform in use (Power BI, Tableau, Looker, Excel), data-access permissions, branding\u002Fstyle-guide requirements.\n\n## Workflow\n\n1. **Define the dashboard purpose statement** — Write a one-sentence scope: audience + decision supported + cadence. Example: \"Monthly P&L dashboard for the CFO to monitor margin performance against forecast and flag variances > 5%.\"\n\n2. **Select and tier KPIs**\n   - **Tier 1 (headline)**: 4–6 KPIs visible at a glance (e.g., Revenue, Gross Margin %, EBITDA, Cash Conversion Cycle, Headcount, NRR).\n   - **Tier 2 (supporting)**: Metrics that explain Tier 1 movement, accessible via drill-down (e.g., revenue by segment, COGS breakdown, DSO vs. DPO).\n   - **Tier 3 (diagnostic)**: Granular data reached through a second drill-down (e.g., invoice-level detail, SKU-level margin).\n   - For each KPI, document: name, formula\u002Fcalculation, data source, refresh lag, owner, and RAG threshold definitions (green\u002Famber\u002Fred). [VERIFY] that formulas match the organization's accounting policies (e.g., adjusted vs. GAAP EBITDA).\n\n3. **Design the layout structure**\n   - **Summary page**: Tier 1 KPIs as scorecards or gauges with trend sparklines and variance callouts.\n   - **Detail pages**: One per functional area (Revenue, Cost, Working Capital, Workforce, etc.) showing Tier 2 metrics with comparison columns (actual vs. budget vs. prior year).\n   - **Drill-down paths**: Define click-through navigation from each Tier 1 card to its detail page, and from detail rows to Tier 3 data.\n   - **Filter bar**: Standard slicers for period, business unit, geography, and product line.\n\n4. **Specify visualization types**\n   - Use bar\u002Fcolumn charts for period-over-period comparisons.\n   - Use waterfall charts for variance bridges (budget → actual).\n   - Use line charts for trend and forecast overlays.\n   - Use tables with conditional formatting for dense data (e.g., GL-level detail).\n   - Avoid pie charts for more than 4 categories; use horizontal bar instead.\n   - Include a consistent color palette: one color for actuals, one for budget\u002Fforecast, red\u002Famber\u002Fgreen for RAG status.\n\n5. **Define interactivity and alerts**\n   - Specify cross-filtering behavior between visuals.\n   - Define exception-based alerts (e.g., email trigger when a KPI crosses its red threshold).\n   - Document tooltip content for each visual (metric definition, data-as-of date, source).\n\n6. **Map data pipeline requirements**\n   - List each source system, extraction method (API, ODBC, flat file), transformation logic, and load schedule.\n   - Identify any manual adjustments or journal entries that must be incorporated. [VERIFY] timing of month-end close vs. dashboard refresh to avoid stale data.\n\n7. **Draft the dashboard specification document**\n   - Compile the above into a spec: purpose statement, KPI dictionary, wireframe layouts, visual specs, data pipeline notes, and RAG threshold table.\n\n## Output\n\nDeliver a **Dashboard Specification Package** containing:\n\n- **Purpose & audience statement**\n- **KPI dictionary** — table with name, formula, source, owner, cadence, RAG thresholds\n- **Wireframe layouts** — page-by-page description of visual placement, chart types, filter bar, and drill-down paths\n- **Data pipeline map** — source → transform → load schedule per metric\n- **Interactivity spec** — cross-filters, alerts, tooltip definitions\n- **Implementation notes** — platform-specific considerations, access\u002Frole requirements, known data gaps marked [VERIFY]\n\n## Quality Checks\n\n- Every Tier 1 KPI has a defined drill-down path to at least Tier 2\n- KPI formulas are explicitly documented and reconcilable to source systems\n- RAG thresholds are defined with stakeholder sign-off, not arbitrary defaults\n- Visualization choices match the data type (categorical vs. time-series vs. part-to-whole)\n- Dashboard does not exceed 6–8 visuals per page to avoid cognitive overload\n- Refresh cadence aligns with the data pipeline schedule — no visual shows data newer than its source supports\n- [VERIFY] that metric definitions match the organization's chart of accounts and reporting standards (GAAP\u002FIFRS)\n- [VERIFY] data-access permissions ensure sensitive cost-center or compensation data is restricted by role\n","# Creating Management Dashboards\n\n## When To Use\n\n- Designing a new executive or departmental dashboard from scratch\n- Selecting and structuring KPIs for a specific business unit, function, or management audience\n- Rebuilding or rationalizing an existing reporting pack that has grown unwieldy\n- Translating a CFO or controller's reporting wish-list into a concrete dashboard specification\n- Creating drill-down hierarchies so users can move from summary to root-cause detail\n\n## Inputs To Gather\n\n- **Audience & decision context**: Who will use the dashboard (C-suite, department heads, board)? What decisions does it support (resource allocation, performance reviews, forecasting)?\n- **KPI candidates**: Existing metrics already tracked, plus any new metrics requested. For each, confirm definition, data source, refresh frequency, and owner.\n- **Data sources & availability**: ERP\u002FGL system, CRM, HRIS, budgeting tool, or data warehouse. Note any gaps or manual feeds.\n- **Reporting cadence**: Real-time, daily, weekly, monthly, quarterly. Determine whether the dashboard replaces or supplements existing reports.\n- **Benchmark & target context**: Internal targets (budget, prior year, rolling forecast) and external benchmarks (industry peers, analyst consensus) to display alongside actuals.\n- **Constraints**: BI platform in use (Power BI, Tableau, Looker, Excel), data-access permissions, branding\u002Fstyle-guide requirements.\n\n## Workflow\n\n1. **Define the dashboard purpose statement** — Write a one-sentence scope: audience + decision supported + cadence. Example: \"Monthly P&L dashboard for the CFO to monitor margin performance against forecast and flag variances > 5%.\"\n\n2. **Select and tier KPIs**\n   - **Tier 1 (headline)**: 4–6 KPIs visible at a glance (e.g., Revenue, Gross Margin %, EBITDA, Cash Conversion Cycle, Headcount, NRR).\n   - **Tier 2 (supporting)**: Metrics that explain Tier 1 movement, accessible via drill-down (e.g., revenue by segment, COGS breakdown, DSO vs. DPO).\n   - **Tier 3 (diagnostic)**: Granular data reached through a second drill-down (e.g., invoice-level detail, SKU-level margin).\n   - For each KPI, document: name, formula\u002Fcalculation, data source, refresh lag, owner, and RAG threshold definitions (green\u002Famber\u002Fred). [VERIFY] that formulas match the organization's accounting policies (e.g., adjusted vs. GAAP EBITDA).\n\n3. **Design the layout structure**\n   - **Summary page**: Tier 1 KPIs as scorecards or gauges with trend sparklines and variance callouts.\n   - **Detail pages**: One per functional area (Revenue, Cost, Working Capital, Workforce, etc.) showing Tier 2 metrics with comparison columns (actual vs. budget vs. prior year).\n   - **Drill-down paths**: Define click-through navigation from each Tier 1 card to its detail page, and from detail rows to Tier 3 data.\n   - **Filter bar**: Standard slicers for period, business unit, geography, and product line.\n\n4. **Specify visualization types**\n   - Use bar\u002Fcolumn charts for period-over-period comparisons.\n   - Use waterfall charts for variance bridges (budget → actual).\n   - Use line charts for trend and forecast overlays.\n   - Use tables with conditional formatting for dense data (e.g., GL-level detail).\n   - Avoid pie charts for more than 4 categories; use horizontal bar instead.\n   - Include a consistent color palette: one color for actuals, one for budget\u002Fforecast, red\u002Famber\u002Fgreen for RAG status.\n\n5. **Define interactivity and alerts**\n   - Specify cross-filtering behavior between visuals.\n   - Define exception-based alerts (e.g., email trigger when a KPI crosses its red threshold).\n   - Document tooltip content for each visual (metric definition, data-as-of date, source).\n\n6. **Map data pipeline requirements**\n   - List each source system, extraction method (API, ODBC, flat file), transformation logic, and load schedule.\n   - Identify any manual adjustments or journal entries that must be incorporated. [VERIFY] timing of month-end close vs. dashboard refresh to avoid stale data.\n\n7. **Draft the dashboard specification document**\n   - Compile the above into a spec: purpose statement, KPI dictionary, wireframe layouts, visual specs, data pipeline notes, and RAG threshold table.\n\n## Output\n\nDeliver a **Dashboard Specification Package** containing:\n\n- **Purpose & audience statement**\n- **KPI dictionary** — table with name, formula, source, owner, cadence, RAG thresholds\n- **Wireframe layouts** — page-by-page description of visual placement, chart types, filter bar, and drill-down paths\n- **Data pipeline map** — source → transform → load schedule per metric\n- **Interactivity spec** — cross-filters, alerts, tooltip definitions\n- **Implementation notes** — platform-specific considerations, access\u002Frole requirements, known data gaps marked [VERIFY]\n\n## Quality Checks\n\n- Every Tier 1 KPI has a defined drill-down path to at least Tier 2\n- KPI formulas are explicitly documented and reconcilable to source systems\n- RAG thresholds are defined with stakeholder sign-off, not arbitrary defaults\n- Visualization choices match the data type (categorical vs. time-series vs. part-to-whole)\n- Dashboard does not exceed 6–8 visuals per page to avoid cognitive overload\n- Refresh cadence aligns with the data pipeline schedule — no visual shows data newer than its source supports\n- [VERIFY] that metric definitions match the organization's chart of accounts and reporting standards (GAAP\u002FIFRS)\n- [VERIFY] data-access permissions ensure sensitive cost-center or compensation data is restricted by role\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26],"drafting","financial-planning-and-analysis","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":34,"practice_areas":36},"casemark",[32,33],"Drafting","Planning",[35],"New Document",[37,38,39],"FP&A","Management Accounting","Business Intelligence","2026-09-20","skills\u002Ffinance\u002Fcreating-management-dashboards\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fcreating-management-dashboards","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill creating-management-dashboards",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill creating-management-dashboards",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill creating-management-dashboards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fcreating-management-dashboards\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]