The path exists - it's just not well signposted
Many of the most effective systems advocates in Australia started as peer workers. They came into the sector through their own experience - of mental health systems, housing instability, disability services, child protection, or substance use - and found that their knowledge was valuable in ways the sector was only beginning to understand.
But the pathway from peer worker to systems-level role is rarely clear. There are no formal ladders. The skills that make someone an excellent peer worker - relational depth, lived knowledge, the ability to hold complexity - are not always recognised in job descriptions for policy or advocacy roles.
This guide is for people who feel the pull toward systems change work and want to understand what the path actually looks like - including the parts that are hard.
What "systems advocacy" actually means
Systems advocacy is work that aims to change the structures, policies, and practices that shape people's lives - rather than supporting individuals within those structures. It operates at the level of organisations, governments, and sectors.
In practice, systems advocacy roles might include:
Policy advisor or analyst
Contributing lived experience knowledge to the development or review of policy frameworks.
Consumer or carer representative
Sitting on boards, committees, or advisory groups to represent the perspectives of people with lived experience.
Lived experience consultant
Working independently or within organisations to advise on co-design, service design, or workforce development.
Advocacy organisation staff
Working within peak bodies or advocacy organisations to influence systemic change.
Researcher or evaluator
Contributing to research that centres lived experience, including participatory action research.
Trainer or educator
Building the capacity of organisations and workforces to work effectively with people with lived experience.
The skills you already have
Peer workers often underestimate how much they already know. The skills developed through peer work are directly applicable to systems advocacy - they just need to be named and framed differently.
Translating experience into insight
You know how to take what happened to you or others and draw out what it means for systems. This is exactly what policy advisors and consultants do - you've been doing it informally for years.
Holding complexity
Systems are messy. People's lives are messy. Peer workers are trained to sit with that complexity rather than reduce it. This is a rare and valuable skill in policy and advocacy environments.
Relational credibility
You can speak to the experience of people who use services in a way that no amount of data can replicate. Organisations and governments increasingly recognise this - even if they don't always act on it well.
Navigating systems as a user
You know what it actually feels like to interact with the systems you're now trying to change. That knowledge is not abstract - it's embodied, and it's powerful.
Facilitation and group work
Many peer workers have significant experience facilitating groups, running workshops, or supporting people through difficult conversations. These skills transfer directly to co-design, consultation, and training roles.
What the transition actually requires
Moving into systems advocacy work is not just a career change - it often involves a significant identity shift. Here's what to expect:
Learning the language of systems
Policy, governance, and advocacy environments have their own language - and learning it matters, not because your language is wrong, but because fluency in both gives you more power. This doesn't mean abandoning how you speak; it means adding to your repertoire.
Building formal credentials (strategically)
Some systems advocacy roles require formal qualifications - social work, public health, policy, law. Others don't. Before investing in study, research the specific roles you're interested in and talk to people already doing them. Credentials can open doors, but they're not always the most direct path.
Managing the emotional weight
Systems advocacy work can be deeply frustrating. Change is slow. You will sit in rooms where your knowledge is valued in theory but ignored in practice. You will watch decisions get made that you know are wrong. Having strong support structures - supervision, peer networks, personal boundaries - is not optional.
Deciding how much of yourself to share
In peer work, disclosure is often central to the role. In systems advocacy, you have more choice about how much of your personal story you share, and with whom. Some people find this liberating; others find it disorienting. There's no right answer - but it's worth thinking about before you're in the room.
Practical steps to get started
Map your experience
Write down everything you've done in peer work - not just job titles, but skills, projects, outcomes. Include informal work: advocacy you've done, groups you've run, training you've delivered. This becomes the foundation of how you present yourself.
Identify the specific area you want to influence
Systems advocacy is broad. Mental health policy, disability rights, housing reform, child protection - these are different fields with different cultures and entry points. Getting specific helps you target your development and your networks.
Find the people already doing it
LinkedIn, sector events, peak body networks, and community of practice groups are all places to find people in systems advocacy roles. Ask for informational conversations. Most people are willing to talk - especially those who came through peer work themselves.
Look for bridging opportunities
You don't have to make a clean leap. Look for roles or projects that bridge peer work and systems work - consumer advisory roles, co-design projects, sector consultations. These build your profile and your confidence in systems environments.
Get clear on your boundaries before you start
Before you move into a systems role, know what you're willing to share, what you're not, and what conditions you need to do the work sustainably. It's much harder to establish these once you're already in the room.
A note on being used vs. being heard
Not every systems advocacy opportunity is a good one. Some organisations want a lived experience voice in the room to tick a box - not to actually change anything. Learning to tell the difference is one of the most important skills you can develop.
Signs that an opportunity is genuine: your input is sought before decisions are made, not after; you're paid fairly for your time; there's a clear mechanism for your input to influence outcomes; and you're treated as an expert, not a case study.
Signs to be cautious: you're asked to share your story without a clear purpose; there's no budget for your time; your input is sought but the decision has already been made; or you're the only person with lived experience in the room and expected to represent everyone.
The sector needs people who've been inside the system.
The most effective systems change happens when the people designing and influencing services have genuine knowledge of what it's like to use them. That's you. The path isn't always clear, but it exists - and it's worth taking.
Coming Soon
Membership for Advocates & Peers
Exclusive resources, monthly content drops, and a community of people who understand what it costs to show up. Join the waitlist to be first in.
Join the waitlist