Leading a cross-service change
I led an identifier migration across the platform's core services, coordinating five engineers, with no known client impact attributable to the team.
Next case studyReport requests to engineering fell by about 30%, as stakeholders built the simpler reports themselves in a configurable tool I built with Claude Code.
01
At a business-messaging platform, stakeholders asked engineering for reports through tickets. Reports were built with client-specific code or periodically synced spreadsheets and, even when the required data was known, a typical one took about a day of custom development.
02
I spotted the opportunity from the volume of report tickets, ran a short proof of concept and demonstrated it to stakeholders.
I then built a configurable reporting interface over the existing front end and contacts data, with Claude Code. It was lightweight custom code with no framework, replacing client-specific code and periodically synced spreadsheets, and the client teams’ reports were recreated in it.
When the required data was known, a report took minutes to configure. Report requests to engineering fell by about 30%, as stakeholders built the simpler reports themselves. Feedback from real use drove the useful changes to the interface.
Diagram of the reporting tool. A configuration form with three fields and a button leads, along an arrow labelled minutes, to a finished report table. When the required data was known, a report took minutes to configure.
03
Report turnaround
Minutes
down from a day of development, when the required data was known.
Report requests
about 30% fewer
report requests to engineering, as stakeholders built the simpler reports themselves.
04
I led an identifier migration across the platform's core services, coordinating five engineers, with no known client impact attributable to the team.
Next case studyContact
Tell me about your project, your team or the problem you're working on.
Or find me on LinkedIn