The challenge
A large, geographically distributed asset-management environment depended on records flowing across multiple systems, user groups, and operational processes. Duplicate records, status conflicts, inconsistent permissions, and incomplete transactions could make it difficult for managers and field teams to understand where action was needed.
My role
I served as a business systems analyst and administrator connecting field users, program leadership, developers, system administrators, technical SMEs, trainers, and reporting stakeholders. My responsibility was not simply to produce a report; it was to trace the issue, clarify ownership, and make the output usable.
Approach
- Collected examples from users and separated symptoms from root causes.
- Traced records across asset-management, ERP, reporting, and reference-data workflows.
- Defined exception categories such as duplicates, status mismatches, inactive records, access issues, and unresolved transactions.
- Designed reporting views that helped leaders prioritize by severity, location, and issue type.
- Created supporting guidance so users understood both the exception and the required action.
| Location | Issue | Severity | Owner | Status |
|---|---|---|---|---|
| Site 104 | Duplicate asset record | High | Data steward | In review |
| Site 218 | Status mismatch | Medium | Field coordinator | Assigned |
| Site 331 | Missing reference value | Low | System admin | Queued |
Outcome
The work improved visibility into data-quality and adoption gaps across a platform serving more than 2,000 users at 397 locations. Leadership and field managers gained a clearer way to prioritize exceptions, while users received more consistent guidance for resolving them.
What this demonstrates
- Systems thinking across interconnected platforms
- Root-cause analysis and data reconciliation
- Dashboard design tied to operational decisions
- Governance, documentation, and distributed stakeholder support