Operational workflow management
A time-off or equipment request goes out as a message, then vanishes somewhere between two inboxes. This tool gives every request a visible state, a named owner and a history that still reads months later. Everyone can see where their case stands without chasing anyone.
Context
A team with no IT department gets organised with whatever is at hand: a shared spreadsheet, a few message threads, a request made in passing in a corridor. While the volume stays low, it holds. Past a certain point, nobody knows who is supposed to approve what, or since when.
Challenge
An approval flow only becomes legible if people actually use it. Full enterprise software would have meant weeks of learning for teams with nobody to train them. The tool also had to hold up on a weak connection, or it would be back to the spreadsheet within a day.
Our approach
One list, states written out in plain words rather than internal codes, and nothing on screen that does not help someone decide. Every step is dated and attributed, so a stalled request comes with the name of whoever stalled it. It all runs on a lightweight server administered by the studio, so teams have no extra machine to watch over.
Result
The application runs on the studio infrastructure, monitored around the clock.