What We Are Learning Through MCC’s Peer-to-Peer Model

A different kind of support

Mob and Country Connections allows IRAAC to share systems, templates and lessons it has developed through its own governance work. The support is offered when another Aboriginal Community Organisation asks for it.

This peer-to-peer model recognises that organisations know their own communities. IRAAC can share experience while the receiving organisation remains responsible for its own choices and direction.

The value of peer support is practical. A conversation between organisations can begin with the real task in front of them: preparing a meeting, organising records, clarifying a responsibility, responding to a reporting request or building a consistent way to follow up actions. The starting point is the organisation’s own priority, not a standard package selected elsewhere.

MCC is therefore different from taking control of another organisation’s work. IRAAC can demonstrate a process, share an editable resource and talk through what it has learned. The participating organisation decides whether the material fits, what needs to change and who has authority to approve its use.

Why invitation and relationship matter

Capability support can become unhelpful when it arrives as a judgement about what an organisation lacks. An invitation-led approach begins with respect for existing knowledge, leadership and community responsibilities. It gives the organisation space to name the problem it wants to solve and the kind of assistance that would be useful.

Relationships also make it easier to discuss the parts of organisational work that are difficult to put in a formal request. A template may be simple, but the surrounding questions can involve workload, confidence, unclear roles or a history of systems that were introduced and then abandoned. Trust allows those practical realities to be discussed without turning them into public shortcomings.

This does not mean expectations should remain vague. A useful MCC engagement should still have a shared purpose, a clear contact person, agreed boundaries and a point at which both organisations review whether the support is helping. Relationship and accountability should reinforce one another.

What practical capability sharing can include

Support may involve governance calendars, meeting preparation, action registers, policy review, program records, funding acquittal preparation or ways to organise evidence for reporting. These examples describe areas of work, not a promise that MCC provides every professional service. Legal, financial, audit and specialist advice must remain with appropriately qualified people.

The most useful resource is often one that can be used immediately and changed locally. An editable agenda, decision record or reporting checklist can reduce the effort required to start. A short working session can then connect the tool to the organisation’s actual roles and deadlines. The aim is not a perfect document; it is a process that people understand and can maintain.

IRAAC should avoid transferring unnecessary information. Peer support may require seeing the structure of a process without receiving personal records, confidential Board material or community data. Before any document is shared, both organisations should agree what is needed, what can be de-identified and where working copies will be stored.

What IRAAC is learning

The lessons below describe the principles guiding MCC. They are not presented as measured program outcomes. Future reporting should distinguish what participating organisations have confirmed from what IRAAC believes may be useful based on its own experience.

One emerging lesson is that systems last when they fit the people who will use them. A detailed process can look impressive but fail if it adds work, depends on one person or uses language that is unclear. Capability grows when the organisation can explain the process, adapt it and continue using it after the immediate support ends.

• Trust and invitation are essential to a useful working relationship.
• Practical templates are most valuable when they can be adapted locally.
• Governance support should strengthen authority rather than replace it.
• Reporting systems can protect programs by reducing missed requirements and unclear responsibilities.
• Outcomes should be described only after participating organisations agree they are accurate.

A respectful working process

This process keeps authority visible. It also reduces the risk that support becomes a series of conversations with no usable result. Each engagement should end with an agreed action, owner and review point. If the need is outside MCC’s role, IRAAC should say so early and, where appropriate, help identify a more suitable source of assistance.

The participating organisation should be able to stop, change or narrow the work. Consent to receive support is not permission for IRAAC to use the organisation’s name, materials or experience in promotion. Public examples require separate agreement and should be checked by the organisation before release.

• Begin with the organisation’s stated priority and confirm what success would look like to them.
• Agree who can make decisions, who will do the work and what information can be shared.
• Use existing processes where they are working instead of replacing them without reason.
• Work on a real task so the support produces something immediately useful.
• Leave editable resources and a clear explanation rather than creating dependency on IRAAC.
• Review the engagement with the participating organisation before describing it publicly.

How MCC can strengthen reporting without taking it over

Reporting can be difficult when information is held across emails, notebooks, meeting papers and the knowledge of individual staff. MCC can help an organisation map where evidence is created and decide how actions, attendance, spending, outputs and community feedback should be recorded. The organisation remains responsible for approving the system and the final report.

A good reporting process starts before a deadline. It identifies what must be recorded during delivery, who checks the information and how differences between planned and completed work will be explained. This can reduce last-minute pressure and make it easier to give funders and community a truthful account of progress.

Reporting should not be reduced to positive stories. It should record what was completed, what changed, what could not proceed and what was learned. When community information is involved, public reporting should use de-identified themes and approved figures rather than detailed stories that could reveal who participated.

How progress should be assessed

MCC should be assessed by usefulness and ownership, not by the number of templates distributed. Possible measures include whether an agreed task was completed, whether staff can use the process without IRAAC, whether responsibilities are clearer and whether the organisation chose to continue or adapt the resource. Any measure should be agreed with the participating organisation.

Qualitative feedback matters because capability is not always captured by a count. Participating organisations can be asked what saved time, what created extra work, what felt culturally or organisationally appropriate and what they would change. Feedback should be invited without tying a positive answer to future access to support.

Public figures should appear only when records are complete, definitions are consistent and participating organisations have agreed that publication is appropriate. Until then, IRAAC should report the model, the learning questions and the improvements being made rather than inventing reach or impact.

What comes next

IRAAC will continue refining MCC through feedback from participating organisations. Future reports can include verified workshops, resources and outcomes once they have been approved for public release.

The next stage should clarify a simple engagement pathway: how an organisation expresses interest, how scope and boundaries are agreed, how work is recorded and how both parties close or continue the engagement. This pathway should remain flexible enough to respect different organisations while giving staff a consistent safeguarding and follow-up process.

IRAAC can also build a small library of editable resources based on repeated requests. Each item should identify its purpose, the decisions it cannot make and the parts an organisation is expected to adapt. Resources should be reviewed when legislation, funding requirements or organisational policy changes.

The next public update should report confirmed activity only after the relevant organisations have reviewed the description. It should explain what MCC helped with, what the participating organisation retained control over and what IRAAC learned about making peer support more useful. Where results are not yet measurable, the report should say that plainly.

Questions for future learning

These questions give MCC a learning agenda without pre-judging the answers. The program should develop through real invitations and feedback, with participating organisations shaping what good support means. The strongest evidence of success will be an organisation’s ability to own and use the result, not its resemblance to IRAAC’s internal way of working.

• Which practical tasks are organisations asking MCC to help with most often?
• What resources are being adapted and maintained after an engagement ends?
• Where does a peer-support role need to stop and qualified specialist advice begin?
• How can IRAAC reduce the information organisations need to share while still providing useful support?
• What do participating organisations say made the relationship respectful and effective?
• Which outcomes can be verified and approved for community reporting?