BI and reporting.
Dashboard craft for event teams. Metric definition and naming, row-level security, self-service against curated reporting, embedding for exhibitors, and report adoption.
21 articles · BI and reporting
- Show director dashboard design around three questionsshow director dashboard designShow director dashboard design works when the front page answers only the three questions a director opens the report to ask, and the rest sits behind a tab.
- Dashboard requirements gathering begins with a decisiondashboard requirements gatheringDashboard requirements gathering that starts from the decision the reader has to make, using a one page brief naming audience, cadence and the measures.
- Dashboard visual hierarchy decides what gets seen firstdashboard visual hierarchyDashboard visual hierarchy puts the number that triggers action top left and sizes it largest, using eyetracking evidence about where readers actually look.
- How many KPI tiles a page can carryhow many kpi tilesHow many KPI tiles a report page can carry before nobody reads any, worked as an attention budget in seconds and tested against a 22 tile page cut to six.
- The pre show countdown dashboard for the final weekpre show countdown dashboardA pre show countdown dashboard that fits one screen in the final week, with six tiles, one filter, and a refresh cadence the platform can actually deliver.
- Drill down path design that follows overview firstdrill down path designDrill down path design for event reporting: one hierarchy per page, overview first then zoom and filter, and a breadcrumb that shows which filter is applied.
- Drill through to record detail when a number is disputeddrill through to record detailDrill through to record detail gives every headline number a path to the rows behind it, so a disputed count can be opened, filtered by source and checked.
- Metric naming conventions that end the attendance argumentmetric naming conventionsMetric naming conventions that carry the population, filter and window inside the measure name, so three different numbers called attendance stop colliding.
- KPI tile labels that carry the filter and the windowkpi tile labelsKPI tile labels that state the population, the filter and the window under the number, so a figure quoted out of a report cannot be read two different ways.
- Metric definitions in tooltips beside the numbermetric definitions in tooltipsMetric definitions in tooltips put population, filter, source and last change date beside the number, so nobody has to open a data dictionary to read a report.
- Metric change control for the day a definition changes mid yearmetric change controlMetric change control for event reporting: version the measure, keep the old definition live for one edition, and mark the changeover date on every chart.
- Certified versus ad hoc reports and the badge that tells readers whichcertified versus ad hoc reportsCertified versus ad hoc reports: two tiers, four entry criteria and a badge that tells a reader whether the number in front of them is the number of record.
- Row level security for event portfolios where a director sees only their showrow level security for event portfoliosRow level security for event portfolios: filter the show dimension once, let the fact tables inherit it, and understand why a contributor still sees every show.
- Dynamic row level security mapping tables beat one static role per showdynamic row level security mappingDynamic row level security mapping replaces one role per show with a user to show table, a single filter expression and access changes made by editing rows.
- Testing row level security before one exhibitor can see another exhibitor datatesting row level securityTesting row level security with a matrix of users, expected row counts and expected totals, run through an impersonating query API instead of by eye.
- Workspace permissions for event teams that stop everybody becoming an adminworkspace permissions for event teamsWorkspace permissions for event teams: four roles, consumers in an app audience, two admins, and a membership review timed to the close of each edition.
- Sensitivity labels on event reports so exports carry their classification outsensitivity labels on reportsSensitivity labels on reports travel with exports to Excel, PDF and PowerPoint, never to CSV, and inside the service they classify without restricting access.
- Object level security when the row is fine but the column is notobject level securityObject level security hides a table or column outright, so the field leaves the field list entirely and any visual or measure that referenced it stops working.
- Embedded analytics for exhibitors inside the portal they already log intoembedded analytics for exhibitorsEmbedded analytics for exhibitors puts one report definition inside the portal they already use, passing identity from the session so nobody signs in twice.
- Multi tenant analytics isolation so one exhibitor never sees another set of rowsmulti tenant analytics isolationMulti tenant analytics isolation: three patterns for exhibitor reporting, why the common one leaks, and where to put a tenant predicate so it cannot be missed.
- Embedded report authentication tokens that never trust a client supplied idembedded report authentication tokensMint an embedded report authentication token on the server, carry the tenant claim inside it, and filter at the data layer so a rewritten URL returns nothing.