The problem
Plant scientists needed visibility into cases that still required attention. Finding the relevant items manually was another step in the daily workflow.
The approach
A scheduled AWS job collects outstanding items and sends a structured overview through the Slack API, using Slack’s table functionality. The workflow can post each morning around 09:00.
The challenge
The useful part is a clear overview at the right moment. The message needs enough structure to scan quickly while keeping the underlying internal records private.
Outcome & value
A repeatable morning overview in the team’s existing workspace. It reduces the need to assemble the same overview by hand and makes pending reviews easier to notice; no time-saving metric is claimed.
Lessons learned
Small automations can be useful products when their timing, structure and destination fit the people doing the work.
This case describes my contribution at a conceptual level. Internal data, code and dashboards remain within Vivent.