SPEAKER_00 0:46

Episode thirty nine Inside Serena Russo, an Australian governance benchmark. For the last two weeks I have been walking through the two most common pathways to governability in the RTO sector. Scale, where systemization forces coherence across distributed delivery. And specialization, where narrowed scope shortens the signal chain and makes drift easier to read. This week I want to take you into the pathway most RTOs assume they cannot achieve. Diversification. Diversified providers operate across multiple service lines, training delivery, employment services,

Why Diversification Feels Ungovernable

SPEAKER_00 1:32

apprenticeship support, workforce programs, commercial contracts, funded programs. Each line has its own rhythm, its own reporting language, its own cadence, its own definitions of what progress means and what success means and what variance means. From a governance perspective, this is the hardest pathway. Scale gives you a single operating logic to systemize across. Specialization gives you a single operating logic to stay within. Diversification gives you multiple operating logics that all have to be reconciled into a single governance view. Most RTOs that attempt diversification end up governed by aggregation. The portfolio looks stable because the numbers average out. Underneath, one line is quietly deteriorating while another is quietly compensating. Governance receives a calm report. The underlying condition is anything but calm. Some organizations have cracked this. Serena Russo Group is one of them, and today I want to walk through what they have figured out and what every RTO running more than one service line can learn from their design. Before I get into the pattern, I want to set some context. Serena Russo Group has been operating in Australia for more than forty years. It began as a small training operation in Queensland and grew through a combination of organic expansion, strategic diversification, and careful integration into one of the most structurally diverse organizations in the sector. Today, the group spans job services, apprenticeship support services, registered training delivery, higher education pathways, and international student services. Each of those is effectively a distinct operating business with its own regulatory framework and reporting obligations. The reason I'm using Serena Russo as the benchmark this week is not that they are perfect. No organization is. The reason is that they have demonstrated over a sustained period and across multiple regulatory cycles that diversified operation can be governed coherently. Most diversified providers in the sector cannot make that claim. Most are governed by aggregation. Serena Russo is not, and understanding the design decisions that separate those two modes of operation is directly useful. Even if your RTO is a fraction of that size. Here's the problem this episode addresses. Diversification is often presented as a stabilizing strategy. Spread your revenue across multiple sources. Reduce your dependency on any single funding stream. Build resilience through portfolio breadth. That is a valid commercial argument. And at the level of revenue risk, it works. A diversified provider is genuinely less exposed to the loss of any single contract or funding source than a narrow scope provider. But from a governance perspective, diversification introduces a specific form of exposure that most leadership teams underestimate. As service lines increase, so does your capacity

The Aggregation Trap And Hidden Drift

SPEAKER_00 5:12

to tell a coherent portfolio story. Activity can remain strong. Performance can appear balanced. Overall indicators can sit within tolerance. And at the same time, drift can develop within individual lines without disturbing the aggregate view. The organization appears stable on the surface. It becomes uneven beneath it. The tension is structural. Accountability is held centrally. Governing persons are responsible for the whole organization, but proof is produced across multiple programs, partners, and systems. Each line generates its own data. Each has its own definition of progress. Each has its own interpretation of what sits within tolerance. Without alignment, those differences do not cancel out. They compound. And averages then become the mechanism through which divergence is concealed. Governance receives a stable narrative. Escalation slows, not because issues are absent, but because variance cannot be located with precision. The issue is not a lack of information. The issue is that the information cannot be compared in time. This is the diversification paradox. You have more data than a specialized provider. You have less useful signal. Let me ground this in the twenty twenty five standards before I get to the case. Under the twenty twenty five outcome standards, the obligation to maintain continuous assurance applies to the whole organization, not line by line. Governing persons must be able to see the state of the organization continuously, not the state of the training function separately from the state of the employment function, separately from the state of the apprenticeship function. The state of the organization. This is the obligation that makes diversification specifically hard under the new regulatory environment. Under the pre 2025 standards, you could

Continuous Assurance Under 2025 Standards

SPEAKER_00 7:29

run each line as its own operating silo and satisfy compliance by demonstrating coherence at the line level. That is no longer sufficient. The regulator can now ask a crossline question. What did the organization know about participant experience across its services in Q2? That question requires an end-to-end answer. It requires crossline comparability. It requires the ability to trace a participant's journey through employment services, into training, through assessment, and into employment outcomes as a single narrative with consistent definitions and contemporaneous evidence at every handover. If your service lines do not share common definitions, you cannot answer that question in a time frame the regulator finds credible. The organization is forced to assemble the answer from fragmented records across systems and teams under pressure. This is exactly the condition benchmark diversified providers have designed to avoid. Let me walk you through what that design looks like. Serena Russo Group is the Australian benchmark for diversified operation in the VET sector. Their portfolio spans employment services, apprenticeship and traineeship support, and training delivery. Each of these functions operates with its own cadence, its own regulatory framework, its own funding mechanics, its own reporting structure. From the outside, this looks like three separate businesses. From a governance perspective, it has to function as one. And the thing the benchmark diversified providers have in common is this. They treat comparability across lines not as a reporting preference, but as an operating

