Who it is for, and how long it takes
| Who it is for | How long | What you need | What you end with |
|---|
| Managers who run a weekly team review, and the people in it. | One Monday morning: a personal read before the meeting, then the meeting itself. | One shared list of open work with owners and dates. With GeniOS, that list is the intelligence each owner already gets. | Every open item with one owner and a date, one gap written down, and a meeting that ends in decisions. |
Key takeaways
- Start from what needs a decision. Look at charts only if a question is left.
- Every owner clears their own items before the meeting starts.
- End with one gap written into a shared doc, so next Monday starts sharper.
A dashboard shows what happened. It leaves the noticing, deciding and assigning to whoever is in the room. This morning flips the order, so the meeting spends its time on decisions. You can run it from a shared list of open work, and GeniOS makes that list arrive ready each Monday.
Worked example. The examples use Vaultex, a safety-footwear manufacturer in Greater Noida and GeniOS's first design partner. The buyers, orders and dates are for illustration only.
PrepBefore you start
Set these up the week before your first no-dashboard Monday.
- One shared list of open work where every item has one owner and a date. With GeniOS, this is the intelligence each owner already receives.
- A fixed meeting time and length, such as 45 minutes at 10:00, with the same people each week.
- A 30-minute read slot in each owner's calendar before the meeting.
- A shared doc for gaps that GeniOS reads, so each week's gap carries forward.
- Agreement on what Later means: a reason and a new date, said out loud.
- Optional: a Reply Drafter and a Scheduler, with one agent chosen first and approval rules written down.
- The dashboards you usually open, bookmarked for the end of the meeting.
StepsThe steps
One morning · 7 steps
- Open the list before anything else
Read the open items since Friday, before email and before chat. With GeniOS, that is the intelligence sent since Friday. Leave the dashboards closed for the morning.
- Clear what you own first
Each item has one owner. Answer yours with Delegate, Done, Later or Not relevant before you look at anyone else's. A Later needs a reason you could say out loud in the meeting.
- Delegate the drafting
Hand follow-ups to a Reply Drafter and meetings to a Scheduler. Review each draft, edit it if needed, and approve it. Nothing goes out without that approval.
- Run the meeting from the open list
Go owner by owner. Harsh covers the Bata quote before Friday's 11:00 vendor review, Anushka covers Line 2 and the Reebok samples due 15 November, and Mayank covers the 60-day terms. Each owner says what they will do and by when, or moves it to Later with a reason.
- Check last week's closes
Look at what closed on proof since last Monday. Anything someone called done that has not closed is worth a two-minute question. Often the email went to the wrong thread, or a meeting was agreed and never booked.
- Write down one gap
Pick one thing the list missed this week, such as the IS 15298 test reports the Adidas audit will ask for next month. Add it to a doc GeniOS reads, so next Monday starts with it.
- Open the dashboards last, if at all
If a number still worries you after the list, open the chart. It now answers a specific question. Whatever it shows goes back onto the list with an owner and a date.
TemplateCopy this Monday agenda
Paste this into the meeting invite and keep the times.
Monday review: [team], 45 minutes
Before the meeting: clear your own items with Delegate, Done, Later or Not relevant.
10:00, last week's closes (5 min). What closed on proof. Anything called done without proof gets one question.
10:05, owner by owner (25 min). About five minutes each: the open items, what you will do and by when. Later needs a reason and a date.
10:30, decisions needed (10 min). Anything that needs someone other than its owner to decide, with a name and a date.
10:40, one gap (5 min). One thing the list missed this week, written into the shared doc.
After 10:45, optional: dashboards, only for a question that is still open.
ExampleWorked example: a Monday at Vaultex
How the morning might run for Harsh, Mayank and Anushka.
08:30. Before opening email, Harsh reads the intelligence sent since Friday. He marks a supplier newsletter Not relevant, delegates the follow-up on the steel toe-cap supplier's 8% price rise to a Reply Drafter, and approves the draft after adding the open Bata quantity.
09:15. Mayank clears his items. Bata's request for 60-day payment terms stays open, with a decision set for Thursday. Anushka moves one quality-test booking to Later, with a reason: the test lab confirms its slots on Tuesday.
10:00. The meeting opens with last week's closes. One item called done, a sample shipment confirmation, has no email behind it. The note went to the wrong thread, and Anushka resends it.
10:05. Owner by owner. Harsh: the Bata quote for 12,000 pairs, about $144,000, is sent, and Friday's 11:00 vendor review is booked. Anushka: Line 2 runs the Reebok samples due 15 November, and the Bata run is split across both lines. Mayank: the terms decision on Thursday.
10:40. The gap of the week is the IS 15298 test reports the Adidas audit will ask for next month. It goes into the shared doc with an owner. Nobody opens a dashboard, and the meeting ends early.
MistakesCommon mistakes
Five ways the meeting drifts back to charts.
- Opening the dashboards first. The meeting then spends its time explaining charts. Leave them for the end.
- Owners arriving with uncleared items. The meeting becomes a reading session. Protect the read slot.
- Accepting "we will look into it". That has no owner and no date. Ask for both before moving on.
- Skipping last week's closes. Done without proof is where work quietly slips. Spend the five minutes.
- Writing down three gaps. Nobody fixes three. Pick one a week.
What good looks like after
- The meeting is shorter, and it ends with decisions instead of "let us look into it".
- Every open item has one owner and one date, said out loud in the room.
- Done means proof, and the list of done-but-not-closed items shrinks from one week to the next.
- Each Monday adds one gap to the shared context, so the list gets more complete.
- Over a few months, you can see how much routine work agents close and how often a person still steps in.
If the meeting still drifts to charts, move the dashboards to a separate, optional slot after it ends.
How to know it worked
Check these after each Monday for the first month. The idea behind the routine is the gap between knowing and doing, and AI for managers covers the wider habit. The same list feeds the monthly investor update, and team commitment management shows it across a whole team.
| What to measure | How to check it | A good sign |
|---|
| Meeting length | Check the calendar | Ends on time or early |
| Items leaving with an owner and a date | Count from the open list after the meeting | All of them |
| Items called done without proof | Count at the closes check | Falls week to week |
| "We will look into it" outcomes | Count them in the notes | Close to none |
| Gaps added to the shared doc | Count the lines in the doc | One a week |