Who
A global manufacturer with a head office in Switzerland, five departments running projects five different ways, and nobody able to see the whole picture. I was the non-technical intern who built the thing that fixed it.
The problem
Every status question meant a meeting, and every meeting produced a slide instead of an answer. The reporting was not the real problem. Five teams kept five versions of the truth, and reconciling them was somebody's full time job.
What I built
| Stage | What I did | Output |
|---|---|---|
| Map | Sat with all five departments and wrote down how each one really tracked work. | Five ways of working, on paper |
| Agree | Got the five to agree one shape for a project, which was the hard part and none of it was technical. | One definition everyone signed |
| Build | Built the platform on SharePoint with JSON configuration, inside their own environment, with no new vendor. | 200+ projects in one place |
| Automate | Wired the reporting so the executive view builds itself from the same data people already enter. | Reporting with no reporting work |
| Adopt | Ran the change work: training, floor-walking, and fixing what annoyed people in the first weeks. | Five departments actually using it |
Results
- S$370,000 a year, measured by the business itself at handover as CHF 244,000.
- Delivery got three months faster against the previous year's cycle.
- It is still running today, years after the person who built it left.
What I carried forward
The software was the small half. Getting five departments to agree on what a project even is was the work, and no tool does that for you. Every engagement since starts with the same question: who has to agree before this can be built.



