The problem

• Broad sustainability monitoring aspirations, no operational concept, low organisational capacities.

Context

A central idea was to create monitorable sustainability evidence by identifying indicators, collecting or sourcing data, building a database and display method, and translating findings into public information products. In principle, the concept made sense and wasn’t new. It sought to connect sustainability priorities, monitoring, public awareness, and stakeholder action.

The concept was at a very early stage. Important practical questions were not yet resolved. It was unclear which data would actually exist, which institutions would share them, where new data would need to be created through surveys or research, what technical and staffing capacity would be needed to manage the system, and how such a model could realistically be operated. Some ambitions were attractive at the level of vision, but not yet grounded in a realistic delivery structure.

What was needed was not simply a more polished presentation of the concept, but a revision that would make the hidden complexity visible. That meant mapping into a roadmap what the organisation wanted to achieve against what would be required to do it in practice.

My role

I developed a roadmap framework that translated the broad idea into a more structured planning logic. The purpose was not only to organise the concept, but to diagnose its feasibility on paper and lay out what implementation steps are required. I used the roadmap to clarify what the original ambitions would actually require in terms of systems, roles, resources, dependencies, and sequencing. In effect, I helped move the conversation from aspiration to implementation reality.

What I did

I turned a broad vision into a more structured roadmap by:

• mapping intended outcomes, outputs, actions, dependencies, risks, and resource needs into one planning framework
• making visible the missing links between the vision and what an indicator monitoring tool would require in practice
• clarifying the minimum delivery requirements behind the ambition, including data access, survey capability, software and visualisation needs, institutional cooperation, and internal staffing capacity
• showing that the aspired model was not a single product, but a chain of interdependent systems that would require sustained technical and organisational support from various stakeholders beyond the organisation
• using the roadmap to distinguish between what was already possible with existing strengths and what would depend on capacities not yet available
• creating a more structured basis for strategic discussion, so leadership could see where the original concept was too broad, too under-specified, or too resource-intensive for development

Outcome

The roadmap did not become a final programme in itself. Its value was diagnostic. It made visible how complex the original ambition would be to deliver and helped clarify that the organisation’s more realistic starting point lay elsewhere.

What this case shows

This case shows my ability to use programme architecture as a diagnostic tool, not just a design exercise. It demonstrates how I work when an organisation has a strong idea but has not yet translated it into operational reality. Before simply developing the expected concept further, I mapped the missing systems, exposed the hidden complexity, and helped clarify what would actually be required to deliver it.

It also shows a broader pattern in my work: I do not only build frameworks. I also stress-test ambitions, identify capability gaps, and help organisations distinguish between what is attractive in theory and what is feasible in practice.