On this page
Product leadership, an exploratory flood-risk digital twin and the value of making complex information understandable.
I joined OSC in Norway as a Software Product Manager in August 2022 and subsequently took on the role of Head of Creative, working there until June 2025.
At OSC, my work spanned product leadership, experience design, systems architecture and technical direction. I looked for practical opportunities to modernise established software and developed working alternatives that colleagues could examine, rather than relying exclusively on proposals.
I designed and built an exploratory Flood Risk Digital Twin proof of concept using Cesium, terrain and Norwegian flood-related information. It made an alternative spatial experience tangible: interactive scenarios, visual overlays and explanatory information could be considered together. The work was research and development, not a deployed flood-warning service.
Questioning an established approach
The existing software environment presented opportunities for modernisation. It involved a substantial legacy implementation, and I could see possibilities for a different approach to visualisation, accessibility and the way users interacted with geographic information.
Rather than begin with a large proposal to replace everything, I developed a prototype to explore what a modern spatial experience might look like.
The purpose was not to reproduce all the functionality of an established application. It was to investigate whether a different technical foundation could make certain problems easier to solve and certain information easier to interpret.
The working prototype gave colleagues something concrete to assess and helped establish a possible direction for further product development.
Bringing data into the landscape
My proof of concept used Cesium to present an interactive three-dimensional geographic environment. I worked with terrain, geographic datasets and Norwegian flood-related information to explore how different conditions could be represented in a spatial context.
The prototype supported scenario-style exploration using numerical sea-level inputs, with visual overlays communicating differences in severity. Explanatory information and graphs helped connect the visual presentation to the underlying data.
I was particularly interested in the user’s journey from a question to an understandable result.
A person considering a coastal location shouldn’t have to begin by understanding how a data pipeline, a geographic information system or a 3D rendering engine operates. The interface should help them frame the question, explore the relevant information and understand the limitations of what is being shown.
I experimented with natural-language interactions as one way to support that journey. The intention was to help people express an enquiry and navigate the resulting view, not to treat an AI-generated explanation as independent scientific evidence.
Later experiments also considered additional environmental information, including sea-surface temperature data. These were exploratory extensions, not validated predictive science.
Engineering beyond the screen
A spatial application is not simply a map with an attractive interface.
The useful work sits in understanding the data, shaping it appropriately, defining the spatial relationships, preparing meaningful scenarios and deciding what the presentation should communicate.
I worked across those concerns, from data preparation and spatial logic to interactive presentation and the overall product experience.
The visual decisions mattered because the information could be misunderstood if its meaning was not clear. Colours, overlays, graphs and explanatory text had to be treated as parts of an intelligible system, rather than decorative features.
I also explored related questions around sensor hardware and streaming information, including discussions with a maritime academic at NTNU with whom I had previously worked. That work provided useful context for thinking about how real-world measurements might connect to digital representations.
It should not be confused with independent validation of the flood-risk model. The prototype was an engineering and product exploration, not a formally certified scientific forecasting system.
What the prototype demonstrated
The prototype attracted positive interest from people familiar with the existing software and the wider technical domain.
I received encouraging feedback from colleagues and from an academic with maritime expertise. Later conversations also acknowledged the direction I had identified for the software and its potential as a basis for further development.
That response mattered. The prototype demonstrated a credible alternative product direction, even though it was not a scientifically validated forecasting system or a completed production replacement.
What I had demonstrated was a tangible alternative approach: a way of bringing geographic information, scenarios and user interaction together in a coherent experience.
That was the R&D outcome.
Security and organisational practice
Alongside my product and development responsibilities, I also introduced information-security practices informed by ISO/IEC 27001.
This drew on earlier work in website security, audits, remediation and helping organisations work towards more formal information-security management.
I brought established security and assurance experience into the work, helping introduce more structured practices informed by ISO/IEC 27001.
I regarded that as part of responsible engineering rather than something separate from product development.
A familiar thread
Looking back, the flood-risk prototype drew on interests I had been developing for years: location technology, user experience, complex information, software architecture and practical experimentation.
The technical challenges were substantial, but the guiding question remained straightforward.
How can the system help someone understand what matters and make a better-informed decision?
That question is not unique to geographic modelling. It applies to almost every complex application I have worked on.
The purpose of a sophisticated system is not to demonstrate its sophistication. It is to make something difficult more useful and understandable.
Project context
Topic: Digital twins
Explore further
Further reading is listed below.