Case 07 / 14
Diyar
Diyar’s internal incident management system replaces email threads with a shared workflow for logging, assigning, tracking, and closing incidents. Built for Kuwait operations, it gives teams a single place to respond with clarity instead of chasing status across inboxes.
- Role
- Internal tools design & platform engineering
- Scope
- Incident management · Ops workflow · Internal app
- Region
- Kuwait
- Category
- Platform
Engagement flow
01 Discovery
Audited how incidents were raised and closed over email. Identified missing ownership, status ambiguity, and the need for a lean internal tool rather than a heavy ITSM suite.
02 Architecture
Modeled a simple incident lifecycle with reporting, assignment, status, and resolution as first-class states shared across the team.
03 Build
Shipped a focused internal app that makes logging, tracking, and closing incidents the default path for Kuwait operations.
04 Launch
Rolled out a shared workflow where incidents move from report to close in one place—without inbox archaeology.
01
What was broken
Opportunity
Internal incidents were getting lost in email: unclear ownership, inconsistent status, and slow closes. Teams needed a focused tool—not a bloated helpdesk suite—to report issues and see them through to resolution.
Diyar required a Kuwait-ready operational workflow: structured reporting, assignment, visible status progression, and a clean path from open to closed that every stakeholder could trust.
02
What we built
Approach
We designed a focused internal application around the incident lifecycle—report, assign, track, resolve—with just enough structure to create accountability without ceremony.
Status tracking and assignment surfaces keep ownership visible. The product stays lean so operators adopt it as the system of record instead of reverting to email.
Everything was shaped for internal Kuwait operations: shared workflow, clear states, and a report-to-close journey that teams can run every day.
03
Why it matters
Impact
Incidents move through one shared workflow instead of fragmented email chains.
Teams gain clearer ownership and a faster path from report to close for day-to-day operations.
[ Deliverables ]
What we shipped
- 01Internal incident management application
- 02Incident reporting and intake forms
- 03Assignment and ownership workflows
- 04Status tracking across the lifecycle
- 05Resolution and close-out flows
- 06Ops-focused UI for Kuwait teams
- 07Shared system-of-record workflow
[ Capabilities ]
Product surface
- 01Structured incident logging
- 02Team assignment and ownership
- 03Visible status progression
- 04Resolution tracking
- 05Shared operational workspace
- 06Email-chaos replacement workflow
- 07Internal-only access model
- 08Report-to-close lifecycle
[ Outcomes ]
What changed for the team
Qualitative results from the engagement—focused on clarity, control, and day-to-day usability.
Clearer ownership on every incident
Shared status instead of email guesswork
Faster path from report to close
Lean tool teams actually use
Operational consistency for Kuwait teams
One workflow for log, track, and resolve
[ Stack ]
Built with intention
03 capabilities
Internal app
Incident management
Operations
Need a system like this?
Let’s make yours the next file.