KyoMel / Yogyakarta, Indonesia

Case 0303 / 04

Incident reporting

An incident reporting feature that cut reporting time by 60% and raised data accuracy by 40%.

Role
Software Engineer, Xapiens Teknologi Indonesia
Period
Feb 2021 - Apr 2024
Stack
React, Node.js, SQL
Artifact
Private - internal product, no public link

Problem

Incident reports were written after the fact, in free text, by whoever was on shift. The data arrived late and could not be compared across incidents.

Decisions 2

Structured fields over free text

The report became a form with typed fields, so incidents could be queried and compared.

CostA longer form than a single text box, and the fields have to cover the common cases.

Report at the moment of the incident

The form is short enough to fill while the incident is still open, on the device the responder already holds.

CostThe UI has to work on a phone, not only on a desk machine, which constrains the layout.

Outcome

  • -60%Time to file an incident report.
  • +40%Accuracy of the incident data.

Next