How do I know where work stands across the team without another meeting?
Ask in your own words and get an answer from the records, not from people reciting them. Here is how a team status update works when the work writes it.
6 min read · · The Felesh team
The short answer
You ask. Instead of calling everyone together so each person can recite what they are doing, you put the question to Felesh in your own words and it answers from your own records.
That only works if the work has been written down as it happened. So the real answer has two halves. Say what happened after each piece of work, in one sentence. Then ask when you want to know where things stand.
The meeting was a way of getting that information out of people’s heads. If the information is already in the records, the meeting has less to do.
Why does a status meeting exist at all?
Most status meetings answer the same few questions. What is open with this customer? Who promised what, and by when? What is stuck?
The answers live in different places. One person has them in a notebook. Another has a half-remembered promise from a phone call. Someone else has a thread of messages that never got summarised. So you sit down together and rebuild the picture out loud.
A template helps a little. It asks everyone to fill in the same boxes. But a written update is still a second piece of work, done after the real work, and it is only as good as the memory of whoever writes it. By the time you read it, it has already aged.
What if the status came from the work itself?
Then nobody has to write it up. Each person says what happened, once, when it happens.
After a call or a visit, they type one sentence, and Felesh drafts the note for a yes.
That one sentence is the whole of the update. It is written while the detail is fresh, in the words of the person who did the work. Nobody has to prepare for a meeting, because the record was made at the time.
What does a week look like?
Take an ordinary week in a small business with a few people on the work.
- A customer rings about a job that has run over. The person who took the call types a sentence about what was said and what they agreed to do.
- Felesh drafts the note, the promise with its date, and the next step. The person reads each draft, sees the reason beside it, and says yes.
- A colleague adds a task for the same customer directly, so it is there straight away.
- Messages from the website chat or Instagram arrive in the one inbox. Felesh answers what it can from the documents and instructions you gave it. What it cannot answer goes to “Needs you”, with the reason. Nobody is notified, so someone has to look.
- On Friday you want to know where things stand. You ask: “What have we promised customers that is still open?” or “What is waiting on the company we spoke to on Tuesday?”
The answer comes from the notes, promises and tasks that were put in during the week. You are reading what was recorded, not a recollection of it.
Getting the Friday summary without asking
You can build a routine once, for example “every Friday, list open promises and what has gone quiet and tell me.” It runs on the schedule you set, and the summary reaches people invited into your workspace as a notice in the panel, not by email or SMS and never to customers. It exists only because you set it up; without that routine, nothing arrives on its own.
What does it not know?
Be clear about the limits, because an answer is only as complete as the record behind it.
Felesh knows what is done on Felesh. It knows the contacts and companies you bring in from an Excel or CSV file, through an import where you see the column mapping and the rows before anything is saved. It knows what you upload or teach it.
It does not read your mail. It does not read your drives. It does not connect to other tools. If a promise was made in a conversation nobody described to it, it will not be there.
That sounds like a weakness, but it is the same discipline a good meeting needs. A status picture is only as good as what people say. The difference is that here the saying takes one typed sentence, at the moment it matters, not a round of updates in a room.
How do I keep it about the work and not about the people?
This matters more than it seems. A status update can easily turn into a way of checking up on individuals, and people notice quickly. They start to perform for the update instead of doing the job.
The better question is always about the work. Ask which customers are waiting. Ask which promises are due. Ask which job has gone quiet. A quiet customer or a quiet deal is something you can act on. A quiet person is not a finding. It could mean they were out on a job, or on a long call, or simply that the work did not need a note.
So frame your questions around customers, jobs and promises. Felesh answers from the work, and the work is what you wanted to see in the first place. If you want to know how someone is getting on, that is a conversation, and it belongs to you and them.
Does it hold up when you review the year?
A year-end review is a good test, because it asks for the long view. What did we promise this year, and what became of it? Which customers did we lose touch with? Where did work pile up?
If the year has been recorded one sentence at a time, you can ask those questions in your own words and get answers from the records. You are not trying to reconstruct twelve months from memory and a few spreadsheets.
The records will still have gaps, and you should expect that. But the gaps will be small and honest ones, where nobody said what happened, rather than the large blur of a year nobody wrote down.
Where to start
Pick one customer with open work and have everyone who touches it say what happens, in one sentence, for a week. Then ask Felesh where it stands, and see how much of the meeting you still need. You can read more about how to ask your work in your own words.