Minimal project management: the fewest fields and rituals that work
Minimal project management for 1 to 5 people is one list of work with five fields (task, owner, due date, status, client), three statuses and two short meetings a week. Drop priorities, estimates, sprints and Gantt charts until a specific problem demands them. It stops being enough when work waits on other people's dates or clients ask to see progress.
As of November 2026. Tool limits link to each vendor's pricing page, opened on 8 November 2026. Written by Flori, not an independent review.
What should a minimal system actually answer?
Three questions, every Monday: what is due, who has it, and what is stuck. Apply one test to anything else you are tempted to track: would this field change a decision this week? If it would not, leave it out. Every extra field is a thing somebody must fill in for every task, forever.
What are the fewest fields that work?
| Field | Rule | Failure it prevents |
|---|---|---|
| Task | Starts with a verb and a thing: "Send homepage copy to client" | "Homepage" sitting on the list for three weeks |
| Owner | One name, never "team" | Everybody assuming somebody else has it |
| Due date | A date someone will actually notice passing | A list with no order |
| Status | To do, Waiting or Done | Long discussions about what "in review" means |
| Client | Who pays for this | Losing a small client's work behind a big one |
Three statuses is deliberate. "In progress" adds little at this size, because a task that is due this week and is unfinished is in progress. "Waiting" earns its place because client work stalls on other people: write who you are waiting on in the task name ("Waiting: logo files from Dana").
Which rituals do small teams need?
- Monday, 15 minutes. Sort by due date. Every task gets one owner. Anything with no date gets a date or gets deleted. Say out loud what is Waiting and who will chase it.
- Friday, 10 minutes. Mark things Done. Send each active client three lines: done, next, what we need from you. Our weekly client update is a starting point.
That is the full calendar. Message each other during the week about anything urgent, and put anything that needs a date on the list.
What should you drop, and when does each thing come back?
| Drop | Why it costs more than it returns | Bring it back when |
|---|---|---|
| Priority levels | Due dates already rank the work | Many tasks share a due date and people keep asking which goes first |
| Time estimates | Few people revisit them | Fixed-fee jobs have overrun twice in a row |
| Time tracking | Daily admin for a number nobody uses | You bill by the hour or need margin per client |
| Gantt charts | They need redrawing with each change | Three or more people depend on each other's dates |
| Sprints and points | Built for product teams with a backlog | You ship software on a cycle |
| Tags | They multiply and go stale | You run the same filter every week |
| Daily standup | You already know, at five people or fewer | People keep discovering blockers late |
| Role charts | Everybody knows who does what | A client has several approvers; use a RACI chart |
What does a one-page setup look like?
This is an illustrative example: a fictional three-person web studio with two clients, in a single shared sheet or board.
| Task | Owner | Due | Status | Client |
|---|---|---|---|---|
| Send homepage copy to client | Maya | Tue 10 Nov | To do | Harbor Dental |
| Waiting: logo files from Dana | Sam | Wed 11 Nov | Waiting | Harbor Dental |
| Build booking page layout | Sam | Fri 13 Nov | To do | Harbor Dental |
| Write October SEO report | Maya | Mon 9 Nov | To do | Fern Coffee |
| Fix mobile menu bug | Lee | Mon 9 Nov | Done | Fern Coffee |
| Ask Fern to approve autumn landing page | Maya | Thu 12 Nov | To do | Fern Coffee |
| Chase Harbor deposit invoice | Lee | Thu 12 Nov | To do | Harbor Dental |
Above the table, write three house rules: one owner per task, no task without a date, and delete anything that has moved three times. Keep briefs and contracts in a folder and paste the link into the task name when someone needs it. Use a second tab for finished work so the live list stays short.
When does minimal project management stop being enough?
These are rules of thumb, so adjust them to your work.
- Dependencies bite. One person's delay moved someone else's deadline more than once this month. You need task dependencies.
- The list stops fitting. Past about 40 open tasks, or a sixth person, a single list gets slow to review. You need boards or views per person.
- Clients keep asking where things stand. More than one "any update?" a week per client means they need something to look at.
- The same customer lives in two places. Sales notes in one tool and delivery in another means somebody re-types the brief at every handover.
- Assistants are doing some of the work. An AI that plans or updates tasks needs a record it can read and write, plus a way for you to review its changes.
What is the best project management for small teams?
The one your team will still be updating in March. For most teams of one to five, that is one of these:
| Option | Starting point | Better than Flori when |
|---|---|---|
| Shared sheet | The one-page setup above, or a sheet template for clients | You have under ten active tasks and want zero new logins |
| Trello | Free for up to 10 collaborators per Workspace, up to 10 boards | You want cards on a board and nothing else to learn |
| Todoist | Free with 5 personal projects; Business is $8 per user a month billed yearly | The work is mostly one person's task list |
| Basecamp | One free project with up to 3 people; Freelancer is $29 a month for 3 projects and 5 users | You want messages, files and to-dos together at a flat price |
| Flori | Free: unlimited people, 3 active projects, 200 customer records | Clients and projects need one record, and your own AI works in it |
Flori is the wrong pick if you only need a to-do list, or if you need e-signatures or to send invoices, neither of which it does.
Do you need a CRM as well as a project tool?
If your deals turn into projects, one tool that holds both saves the handover: the CRM with project management page explains how that works in Flori. If sales are occasional and projects are long, keep a simple client sheet beside Trello or Basecamp and link the two by client name. Avoid buying a full CRM and a full project suite at five people, because each will sit half empty.
FAQ
What is minimal project management? It is the smallest set of fields and meetings that still tells a team what is due, who owns it and what is stuck. For one to five people that usually means a shared list with five columns and two short weekly check-ins. Anything else gets added only after a real problem shows it is needed.
Is a spreadsheet enough for project management? For a team of one to five with a handful of clients, yes. A spreadsheet handles five columns and a filter by client. It falls short when clients need their own view, when tasks depend on each other, or when you want reminders without someone remembering to open the file.
What is the minimum a project plan should include? A goal in one sentence, the deliverables, what is out of scope, a list of dated milestones, and one named approver on the client side. Those five items settle most later arguments. A longer plan is worth writing only when the work is fixed price and large enough that a misunderstanding would cost real money.
How many statuses does a small team need? Three: To do, Waiting and Done. Add a fourth only when a real stage has a different person responsible, such as a client review step that always sits with the same account lead. More statuses than that mostly generate debate about where a card belongs while nobody moves it.
Do freelancers need project management software? Usually not at first. A solo freelancer with up to three clients can run on a task app or sheet. Software starts paying for itself when clients want to see progress, when a contractor joins, or when client details and project notes have spread across email, chat and several files.
Start your workspace