7 common project management mistakes (we've all made them)

These are the 7 most common project management errors we see in small teams — agencies, studios, family businesses, ops teams. If you recognize yourself in three or more, that's not embarrassing: that's a diagnosis. Each one comes with a simple fix.

Mistake 1: running the whole project from the group chat

The scene: the client approved the new deadline… in a WhatsApp message, nine days ago, buried between a Monday meme and three 4-minute voice notes. Today nobody can find it, two people swear the date was different, and someone asks "wait, was that confirmed or just a proposal?". Chat is great for talking — and terrible as a project's memory.

The fix: chat for conversation, something else for commitments. Every important decision becomes a task with an owner and a due date, somewhere searchable. With Doku you just type it — or say it out loud — the way you'd say it in the chat: "Andrea owns the new logo, due Friday", and it lands as a task with an owner and a reminder, not as message number 1,847.

Mistake 2: the spreadsheet only one person understands

There is ONE file. It has tabs named "FINAL_v3_for_real", orange cells that mean something only one person knows, and a formula nobody has dared to touch since 2023. When that person goes on vacation, so does the project. And when anyone else edits it, something breaks and nobody knows what.

The fix: project status has to be readable without a translator. A shared board where anyone on the team can see what's pending, in progress, and done — no permission requests, no color-code decoder. If your project lives in a spreadsheet today, migrating hurts less than you think: describe it to Doku and the AI builds the board for you.

Mistake 3: tasks with no owner

In the meeting someone says "we should update the proposal" and everyone nods. Nobody writes anything down. Next week: "so… the proposal?" — silence — "oh, I thought you had it". It gets noted again, the cycle repeats. A task that belongs to everyone belongs, mathematically, to no one.

The fix is almost offensively simple: one person per task, by name. Others can help, but the owner is the one who answers for the date. Golden rule: if a task leaves the meeting without an owner, the task doesn't exist.

Mistake 4: decorative deadlines (or none at all)

Two flavors here. The first: tasks due "whenever we get to it", which is the official euphemism for "never". The second, more sophisticated: dates everyone knows won't be met, that nobody moves once they pass, and that stop meaning anything by week three. The timeline becomes wall art.

The fix: realistic dates — set by asking the person doing the work, not by wishful thinking — plus a system that remembers them for you. In Doku, every dated task generates automatic reminders, and the AI follows up on whatever is coming due or slipping, so a deadline goes back to being a commitment instead of a suggestion.

Mistake 5: status meetings that don't track any status

45 minutes, six people, and the first 30 go to reconstructing what happened: everyone reports from memory, two people discuss different versions of the same to-do, and the new agreements… nobody writes down (see mistake 3). The status meeting becomes the reason you need another status meeting.

The fix: status gets read before the meeting, not during it. If the board is up to date, the meeting drops to 15 minutes and gets spent deciding, not reporting. Doku's daily email digest helps with exactly that: everyone walks in knowing what moved and what's stuck, so the meeting starts at the useful part.

Mistake 6: the project lives in one person's head

Every small team has that person who "has it all under control": they know what's missing, who owes what, and what was promised to the client. It's admirable — until they get sick, travel, or quit, and the team discovers the project was never documented. It was memorized. It's called the bus factor, and in small businesses it's risk number one.

The fix: whatever is in your head doesn't count as a plan. Get it onto a shared board — tasks, dates, agreements, context — even imperfectly. The fastest way: tell Doku about the project out loud, as if you were briefing a new teammate, and let the AI structure it. Ten minutes of dictation beat a month of "don't worry, I have it written down somewhere".

Mistake 7: over-correcting with an enterprise tool

After the chaos comes the epiphany: "we need a professional tool!". Someone installs the platform Google uses, sets up sprints, epics, story points, and a 14-required-fields form just to create a task. Three weeks later the tool looks immaculate… because nobody touches it. The team has quietly moved back to the group chat.

The fix: the best tool isn't the most complete one — it's the one your team actually uses on a random Tuesday without being chased. For a non-technical team that means creating a task in one sentence, seeing the project as a list, kanban, or Gantt without a certification course, and letting AI handle the follow-up. That's exactly the gap Doku was built for: you describe it, Doku builds it.

Self-check: how many are you making today?

Answer honestly. Every "no" is one of the 7 mistakes waving at you:

• Can you find the project's last important decision in under a minute (without scrolling a chat)?
• Does anyone besides you understand the file or board where the project lives?
• Does every open task have exactly one named owner?
• Do your deadlines get met — or at least renegotiated before they blow past?
• Do your status meetings run under 20 minutes and end with written agreements?
• If your key person disappeared for two weeks, would the project keep moving?
• Does your team use your current tool without being begged to?

Frequently asked questions