Designed a time‑management and reporting system that remained in production use for years without significant modification.

Situation. The team didn’t have a dependable way to manage time and report progress. Which usually means it’s happening in a scatter of spreadsheets and memory, and the reporting turns into a scramble at the end of each period rather than something that just falls out of how people work.

Task. Building a system for both that would actually last was the task.

Action. A time‑management and reporting system was designed around how the team actually worked, rather than imposing some off‑the‑shelf process they’d route around. That’s the whole trick with internal tools — if it fits the real workflow, people use it; if it fights the workflow, they quietly abandon it and you’re back to spreadsheets. So it was built to match reality rather than an ideal.

Result. It stayed in production use for years without any significant modification. That’s the compliment you want for an internal tool — not that it was impressive, but that it just kept working and nobody ever needed to replace it. Something that survives years of daily use untouched was clearly built to fit.