Every issue in this report includes the problem, why it matters, a suggested fix, and supporting evidence where the heuristics have it. Filter by category, then expand the cards that need a closer read.
Drill-down paths
Review structure first
Cross-check table design and linked relationships before applying fixes.
Weighted category scoring shows where the base is structurally solid and where issue volume pulls the overall score down.
Overall score: 62
22
Total findings
Schema quality
5 issues · weight 30%
60
Mixed
Workflow design
4 issues · weight 30%
61
Mixed
Data quality
6 issues · weight 20%
55
Needs work
UX opportunities
7 issues · weight 20%
73
Mixed
Sorted by severity, then category and confidence. 4 findings visible.
Structural or workflow friction impacting day-to-day usage.
4 items
Why it matters
Large status lists slow down triage, create near-duplicate states, and make dashboards harder to interpret.
Suggested fix
Collapse adjacent statuses into a smaller lifecycle or split planning-only states into a separate field if they truly serve a different purpose.
Why it matters
Workflow tables without ownership make queues harder to route and make generated workload views incomplete.
Suggested fix
Add an owner or assignee field, ideally as a collaborator or linked People record, so each item has clear accountability.
Why it matters
Operational work without a target date is hard to prioritize, escalate, or surface in overdue views.
Suggested fix
Add a due date, deadline, or SLA field so time-based reporting and reminders can work consistently.
Why it matters
Operational work without a target date is hard to prioritize, escalate, or surface in overdue views.
Suggested fix
Add a due date, deadline, or SLA field so time-based reporting and reminders can work consistently.