How a piece of work actually moves
Three modules can hold a to-do. Picking the wrong one is how teams end up maintaining the same list in two places.
Lodos gives you three places to put something you have to do: a card on a Kanban board, a line in a Checklist, or a block on the Calendar. That looks like redundancy. It is not — they answer three different questions — but nobody explains which is which, so most teams end up duplicating.
Which one holds what
Task Management is for work that has a state. A card sits in a column, moves right as it progresses, and is visible to everyone. If someone other than you needs to know whether it is done, it belongs here.
Checklist is for steps inside one piece of work. Items nest, so a card called "Launch the landing page" can have a checklist with eleven items under it, each with a priority and an owner. Nobody wants eleven cards on a board for one launch.
Calendar is for work that has to happen at a specific hour. Not "this week" — Thursday at 14:00. If it does not need an hour, it does not belong on the calendar, and putting it there is how people end up with a calendar they stop reading.
The test that settles most arguments: Does someone else need to see its status? Board. Is it a step inside something bigger? Checklist. Would it be wrong to do it at another time? Calendar.
Getting the board shape right
Boards fail for one of two reasons, and both are about columns.
Too many columns is the common one. A board with nine columns looks thorough and behaves like a filing system nobody updates, because moving a card becomes a decision. Four columns is enough for almost every team: something not started, something in progress, something waiting on someone else, something done.
That third column matters more than it looks. Without an explicit "blocked" or "waiting" column, work that is stuck sits in "in progress" and looks identical to work that is moving. You lose the single most useful signal a board can give you.
The other failure is a board per person. It feels organised for a week and then nobody can see the whole picture, which was the entire reason for having a board. Use one board per project and filter by assignee when you need your own view — the multi-filter search does this in two clicks.
From a column to an hour
Task Management has calendar and timeline views built in, and this is where the modules stop being separate. A card with a deadline appears on the timeline. Drag it and the deadline changes; the card does not care which view you edited it from.
The habit worth building is a weekly pass rather than a daily one:
- Open the board, filter to your own cards.
- Switch to calendar view. Anything without a date is invisible here — that absence is the point, it shows you what you have committed to versus what you have merely accepted.
- Drag the three or four things that genuinely have to happen this week onto specific days.
- Leave the rest undated. A card without a date is not neglected; it is honestly labelled as not scheduled.
Most people resist step four because an undated card feels like a loose end. It is the opposite: dating everything produces a calendar that lies, and a calendar that lies gets ignored within a fortnight.
Where the conversation about a task goes
Cards have comments. Use them, even when it would be faster to send a message — especially when it would be faster.
A decision made in a comment stays attached to the thing it was about. The same decision made in a chat channel is gone in a day, and six weeks later somebody asks why the design changed and nobody can find the answer. Chat is for coordinating; the card is for the record.
The practical rule: if a message contains the word "because", it belongs on the card.
What "done" should mean
Agree on this once and the board maintains itself. Leave it vague and you get cards that sit in the last column for a month while people argue about whether they are finished.
A useful definition of done is one somebody else can verify without asking you. "Deployed to production" is verifiable. "Finished" is not. If your last column is full of cards nobody is sure about, the definition is the problem, not the team.
Archive rather than delete. Archived cards leave the board but keep their comments, their checklist and their history, and a quarter later that history is the only record of why something was built the way it was.
Questions people actually ask
Should each person have their own board?
No. Use one board per project and filter by assignee for a personal view. Per-person boards feel tidy for a week and then destroy the one thing a board is for — seeing the whole picture.
What is the right number of columns?
Four for most teams: not started, in progress, blocked, done. The blocked column is the one people skip and the one that carries the most information — without it, stuck work looks exactly like moving work.
Should I put every task on the calendar?
No. The calendar is for work that must happen at a specific hour. Dating everything produces a calendar nobody trusts, and an untrusted calendar stops being read within a couple of weeks.
What happens to a card when I archive it?
It leaves the board but keeps its comments, checklist and history, and stays searchable. Archive rather than delete — a quarter later that history is often the only record of why a decision was made.
