Platform overview
One connected platform. Community-led change.
Wathaga brings data, policy frameworks and practical development projects into a shared learning cycle, across three connected areas.
Area 1
Community Theory of Change data portal
A shared place to describe the change communities want to make, collect relevant evidence and learn from what is happening.
Design principle: communities define the questions, protocols, access and use of their data.
Wathaga's eight Theory of Change headings
Area 2
Key issues & policy alignment
See where local change contributes to agreed commitments — and where gaps remain.
Alignment is a lens, not a substitute. Community-defined outcomes stay central; frameworks help organise evidence and communicate contribution.
Policy-alignment workflow
Area 3
Enterprise & development
Turn insight into action. Data projects help identify practical solutions and build the partnerships, capability and investment to deliver them.
From evidence to enterprise: identify a need → co-design a response → mobilise partners → measure outcomes → share learning.
The UMEL cycle
From community priorities to long-term learning
A Theory of Change is a living explanation of how change is expected to happen, not just a reporting template. The cycle repeats as communities learn, priorities shift and new evidence emerges.
What matters here? What change does the community want?
What evidence will show progress, and how should it be collected?
What is changing? What is working or not, and for whom?
What should be adapted, sustained or resourced next?
The Wathaga ecosystem
How everyone connects through Wathaga
Funders, providers, evaluators and communities work with Kowa's consultancy and learning services, and Wathaga connects them all. Select a group to see its connections.
Every group has a two-way connection with Wathaga.
Foundations
Trust, governance and sovereignty by design
Technology should support First Nations decision-making, not replace it.
Community authority
Agree who decides what is collected, why it is needed and how results are interpreted.
Controlled access
Set clear permissions, approvals, sharing protocols and responsibilities for each project.
Benefit & accountability
Projects return value to communities and report back in accessible, useful ways.
Important distinction. Platform code and intellectual property may be held by the developer; community data rights, ownership and control are established clearly in governance and agreements for each implementation.
