Service management
A service desk with a boundary that holds
Request intake, engineering tickets and documentation split into three layers that do not duplicate each other.
- Client
- Diagnostic imaging practice
- Period
- 2026
- Stack
- Service management platform, Issue tracker, Docs platform
The problem
Requests arrived by hallway, text message and email. Nothing had a queue, a priority or a history.
What I built
A service portal for people who need something, a separate engineering project tracker for the work itself, and documentation kept in one place with links instead of copies. The rule is enforced: docs live in one system, tickets in another, never both.
Result
Requests have a queue and an owner. The documentation stopped forking.
Service management platformIssue trackerDocs platform
All projects