Situation Awareness Cockpit
Instead of ‘replace a paper’, rethink how context is transferred.
Lesson
Be wary of the telephone game; dare to rethink the entire experience, while navigating challenging politics.
The lesson in full: Stepping into the ‘full-stack’ role again gave me a new perspective on what happens when the end user is not an integral part of the development cycle. The ‘telephone game’ effect is dangerously real in a B2B context, where multiple layers of product management, sales, deployment teams and development teams can distort original user needs. What’s even harder is dealing with the consequences of such distortion, keeping everyone happy, understanding the root of user needs and finding ways to deliver real value.
What it is
My temporary return to the deployment role after 2 years away (since Trinidad & Tobago in 2021), for a North American LNG operator. The original discussion was: ‘When changing shift, one has to read a paper that the previous shift wrote, to be aware of what happened’. The telephone game of product management led to less than ideal feature development where teams were trying to ‘replace the paper’ with digital twin features, trying to tick boxes. As both sides sat together in the same office, we realized it’s not the paper that users care about, it is the transfer of context to be aware of the situation. This led to a complete UX rethink: how the ‘at a glance’ experience should be designed. This project introduced many new core concepts for Kognitwin focusing on the time dimension: shift, handover, process roles, operation rounds, etc.
Tools and technologies
Zero-to-One · UX · B2B
Lineage
Built on lessons from Digital Twin Platform, First Global Twin Deployment, Deployment CLI and SDK.
Lessons carried into UX Reboot and Design System.