Building Stronger SRC Teams Through Better Communication and Shared Leadership

Why SRC communication matters

A student representative council works best when every member feels heard and trusted. Without clear communication, even the most motivated team can stall. Decisions get delayed, responsibilities blur, and small disagreements grow into bigger problems. Shared leadership is not about giving everyone the same title. It is about distributing influence so that each person contributes from their strengths while still moving toward common goals. For an SRC serving a university community, this balance is essential. Students expect their representatives to act cohesively, and a fragmented council loses credibility fast.

Step one: Set communication ground rules early

The first weeks after elections set the tone for the whole term. Call a meeting dedicated only to how the team will communicate. Decide on a primary channel for urgent messages, a secondary one for updates, and a clear expectation for response times. If a member knows they cannot reply within two hours during a certain period, they should say so upfront. What to watch for: people who stay silent in these early conversations. They may later disengage or feel sidelined. Invite them directly to share their preference. Also watch for a tendency to rely on one platform for everything. Group chats become chaotic when used for both casual chat and formal decisions. Separate the two or use threads and folders if the platform allows.

Step two: Rotate meeting roles

Many SRCs fall into a pattern where the chair or president dominates every meeting. Shared leadership breaks this habit by rotating roles such as facilitator, timekeeper, note-taker, and agenda-setter. Each role rotates every meeting or every two meetings. This gives every member practice in guiding a discussion and holding others accountable. What to watch for: members who resist taking the facilitator role because they feel shy or unprepared. Pair them with a more experienced member for the first rotation. Also notice if someone uses their turn as facilitator to push their own agenda rather than keep the group on track. Address this gently by reminding the team that the facilitator serves the group, not their own priorities.

Step three: Build trust with structured check-ins

Trust does not grow from a single retreat. It grows from repeated, honest exchanges. Start each meeting with a five-minute check-in where each person says one thing about their week and one thing they need from the team this week. This is not small talk. It surfaces hidden pressures. A member struggling with academics may need less committee work for a while. Another may feel left out of a sub-project. What to watch for: check-ins that become rote or insincere. If members repeat the same safe answer every week, ask a different question. For example, "What is one thing you have learned from a teammate this month?" Rotate the question each meeting to keep the practice fresh.

Step four: Make decisions together, not by majority alone

Shared leadership means decisions are owned by the group, not imposed by a few. Use a clear decision-making framework. For low-stakes choices, a quick show of hands works. For important ones, use consensus-seeking: discuss until everyone can at least live with the outcome. A formal vote should be the last resort, not the first. What to watch for: the loudest voices dominating every decision. Quiet members may agree just to move on. Create moments where each person shares their view before any vote is taken. Use a round-robin format. Also watch for "false consensus" where members say yes in the meeting but complain afterwards. If that happens, revisit the decision openly at the next meeting without blaming anyone.

Step five: Clarify roles and responsibilities in writing

Ambiguity is the enemy of shared leadership. When everyone assumes someone else will handle a task, it does not get done. Write down each role's responsibilities, decision rights, and key contacts. Share this document with the whole council and update it whenever a project shifts. What to watch for: members who accumulate too many tasks because they are reliable. This leads to burnout and resentment. Redistribute tasks regularly. Also watch for roles that overlap confusingly, like a communications officer and a social media coordinator. Define the boundary clearly or merge the roles.

Step six: Plan a structured retreat with clear outcomes

A retreat is a powerful tool if it has a purpose beyond fun. Before booking a venue, agree on what the team wants to achieve. Common goals include setting annual priorities, resolving a specific tension, or practising a new decision-making process. Build the agenda around these goals, not around activities. Leave room for informal time, but keep the main sessions focused. What to watch for: a retreat that becomes all play or all work. Balance is key. Also watch for members who skip the retreat because they see it as optional. Treat it as a core team event. If someone cannot attend, schedule a follow-up session so they are not left out. For ideas on retreat structure and facilitation, resources like teambo.co.za offer practical frameworks that many student councils have found useful when planning their own sessions.

Step seven: Address conflict early and directly

Conflict is natural in any team. Shared leadership does not mean avoiding disagreement. It means handling it constructively. The moment you notice tension, raise it in a private conversation. Use "I" statements: "I noticed you seemed frustrated in the meeting when we discussed the budget." Then ask for their perspective. The goal is understanding, not winning. What to watch for: conflicts that go underground and reappear as gossip or passive resistance. Stop this by naming the behaviour, not the person. For example, say "There has been some confusion about who follows up with vendors. Let's talk about it openly" instead of pointing fingers. Also watch for members who try to mediate every conflict themselves. That is not shared leadership. Teach the whole team basic conflict resolution skills so anyone can step in.

Step eight: Celebrate contributions publicly and specifically

Recognition fuels motivation. When someone does something well, say it in front of the team. Be specific: "Thanks to Thandi for reorganising the filing system, which saved everyone time this week" rather than a vague "good job everyone." This reinforces the behaviours you want to see. What to watch for: recognition that only flows from the top. Encourage members to recognise each other. Create a simple ritual, like a five-minute shout-out at the end of each meeting. Also watch for favouritism. If the same two people always get praised, others may feel invisible. Actively look for contributions from quieter members and highlight them.

Step nine: Review and adjust regularly

Shared leadership is not a one-time setup. It needs maintenance. Schedule a brief review every month. Ask three questions: What is working well in how we communicate? What is not working? What will we change next month? Keep the tone constructive. The goal is continuous improvement, not blame. What to watch for: reviews that become gripe sessions. Steer the conversation toward solutions. Also watch for members who say nothing during reviews but later complain. Encourage anonymous written feedback if some people hesitate to speak up. Use that feedback to adjust how the team operates. Over time, these small adjustments build a resilient, high-trust council.

Final thoughts

Strong communication and shared leadership do not happen by accident. They require intentional effort from every member. The steps above give a practical path, but the real work lies in consistent practice. Start with one or two changes, see how the team responds, and build from there. The same principles that make an SRC effective also make the team more enjoyable to be part of. And that is a goal worth pursuing for any student leadership group.