Serena Russo’s Three Governance Moves

SPEAKER_00 9:29

condition. Comparability is not something their governance team tries to produce when a question comes in. It is something the organization builds into how data is captured at source. Three design moves characterize this. The first move is participant level common definitions. A participant in an employment service means something different to a student in training delivery means something different to an apprentice in workforce support. Those are three different operating categories. The benchmark, diversified providers don't pretend these are the same. They maintain the distinction, but they also build a layer above that. A participant level view that allows the organization to see the same human being as they move through multiple services with consistent definitions of what active, progressing, at risk, exited, and outcome mean across lines. This is hard. Each service line has its own compliance and reporting framework that uses these terms differently for funding purposes. The design move is to maintain the reporting level distinctions required for funding, while simultaneously building a governance level common definition that allows cross-line visibility. Most diversified providers don't do this. They report against the funding frameworks and stop there. And their governance inherits the fragmentation. Let me make this concrete. In a well-designed, diversified provider, a participant who enroll through an employment service and later transitions into training is visible as the same person across both systems. Their employment services caseworker sees their training progress. Their trainer sees their employment services history. Their governance dashboard, when it reports participants active, is counting each human being once, not once per service line. The reporting to funders still uses funder specific definitions. The governance uses a higher level, common definition that sits above those and allows crossline reading. The second move is crossline cadence alignment. Training delivery runs on a semester rhythm. Employment services run on a caseworker rhythm. Apprenticeship support runs on a mentor rhythm. Each line has its own natural cadence, and each is doing good work within that cadence. The benchmark providers layer a governance cadence on top, a monthly cross line review, a quarterly portfolio review, an annual integration review. At each point, signals from every service line are brought into a single conversation. Not a stack of individual reports reviewed in sequence, but a single integrated agenda that reads the portfolio as one organism. This is the rhythm that makes diversification governable. Without it, each line operates in its own clock, and the organization never has a moment where the whole portfolio is read at once. The third move is end-to-end evidence discipline. When a participant moves from employment services into training, evidence of that transition exists. When they move from training into workplace assessment, evidence exists. When an outcome is achieved or an exit occurs, evidence exists. And critically, all of that evidence is captured in a way that lets the organization reconstruct the participant's full pathway on demand without retrospective assembly. This is what allows a diversified provider to answer the end-to-end question from the regulator in a time frame the regulator finds credible. The evidence is not assembled from multiple systems after the question arrives. It exists as a participant level trail across the portfolio, formed while the participant was active. Three moves. Common definitions, cross line cadence, end to end evidence discipline. These are what makes Serena Russo and diversified providers like them governable. Not the aggregate performance of the portfolio. The comparability beneath the aggregate. Let me make this concrete with a scenario from the book. A diversified provider reports stable portfolio performance. Governance materials show strong activity across services, improvement in one line, manageable variance in another. The overall position appears balanced. Beneath this, inconsistency is developing. One service line reports participants as progressing based on completed appointments. Another defines progression through milestone attainment. Training delivery records progression through enrollment status and attendance. Employment services records progression through activity engagement. Each measure is internally valid. Each is appropriate

When Definitions Clash Across Service Lines

SPEAKER_00 15:04

within its funding framework. But together they do not describe the same condition. A participant who is progressing in employment services is not necessarily progressing in any sense that training delivery would recognize. And vice versa. When leadership tries to understand participant movement across the end-to-end pathway, which is what continuous assurance effectively requires, the picture fragments. It is not clear where individuals are stalling, where support is insufficient, where delivery conditions are affecting outcomes, where transitions between services are breaking. Resources are then directed based on incomplete interpretation. Attention shifts to the visible constraint rather than the actual one. If the visible constraint is in training delivery, training gets attention. If the underlying constraint is actually in the transition from employment services into training, that remains invisible, because no line owns the transition and no crossline view tracks it. Drift is not only missed, it is redistributed. The organization is busy, it is active, it is producing the reports each framework requires, and it is still, structurally, learning late about its own condition. The turning point in scenarios like this, and I have seen this play out in practice, happens when leadership decides to build a cross-line participant view. Not to replace the line level reporting, to sit alongside it, same data source, different aggregation, a single view of what is actually happening to the humans who are moving through the portfolio. The day that view becomes operational, things that were invisible for months become obvious within minutes, and the organization is no longer learning about itself through external pressure. It is reading itself in real time. Let me say more about what changes when that crossline view goes live. The governance meeting agenda shifts. Instead of spending the first hour reviewing training performance and the second hour reviewing employment services performance and never really integrating them, the meeting starts with the participant view and works outward. What does the crossline data show? Which participants are stalling at which transition points? Where is the organization's support working and where is it breaking? The resource conversation shifts. Instead of each service line fighting for its own budget line, leadership can see where an investment in one line would actually reduce cost or risk in another. An investment in early intervention in employment services might reduce the retention risk in training. An investment in trainer capability might improve the employment outcomes for graduates. These trade-offs only become visible when the crossline view exists. The regulatory conversation shifts. When the regulator asks a crossline question, the answer exists already. Not assembled under time pressure, but pulled from a view that has been operating continuously. This is what continuous assurance looks like in a diversified provider. Not heavier reporting. Smarter aggregation. A governance view that sits above the operating lines without blurring the lines themselves. Now most RTOs listening to this are thinking, Angela, I am not Serena Rousseau. I don't have employment services. I don't have apprenticeship support. I don't run multiple service lines. You may be right and you may be wrong, because most RTOs I work with have more service lines than they think. Let me give you some examples of what counts as a service line for governance purposes. Funded programs versus fee for service delivery. That is two service lines, even if the training product is the same, because the funding frameworks create different reporting requirements, different compliance obligations and different cadences.

