The biggest lesson from the Roche engagement was not about dashboards or automation.
It was about execution.
A good insight is not enough. A good recommendation is not enough. If the work cannot be explained clearly, measured, and handed off, it will probably not survive.
The reality of operational work
Operational environments do not reward vague ideas. They reward systems that reduce friction, clarify responsibility, and improve decision-making.
Across the engagement, the work required:
- mapping the real process, not the idealized one
- identifying handoffs and bottlenecks
- understanding why delays and rework happen
- designing automation concepts with exception handling
- creating dashboard views that make operational health visible
- packaging standard operating procedures for handoff
What made the work different
The project was not just analysis. It had to become something usable.
That changed the way I approached each deliverable. Instead of asking “is this interesting?” I had to ask:
- can someone else understand this quickly?
- does it map to a real workflow?
- what happens when the normal path breaks?
- what metric would show improvement?
- who owns this after our team leaves?
The product lesson
Every product is also an operational system.
Even a beautiful product fails if users do not know what to do with it, if stakeholders do not trust it, or if the next team cannot maintain it.
That is why the best product work is not just ideation. It is handoff, measurement, and adoption.
What I am taking forward
When I build AI products now, I think more like an operator:
- What is the workflow before the AI?
- What changes after the AI?
- What does the user do next?
- What does success look like?
- What breaks in edge cases?
- How does this survive beyond the builder?
That mindset is going into every product I build next.