Data, AI & institutional capacity

Operationalising data for global governance

My work concerns how institutions put data to use: how it informs decisions, directs resources, and becomes part of the daily work of delivering public services.

Since 2018, I have led product development at mWater, working with governments, utilities, and development partners around the world to put data into operational use.

I have helped shape strategy, launched Solstice, and written about data, AI, and institutional capacity. I am also Venture Lead at Stellar Data. Across these roles, I combine product leadership with consulting, training, and software development.

I am interested in how AI can extend this capacity, and what it takes for institutions to understand, govern, and sustain the systems they rely on.

Petri Autio at his desk with mWater dashboards on screen
Petri Mikael Autio · Head of Product

390K+registered users

200countries & territories

50M+survey responses

mWater platform figures.
September 2026 · Full product record →

Selected work

Decisions behind the products

From launching Solstice to shaping shared tools: examples of my leadership, working with our team and partners.

01 / Product and venture leadership

Solstice: from an idea to adoption across sectors

When I joined mWater in 2018, Solstice was an idea for extending the platform beyond water and sanitation. I led its development into a product: shaping the brand and positioning, implementing the app deployment and parallel portal, and managing projects, staff, and partner relationships.

At Medair, I encouraged the WASH team to adopt the Solstice identity so the system could find a home in other parts of the organisation. Its use subsequently expanded into health and other areas. This was the wider purpose: make shared infrastructure useful across institutional responsibilities.

By September 2026, Solstice had grown to more than 42,000 registered users across 155 countries. At that point, Solstice accounted for approximately one in five registrations across mWater and Solstice during 2026.

Internal platform registration data, September 2026. Registered accounts, not active users.

How I developed and grew Solstice →
02 / AI access

A useful way in for AI agents

Users were bringing AI assistants to a platform built for people, and they needed capable access without losing control of their data.

My role
Product leadership and the platform’s published AI strategy.
Design choice
Give agents a supported, permission-aware route in, with people reviewing proposed data changes. Subsidised use with daily caps to democratise access to AI-boosted work.
In practice
Free in-built features help users do more in key areas such as data analysis. The MCP server connects assistants to users’ data. The Integrator helps practitioners connect external systems in plain language.
Read the strategy and lessons →
03 / Operations

From a reported fault to a repair

Operationalising data processes so that users can assign the work, follow it through, and check the result.

My role
Product leadership for Workflows, developed with investment from UNICEF Madagascar.
Design choice
Let organizations define their own steps, responsibilities, and reviews within the platform.
In practice
By August 2026, users had created nearly 10,000 workflow instances across about 170 types.
Read nine months of Workflows →

Much of this work takes shape with public institutions, including national systems in Zimbabwe, Uganda, Madagascar, and Papua New Guinea. My work also includes CRS Azure, which spans multiple countries.

Government and deployment experience →Browse the full product record →

Shared infrastructure for water and sanitation

mWater’s larger contribution is shared data infrastructure for water and sanitation. Governments, utilities, and development partners can build on the same tools rather than commission separate systems for each project. Improvements funded for one organisation become available to everyone, reducing duplicated development and helping teams spend more of their effort on delivering services.

What changes in practice

Published accounts from mWater and its partners show how the shared platform fits into daily work.

Uganda · RUMIS. The 2023 case study describes field collection and database updating becoming a single task, with local, district, and national staff accessing the same information. Read the RUMIS case study →

DR Congo · Yme Jibu. In a 2025 account, the utility’s database manager reports easier data centralisation, automated monitoring, and invoices generated directly in mWater. Read the utility’s account →

Writing

Articles and reflections

All writing →
About me

Technology, institutions, and the people using both.

Before mWater, I worked on global information systems at WaterAid and mapping tools at the British Red Cross. That experience still shapes how I think about product development: the software has to fit the responsibilities, resources, and working lives around it.

I have done extensive consulting and training through UpBeam Oy, including engagements with WaterAid, the Netherlands Red Cross, and Water For People. Away from the product roadmap, I explore philosophy, writing, and small interactive projects.

Contact

Contact and speaking

Get in touch about product and AI strategy, putting institutional data systems into practice, training, or speaking. Tell me about your organisation, the problem you are working on, and the kind of contribution you have in mind.

Connect on LinkedIn ↗