From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 32 of 60
-
Triage Incorrect Units and Labels in Reports
Compare measure definitions, raw values, scaling, chart labels, and exports to locate where a report changes or misstates a number’s unit.
-
Prioritize Misleading Report Units
Assess unit and label defects by changed interpretation, decisions affected, shared measure reach, and the clarity of an alternative correctly labeled view.
-
Investigate Unit Conversions and Report Labels
Trace source units, aggregation, conversion order, formatting, and shared labels with known values that distinguish a scaling error from a presentation mismatch.
-
Verify Report Values and Units Stay Consistent
Check known magnitudes, conversion order, series labels, tooltips, tables, and exports against an explicit unit contract for the affected measure.
-
Keep Report Units Clear as Measures Change
Document measure units and conversion ownership, and preserve known-value fixtures that expose mismatches across charts, tables, tooltips, and exports.
-
Triage Unexpected Totals in Pivot Reports
Compare visible cells, underlying records, aggregation rules, filters, and total calculations to identify why a pivot’s total differs from reader expectations.
-
Prioritize Confusing or Incorrect Pivot Totals
Assess pivot-total issues by decisions affected, non-additive measures, hidden populations, shared report use, and the clarity of the total definition.
-
Investigate How a Pivot Calculates Its Totals
Trace aggregation grain, overlapping groups, filters, and total expressions with a small dataset that distinguishes cell sums from recalculated measures.
-
Verify Pivot Totals Against Their Measure Definition
Check additive and non-additive measures, overlapping identities, unequal groups, filters, and hidden categories against independently calculated pivot expectations.
-
Make Pivot Total Definitions Easier to Maintain
Document additive and non-additive total semantics and retain small fixtures that expose overlapping groups, unequal weights, and hidden population changes.
-
Triage Dates Displayed Out of Order in Reports
Compare raw date values, period keys, formatted labels, and sort settings to locate a report that orders time as text or reorders it during presentation.
-
Prioritize Chronological Sorting Defects in Reports
Assess timeline ordering problems by misleading trends, affected period formats, shared views, recovery controls, and whether readers can see the active sort.
-
Investigate Date Labels and Time Sort Keys in Reports
Trace raw dates, grouped period keys, label formatting, saved sort state, and rendering with fixtures that expose lexicographic rather than chronological order.
-
Verify Reports Sort Time by the Intended Key
Check year boundaries, repeated period labels, saved sorts, chart order, and exports against independently defined chronological and ranking sequences.
-
Keep Report Time Keys Separate From Date Labels
Document ordering semantics and retain period fixtures that expose text sorting, year-boundary ambiguity, saved-state drift, and inconsistent export order.
-
Triage Misleading Baselines in Report Comparisons
Compare current and baseline definitions, populations, filters, time coverage, and units before interpreting a displayed increase or decrease as a real change.
-
Prioritize Incorrect or Unclear Report Baselines
Assess baseline comparison issues by decisions affected, population mismatch, shared report reach, clarity of context, and the availability of a comparable reference.
-
Investigate Population and Definition Drift in Baselines
Trace current and baseline filters, measure versions, coverage, and comparison arithmetic using matched and deliberately mismatched report fixtures.
-
Verify Report Baselines Are Comparable and Clear
Check matched definitions, intentional differences, filter changes, unavailable baselines, and displayed change calculations against explicit comparison expectations.
-
Keep Report Baseline Definitions Traceable
Document comparison populations and preserve matched fixtures so changing filters, measures, or benchmark context cannot silently alter the meaning of reported change.
-
Triage Missing Context in Scheduled Report Snapshots
Compare the scheduled definition, applied filters, data timestamp, generated artifact, and interactive report to locate context lost during snapshot creation.
-
Prioritize Context Gaps in Scheduled Reports
Assess scheduled snapshot problems by misleading interpretation, affected recurring views, missing filter or freshness labels, and the ability to reconstruct the original result.
-
Investigate Scheduled Report Snapshot Context
Trace saved schedule parameters, data freshness, generation inputs, artifact labels, and destination links to locate where a report snapshot loses its meaning.
-
Verify Scheduled Snapshots Preserve Report Context
Check filtered variants, period labels, data freshness, generation time, values, and destination links in controlled scheduled-report artifacts.
-
Keep Scheduled Report Snapshots Self-Explanatory
Document snapshot context and retain distinct schedule fixtures so filters, periods, freshness, and destination behavior remain clear after generation.