Once a week, at the same time, gather the team for about 20 minutes before opening. Look at last week's few numbers, let each area owner speak briefly, and agree on one or two changes with a name against each. Write them down and start the next meeting by checking whether they happened.
Why it matters
Small problems in a running shop repeat quietly. The same dish comes back, the same supplier is late every Thursday, the same customer complaint arrives on Google. Staff often know the cause long before you do but never have a moment to say it. A short regular meeting is that moment, and it keeps problems from piling up until you lose your temper over them.
There's also something concrete to discuss: real numbers from the week. Cash differences, items that ran out, wastage, complaints, reviews. The meeting is where the checklists and area owners come together, and where you hear what's working before you change anything.
How to do it
Keep the format identical every week. The value comes from it being short and predictable, not from long discussion.
Fix a slot and protect it
Choose the quietest time of the week, often 20 minutes before opening on your slowest weekday. Same day, same time, every week. If you're travelling, hold it on a video call or ask an area owner to run it. Pay for the time if it falls outside working hours.
Bring the week's numbers on one sheet
Five or six figures, no more: total sales against the previous week, closing cash differences, items that ran out, wastage if you measure it, complaints and new reviews. Read them out in a minute. You're not grading anyone; you're showing the team the same picture you see.
Go round the area owners
Each owner gets about two minutes: their number, what went wrong, what they did about it. Others can add one point. If something needs a long discussion, note it and take it up later with the two people involved, not the whole group.
Ask one open question
"What slowed you down this week?" or "What did a customer ask for that we couldn't do?" Wait through the silence. The quieter staff, helpers and delivery people, often have the most useful answers. Thank whoever raises a problem, even if it's about you.
Agree one or two changes, with names
Pick the changes that fix the most repeated problem. Each one gets an owner and a date: "Meena will move the gas line up the closing list by Friday." Resist agreeing six things; two that happen beat six that don't.
Write it down and send it
Keep a notebook or a running note, and after the meeting post the decisions in the staff WhatsApp group in three or four lines. Next week, start by reading last week's decisions: done, not done, or dropped.
Rough timing for 20 minutes: last week's decisions, 2 minutes; numbers, 2; area owners, 10; open question, 3; agree changes, 3. Stop on time even if you haven't covered everything; that's what next week is for.
Your result
A fixed weekly slot, a one-sheet set of numbers, and a running record of decisions that actually get checked. Reuse the same notes layout each week.
Date: ____ Present: ________ Last week's decisions: done / not done / dropped Sales vs last week: ₹____ / ₹____ Cash differences: ₹____ Ran out of: ________ Wastage: ____ Complaints / new reviews: ____ Area owners, one line each: Open question asked, main answer: Changes agreed (what, who, by when): 1. 2.
Worked example (made up, to show how it reads)
Date: 10 Nov Present: all 5
Last week: new closing order — done; ask supplier for earlier delivery — not done
Sales: ₹1.42 lakh vs ₹1.36 lakh
Cash differences: ₹120 (Tue, noted) Ran out of: paneer twice
Complaints 1 (cold food), reviews 3 new
Open question: "what slowed you?" — billing phone hangs at lunch
Changes: 1. Owner calls supplier about delivery time by Wed
2. Ravi clears storage on billing phone, ThuFill it in on your checklist, next to this topic. It stays in this browser.
Time and cost
- Time
- 20 minutes a week, plus 10 minutes beforehand to pull the numbers from your billing app or register.
- Cost
- Only the staff time, which should be paid. Some owners add tea and snacks, which helps attendance more than it costs.
Ballparks to verify: prices and fees change by city and over time, so check current rates before you budget.
Common mistakes
Turning it into a scolding session
If every meeting is a list of complaints from the owner, staff stop raising problems. Keep it about what to change, not who to blame.
Letting it run long
A 45-minute meeting before opening makes everyone late and resentful. Stop at 20 and take long topics offline.
Not following up
If last week's decisions are never checked, people learn that agreeing to something means nothing.
Skipping it when things are going well
Good weeks are when you'll hear what's working. Cancelling it now and then quickly becomes never.
Go deeper
- Read nextMake one person responsible for each area →The area owners whose updates form the core of this meeting.
- Read nextMeasure wastage →A useful number to bring to the meeting each week.
- Business playbookWho to hire: restaurant →Kitchen and floor roles in a restaurant, the people who'd sit in this meeting and what each looks after.
The playbooks are written for one business each. Start with the full playbook or find yours.
Questions people ask
Should I hold it if I'm not there?
Yes. Ask an area owner to run it from the same sheet and send you the notes. It's good practice for the day you're away for longer.
What about complaints and bad reviews raised in the meeting?
Agree a fix for the cause, then reply to the customer. How to respond and close the loop is covered in replying to reviews.
Is a WhatsApp group enough instead of a meeting?
It works for passing decisions on, not for finding problems. People say things face to face that they won't type in a group. Use both.