Applying Cross-Line Design In Small RTOs

SPEAKER_00 19:43

Workplace based traineeships versus classroom based qualifications. That is two service lines because the evidence environments are fundamentally different. Corporate contracts versus public intake. That is two service lines because the employer relationship, commercial terms, and delivery expectations are different. If you are running two or more of these, you have a diversified operation. Smaller than Serena Russo. Same governance challenge, same three design moves apply. Common definitions, crossline cadence, end to end evidence discipline. Let me give you a concrete example of how this plays out at the smaller scale. Because it is where most RTOs will recognise themselves. An RTO with roughly a hundred active enrolments. Two service streams. The first is a publicly funded workforce program where learners come through a funding body with particular reporting requirements and a defined set of outcomes. The second is fee for service delivery to corporate clients, where the employer directly contracts for training and the outcomes are employer defined. Same trainers. Same assessment resources, same compliance framework. From the outside, one RTO. From a governance perspective, two distinct operating systems. Funded learners have a different intake process, different support entitlements, different progression expectations, and different exit pathways from corporate learners. Attendance means different things. Progress is measured against different frames. Completion triggers different reporting. If that RTO's monthly governance report just shows 72% completion rate across all learners, it is mixing two completely different operating logics and presenting them as one number. Drift could be forming in either stream without any visibility at the aggregate level. The three design moves at this scale might look like a common internal definition of at risk that applies across both streams while the funder specific definitions remain for reporting. A monthly 30-minute cross-stream review before the full leadership meeting. A simple participant level view that shows each learner's movement across both streams where any dual flag applies. None of this requires new technology. It requires design. Three mistakes I see RTOs make when they try to apply this. The first mistake is treating service lines as separate operational silos. The training team handles training. The compliance team handles compliance. The corporate team handles commercial contracts. Each team reports monthly to the CEO. And the CEO has the whole picture. In my experience, the CEO rarely has the whole picture under this model. The CEO has three pictures reviewed in sequence, with no comparability between them. The whole picture only forms when the lines are read together against shared definitions. And that requires an operational move, not just a reporting move. The second mistake is reporting portfolio totals without line level variance. Our completion rate across the organization is 78%. That is an aggregated number. It tells you almost nothing. The useful question is whether the completion rate is 78% in every line, or whether it is 90% in one line and 65% in another, and the variance is being smoothed by the aggregation. Report variance, not totals. Always. The third mistake is assuming aggregation reassurance is governance. A stable portfolio looks like governance. It is not governance, it is a reporting artifact. Governance is the ability to see drift forming in a line while options still exist. That requires visibility beneath the aggregate, and the whole point of good portfolio management from a governance perspective is to preserve that visibility, not to obscure it. This week I want you to do something specific. Pick one metric, any metric your governance actually pays attention to.

Three Common Mistakes And A Challenge

SPEAKER_00 25:40

Pick it, put it on the agenda for your next leadership meeting. Agree on a single cross-line definition. Rebuild the metric against that definition. And watch what it tells you. The Serena Russo chapter sits in the benchmark section of the Governance Shift alongside the public providers and the specialists. Together, those chapters walk through all three pathways to governability that Australian RTOs have successfully taken. Different routes, same destination. The Governance Shift launches in June 2026. It is sold alongside the eight critical drivers to RTO success as the RTO governance bundle. The landing page is governance-shift.com.au Next week, episode forty. We leave Australia for the first time. What Brazil, Britain, and the United States teach us about governance timing. Three different jurisdictions. Three very different VET systems. If you have ever wondered whether the governance patterns I have been describing are Australian specific or structural, that is the episode that answers the question.