How to manage projects when your team is three people (including you)

Most project management advice assumes you've got departments, resources, and multiple layers of people to delegate things to. The reality for many small teams is rather different: there are three of you, everyone's already doing several jobs, and the last thing anyone needs is a project manager who insists on daily standups and Gantt charts.

The problem is that tiny teams still need coordination. You can't just wing it and hope for the best—that ends with duplicated work, missed deadlines, and the awkward discovery that you've both been solving the same problem whilst the actual urgent thing sits untouched. What you need is structure that's light enough not to feel like bureaucracy, but solid enough to keep everyone pointing in roughly the same direction.

Stop pretending you're a bigger team

The first step is accepting that you're not a scaled-down version of a proper company. You're something different, and that's fine. Enterprise project management exists to solve problems you don't have: coordinating across departments, managing stakeholder complexity, and ensuring that fifty people aren't accidentally working against each other.

You've got different problems. Your issues are things like: everyone's context-switching constantly, there's no slack in the system when someone's ill, and decisions that would take five minutes face-to-face somehow spawn three-day email threads instead. These need different solutions.

So stop looking for software that promises to solve "resource allocation across multiple teams" and stop reading articles about "aligning your PMO strategy with enterprise objectives." That's not your world, and pretending it is just adds overhead you can't afford.

One shared source of truth (just one)

Pick a single place where work lives. Could be Trello, Notion, Asana, a shared spreadsheet, or even a well-organized Google Doc if that's what everyone will actually use. The tool matters less than the commitment to having one tool.

Three-person teams often end up with tasks scattered across Slack messages, someone's notebook, a spreadsheet that lives on one person's desktop, and half-remembered conversations from Tuesday. This is how things fall through cracks.

Whatever system you pick needs to answer these questions immediately:

• What are we working on right now?

• What's coming up next?

• Who's doing what?

• Are we blocked on anything?

If your system can't answer those four questions within about ten seconds, it's too complicated. Simplify it until it can.

Weekly check-ins, not daily standups

Daily standups make sense when you're coordinating eight or ten people. With three people, they're usually performative nonsense. You already know what everyone's doing because you talked about it yesterday, or saw their commit messages, or answered their question an hour ago.

A weekly check-in is enough. Thirty to forty-five minutes where you review what happened last week, confirm what everyone's tackling this week, and flag anything that needs discussion or decision-making. That's it. You don't need more meetings than that unless something's actively on fire.

The trick is making this meeting actually useful rather than a status report performance. Come prepared with your blockers, your questions, and the decisions that need making. If someone just reads out their task list, you're doing it wrong.

Default to asynchronous communication

When there are only three of you, it's tempting to just tap someone on the shoulder (literally or virtually) whenever you need something. This feels efficient because you get an immediate answer, but it's murder for anyone trying to do focused work.

Most questions don't actually need answering within thirty seconds. They can wait an hour, or two hours, or even until tomorrow. Writing things down in your shared system—with enough context that someone can understand the question when they get to it—lets people work in chunks rather than being constantly interrupted.

Reserve real-time conversations for things that genuinely need back-and-forth discussion or quick decisions. Everything else can be asynchronous. This is especially important if anyone works different hours or has caring responsibilities that mean their availability is patchy.

Be honest about capacity

Small teams have almost no buffer. If someone's off sick, you've just lost a third of your capacity. If someone's dealing with a production emergency, that's half your team unavailable for new work. And yet small teams often plan as if they have the resilience of a much larger group.

When you're planning work, assume people have about 60-70% of their time available for planned project work. The rest goes on interruptions, maintenance, admin, and all the other bits that don't make it onto task lists but nonetheless eat hours.

This feels pessimistic until you track it for a few weeks and realize it's actually quite optimistic. But planning for 60% capacity means you're less likely to promise things you can't deliver, and more likely to actually hit your deadlines.

Rotate the boring work

Someone needs to update the client, write the meeting notes, chase that supplier, or update the task board. In a larger team, you might have someone whose job this is. With three people, it's just extra work on top of everything else.

These tasks are never anyone's favorite, so they tend to drift towards whoever's most conscientious or least willing to just ignore them. This breeds resentment and means your most organized person spends time on admin whilst others get to focus on interesting work.

Rotate it. Not everything—some people are genuinely better at certain tasks—but the general coordination overhead should move around. Everyone takes turns being the person who makes sure the meeting happens and the notes get written. It's fairer, and it means everyone understands what's actually involved in keeping things running.

Write down your decisions

With three people, you'll make a lot of decisions in casual conversation. Someone asks a question in Slack, you discuss it for a few messages, make a call, and move on. Six weeks later, someone new wonders why you're doing it this way, and nobody can quite remember what you decided or why.

Get in the habit of recording decisions somewhere. Doesn't need to be formal—just a shared doc that lists what you decided and roughly why. Date it, add a sentence or two of context, move on. Takes thirty seconds and saves the "wait, why are we doing it this way again?" conversation later.

Be careful with "quickly"

The phrase "can I quickly ask you something" is dangerous in small teams. It's never actually quick. Either the question itself takes longer than expected, or it leads to a discussion, or it derails someone's afternoon because they can't get back into the flow of what they were doing.

Notice when you're about to say "quickly" and ask yourself if it actually needs to happen right now. If it can wait until later, write it down. If it genuinely is urgent, be honest about that—but most things aren't nearly as urgent as they feel in the moment.

Embrace the flexibility

The advantage of being three people is that you can change direction fast. You don't need approval from six layers of management, or a steering committee meeting, or a formal change control process. If something isn't working, you can just... stop doing it.

This applies to your project management too. If your weekly meeting isn't useful, change when it happens or how you run it. If your task board is getting cluttered and nobody's updating it, simplify it. If you realize you're spending more time updating the system than actually working, drop the bits that aren't helping.

The project management advice that works for fifty people definitely won't all work for three. Keep the bits that help you stay coordinated and deliver work. Bin everything else without guilt. You're small enough to be pragmatic about this.