Project management for people who hate project management tools
I struggled with this for years. I have used ClickUp, Trello, Asana, monday.com and Notion boards, and the pattern was always the same: building the system felt like progress, and the work still slipped. What finally works for me is the opposite of a new tool. One plain list, the channels I already check, and AI doing the remembering.
Why the tools never stuck
The tool was never the problem. Where it lived was.
| What happened | Why |
|---|---|
| I built the system instead of the work | Designing boards feels productive. It is not the thing. |
| The board went stale in a week | Real updates happen in chat and calls, not in the tool |
| Nobody fed it but me | A tool that needs feeding becomes one more job |
| I still missed things | Nothing reminded me in a place I actually look |
The rule I wrote for myself. "Before I optimize the system, I must execute the thing the system is supposed to help me do." Redesigning Notion does not count. Tidying the inbox does not count. Making the perfect task system does not count.
Keep one list, and nothing else
Every open task lives in exactly one place, one line each.
- Pick one home: a plain note (mine is
TASK HQ.md) or a simple app like Todoist. Not a board. - One line per task: a verb, the thing, and a deadline only if there really is one.
- Mark repeating work as recurring once, so you never type it again.
- Add a source link when a task came from a message or call, so you can find the context in one click.
- [ ] Reply to the team on the launch status - Source: Slack thread "Launch" - Deadline: 2026-10-20 - [ ] Check ad accounts have money - Recurs every weekday
Capture where you already are
Tasks get into the list without you opening it.
- Talk, do not type. I dictate brain dumps with Wispr Flow straight into an Inbox note. Messy is fine.
- Let calls write their own actions. A meeting note taker such as Granola gives you the transcript; the AI pulls out the actions with owners.
- Forward, do not retype. When a chat message is a task, paste or forward it to the inbox as it is.
- Let the AI triage. Real tasks go into the list, reference material gets filed, the rest is deleted.
Prompt · triage my inbox
Here is everything I captured since yesterday: voice notes, call actions and forwarded messages. Turn it into tasks for my list. - One line each: verb + thing. Add a deadline only if one was said. - Keep a source link for anything from a call or a message. - Merge duplicates with tasks already on my list. - Anything that is not a task: tell me where it should be filed. Show me the new lines before adding them.
Let AI be your project manager
Every morning, a short brief tells you what matters and what is slipping.
This is the part a tool never did for me: noticing. The AI reads the list, yesterday's notes and recent calls, then tells me in a few lines what to do and what I am about to drop.
Prompt · morning brief
Read my task list, yesterday's daily note and any call notes from the last two days. Then give me, in under ten lines: 1. Today's three: the tasks that matter most, and why 2. Dragging: anything overdue or open for more than a week 3. Untouched: anything I have not looked at in a while 4. Waiting on others: who, what, since when 5. One thing I could delete or hand off Do not mark anything done. Only I mark tasks done.
Keep your hands on the wheel. The AI suggests and reminds; you decide and close. A task is done only when you say it is.
Use the channels that already work
Reminders arrive where you already look, so nothing depends on opening a tool.
I check Slack all day. I do not check project boards. So the brief and the nudges come to Slack, and the work stays where the conversation is.
| Channel | Use it for |
|---|---|
| A Slack message to yourself | The morning brief and anything due today |
| Your phone | Task app notifications for hard deadlines only |
| Your calendar | A block for the one deep-work task of the day |
| A weekly summary you can forward to your manager |
- Start manual: run the morning brief yourself and paste it into Slack for a week.
- Then schedule it: a scheduled AI task, or a small n8n, Zapier or Make flow, posts it to your Slack at the same time every morning.
- One channel per job. If everything pings you everywhere, nothing does.
Make waiting visible
The tasks that slip most are the ones waiting on someone else.
Most of my dropped balls were never mine to finish. They were waiting on a decision, a signature or an answer. So once a day I send the person who owns those decisions one short list.
Prompt · what I need from you
From my task list and recent messages, list only the things that need [name]'s decision, signature or knowledge. For each: one line on what is needed, why it matters, a time estimate for them (2 min, 10 min, 30 min), and the deadline. Number them. Shortest first. Keep it under eight items. Draft it as a Slack message from me. I will send it.
Close loops once a week
Twenty minutes that keeps the list honest.
- Delete what no longer matters. A shorter list is a better list.
- Give every vague task one concrete next action.
- Move anything waiting on someone else to the step 5 list.
- Leave the rest open. Not everything needs resolving this week.
Open loops are okay. "This is unclear. I'm going to choose a reasonable next action and allow reality to give me more information." That is not giving up. It is action without complete certainty.
Write messages that move work
Most project management is a clear message with an owner on every action.
- Context first, in one or two lines.
- Number the actions, and give each one an owner.
- Label every link so people know what they are clicking.
- Close warmly, and say what happens next.
TITLE IN CAPS: what this is about Context: [one or two lines on why this matters now] 1. [Action] (owner: @name, by Fri) 2. [Action] (owner: @name) 2.1. [Sub-step] Links: [Spec] · [Tracker] Let me know if you have questions, happy to jump on a call.
What to skip
Do not over-engineer it. Add structure only when something actually slips.
| Skip | Do instead |
|---|---|
| Boards, sprints, swimlanes | One list |
| Tags, priorities, custom fields | A deadline, only when real |
| Status columns | Done or not done |
| A new tool for the team | The chat channel everyone already uses |
| Automating on day one | A week by hand, then automate what repeated |
| Rebuilding the system when it slips | Do the next task, then fix one thing |
Go one step further
The same idea, applied to everything you know: give the AI notes to read first and write back to.