Leading a small Australian team without the MBA language

Most people who lead a small Australian team did not apply for a leadership career. Someone went on leave, someone quit, or the owner finally admitted they cannot be on every job. You get a higher-duties allowance, a set of keys, and a week to work out who actually knows the regulars. The leadership and management habit that matters is not charisma. It is making Thursday predictable.

This guide is for that person — a Dandenong warehouse acting supervisor, a Fremantle cafe owner, a Townsville leading hand. It is the old vocational work of leading work teams, written so you can use it before smoko.

What the job actually is

A small-team leader has four recurring jobs. Everything else is decoration.

1. Decide what happens this week, in language a casual on their third shift can follow.
2. Put the right people on the right work, including the unglamorous jobs nobody volunteers for.
3. Notice when someone is slipping, overloaded or unsafe, and say so early.
4. Carry the conversation with customers, suppliers and the person who signs the invoices.

If you only do the first two, you are a dispatcher. If you only do the last two, you are a counsellor with a radio. The craft is holding all four. The old Certificate IV language on team purpose and roles is still the spine. On a six-person team you are also covering lunch and filling in when the only person who can run the saw is at an appointment.

Stop translating yourself into corporate

People who have sat through a leadership offsite come back speaking a dialect their crew does not use. They say "cascade the priorities" when they mean "school job first, it has a lock-in time". They say "hold people accountable" when they mean "I will check the load at 2 pm".

Australian crews smell that translation. They do not need you to be mates. They need you to mean the same thing at 6.30 am that you meant on Monday. Use the words the work already has: the pour, the pickup window, the 10 o'clock list. If a phrase would look silly on a crib-room whiteboard, do not put it in an email.

The first fortnight, not the first 90 days

Consulting decks love a 90-day plan. Most acting supervisors get a fortnight before the next roster cycle. Use it like this.

Days 1 to 3: map the real system

Walk the work. Write down who people actually ring, not the org chart. Note the jobs that only one person can do. Ask the longest-serving casual what breaks every summer. If you are in a workplace with plant, vehicles or chemicals, start at the work health and safety duties, not the sales board. A leader who cannot name the live risks is not leading.

Days 4 to 7: make one week hold

Pick a single week and make it boring in a good way. Confirm start times. Name a deputy for the two hours you are off site. Write the customer promises that already exist — "same-day if it is in by 11" — so you stop inventing new ones under pressure. If you need a document, keep it to one page. The longer version can wait until you write an operational plan staff will actually use.

Days 8 to 14: have the two conversations you have been avoiding

One will be about a standard that has slipped. One will be about a person who is carrying too much. Both are cheaper now than after the next incident. If you are unsure how to keep the relationship intact, read performance conversations that do not destroy trust before you book the room.

How small work teams actually run

A work team is not a family. It is people who share a result and a roster. The old unit on team effectiveness asked you to set purpose, agree ways of working, and support the job. That is still the right sequence. The mistake is doing it as a workshop.

Purpose is a sentence: "Morning run out by 7.30, nobody skips the pre-start." Ways of working are the five things that cause fights: phones, swaps, smoko, who stays back, who talks to the angry customer. Write those five.

Support is practical: show the awkward lift, swap a close after a bereavement, and stop treating the only bilingual staff member as an unpaid interpreter.

Meetings that earn their time

A six-person team does not need a weekly leadership huddle. It needs a standing ten minutes: what is due, who is missing, what could hurt someone. Stand up. Write decisions on the board. Park last month's argument. A performance conversation is a private talk, not a meeting item.

Owner-operators skip the meeting because they are already in every conversation. That is how the Saturday casual hears a different story from the Tuesday regular.

When you still do the work

The hardest part of leading a small Australian team is that you are still on the tools. You plate up, you pick orders, you run the excavator between phone calls. The risk is not laziness. The risk is disappearing into the work you are good at because leading feels slower.

Protect two blocks in the week that are not production. One is for the roster, the orders and the plan. One is for people: check-ins, the awkward chat, the new starter. If both blocks get eaten, you are a very expensive pair of hands.

This is also where emotional intelligence at work stops being a poster. You will be tired. You will take a short tone from a customer and hand it to the closest staff member. Notice that move. Apologise specifically. Do not give a speech about culture.

Safety is not a fourth priority

Small teams skip the conversation that prevents the injury because it feels like admin. Under the model WHS laws, and Victoria's OHS Act, the person conducting the business still has to eliminate or minimise risk so far as is reasonably practicable. Five people does not shrink that duty.

Keep the live hazards in the weekly conversation: the wet dock, the aggressive regular, the lone close, the fatigue after a double. Consultation can be a toolbox talk. It cannot be a nod at a poster.

If you are unsure whether a risk is yours to own, say so and contact the editorial desk. We will not be your PCBU. We will help you find the right question.

Worked example: Friday in a Fremantle cafe

Priya owns a 42-seat cafe with six staff, two of them casual students. Friday is the week. She used to write a long group chat on Thursday night. People skimmed it. The Saturday opener still arrived unsure whether the function was set for 11 or 12.

Now she uses a one-page Friday plan on the pass:

• Open: Dan and Mei. Function set by 10.30, not during the 8 am rush.
• Lunch: Priya on pass, Sam on floor. Refunds under $50 without asking.
• Risk: wet tiles near the dishwasher after the function. Mats down before service.
• Close: Mei and the new casual. Priya on the phone until 8. No one walks to cars alone.
• Parking-lot issue: Dan has been late twice. Priya talks to him Saturday at 2, not in the group chat.

The team can see the week. The risk is named. The late-start talk has a private time. The customer promise is a number.

If she later needs another cook, she will start with the actual shifts, the same way you should when recruiting and retaining frontline staff. If functions stretch the floor, she will treat it as customer service run from operations, not as branding.

What good looks like after a month

The roster is out before people ask. A casual can follow one written plan. One standard has been held without a public shaming. Someone else can open or close without ringing you for the alarm code. That is the ordinary competence the old leadership units were pointing at. Keep the language plain. Leave the slogans on the flyer you did not print.