Back

GuidesCase studyTeam

Staying organized when you manage a team

Flots team4 min read

Managing means spending your day inside other people's subjects. You come out of a meeting and straight into a check-in, you unblock someone in between, and at six o'clock you notice that none of your own work has moved.

Here is a structure that makes that kind of day workable.

Tracking your team's progress through milestones

The temptation when you manage is to want every task of every person in view. It is exhausting for you, and heavy for them.

Track states instead: what has to be reached, and by when. A project with its milestones in place tells you the essentials at a glance: the next milestone and its date, shown as "Overdue:" once it has passed, without you having to read forty lines.

Tracking a team project's dated milestones in Flots, with the milestones reached ticked off and the progress bar

The difference is political too. Asking "where are we on Wednesday's milestone" is not the same conversation as "what did you do yesterday".

The mechanism is described in project milestones: how to choose the right ones.

One note per person

This is the habit that transforms one-on-ones, and it costs two minutes a week.

Open a note for each team member, and feed it whenever something comes up: a point to raise, a win worth mentioning, a difficulty you noticed, a request you did not answer on the spot.

Without that note, the meeting covers the last seven days, because that is all anyone remembers. With it, the meeting covers the quarter.

Keep those notes in a personal project, not in the team project: notes in a shared project are open to all its members, and a difficulty you noticed in someone is not for their colleagues to read. Pin them at the top of that project so you can reopen them without hunting, as explained in pinning: keeping the essentials in view.

Separate what you do from what you follow

The costliest confusion fits in a single list where your own tasks sit mixed with the ones you are waiting on from others.

NatureWhat it calls for
What you doA task with a date and a slot
What you expect from someoneA follow-up point, not a task of yours
What you have to decideA task, and often the most urgent one

The third row is the one people forget. A pending decision often blocks several people at once, and it does not look like work. It does not look like anything, until the day you notice that three pieces of work have stopped moving.

Treat your pending decisions as priority tasks.

Protect your own time

A manager's calendar fills itself, with other people's requests. If you put nothing in it, nothing will be left.

Place your deep work slots before the week fills up, and treat them like appointments. That is the principle behind time blocking, and it counts double when your calendar is visible to the whole team.

Making those slots visible helps as well: your colleagues stop proposing meetings on top of them. If you set them up as scheduled tasks, the outgoing .ics feed from Flots shows them in the calendar your team checks. It is described in seeing your Flots tasks in another calendar.

One check-in for every piece of work

One meeting that sweeps across every piece of work beats one meeting per subject: it surfaces the trade-offs between them, which stay invisible when you follow each one separately.

The run-through fits in three questions per piece of work. What moved? What is blocked? What is waiting on a decision from me?

The third one concerns you directly, and that is often where the real bottleneck sits. The full method is in running several projects at once.

Write it instead of repeating it

A good part of what a manager repeats could be written once. Procedures, decision criteria, what a deliverable is expected to contain.

A shared note inside the project, one the team can read and add to live, replaces three spoken explanations per person. How it works is detailed in writing on a Flots note together, live.


For people outside the team who still take part, see collaborators: who works on this project. And for a small organization, Flots for a founder and a small team.

Who does what, where it is blocked, and what is left for you.

Team tracking with project milestones and one-on-one notes in Flots

Frequently asked questions.

How do you track your team's work without micromanaging?

By tracking milestones rather than tasks. Checking whether a project milestone was reached on its due date tells you as much as a detailed list, without giving anyone the feeling of being watched on every single action.

How do you prepare a one-on-one?

Keep one note per person and feed it week by week. Points to raise get added the moment they come up, which saves you from the improvised meeting where all anyone remembers is the past week.

How do you keep time for your own work?

By placing your slots before the calendar fills up. A manager who blocks nothing ends up with a week made entirely of other people's requests, and their own deep work slides into the weekend.

Do you need a dedicated project management tool?

Not necessarily for a small team. What matters is knowing who does what and where each piece of work stands. A heavy platform becomes a job of its own to maintain, and that job is usually yours.

Your question isn't here?

A message or a video demo: someone from the team replies within 24 hours.

Where do you want to start?

One account, everywhere, in sync. 2 months free, no credit card.