Use Trello for project management by giving each board one workflow, each list one state in that workflow, and each card one deliverable with one owner and one due date. Then let Butler automation move cards between states so people don’t have to. That structure holds up; decorative boards do not.
Design the board around a flow, not around people or clients
The most common failure in a Trello rollout is one board per client, or one board per team member. It looks tidy in week one and falls apart by week six, because any work that crosses two clients has no home, and nobody can answer “what is in flight right now” without opening eleven boards.
Build boards around a repeatable delivery flow instead. One board per flow — content production, client onboarding, release pipeline, bug triage — with lists that represent states of that flow. Clients, owners and priorities then become labels, Custom Fields and card members, all of which are filterable. Board membership is not filterable, so anything you encode as a separate board becomes invisible from everywhere else.
A board that works looks roughly like this: Backlog, Ready, In progress, Blocked, Review, Done. Six lists. The Blocked list matters more than it appears: without it, stalled work sits in In progress and quietly inflates your sense of throughput.
Two conventions keep the structure honest. Lists are states, never categories — the moment a list called “Marketing” appears next to a list called “Review”, the board stops meaning anything. And a card only moves right, or sideways into Blocked; it never occupies two states at once.
Set up a board that survives contact with real work
- Open your Workspace, select Create, then Create board. Name it after the flow, not the project.
- Add your state lists in order, left to right. Stop at six or seven — beyond that, horizontal scrolling costs more than the extra granularity buys.
- Open the board menu, select Labels, and define labels for one dimension only. Work type or priority, not both, and never status.
- On Standard or higher, enable the Custom Fields Power-Up and add fields for the attributes you will report on later — client, estimate, stage. Fields are sortable in Table view; label soup is not.
- Create one card, write a description template into it, then open the card’s … menu and convert it into a template card. Every new piece of work now starts from a consistent shape.
- Open the board menu, select Automation, and build your rules before inviting anyone. Retrofitting automation onto a board people already use badly is far harder than starting with it.
What actually belongs on a card
A card is a unit of deliverable work, not a topic. If the title is a noun with no verb — “Website”, “Q3 campaign” — it is a project, and it belongs on a board or as a checklist parent. If finishing it requires three different people to each do their part, it is three cards.
Assign exactly one member as the owner, even though Trello permits several. Shared ownership on a card reads as ownership by nobody, and it destroys any filter you later build to answer “what is Priya carrying this week”. Use checklists for the steps inside a single deliverable, and advanced checklists on Standard and above when individual steps need their own due dates and assignees. Keep the source material on the card — attachments, links, decisions in comments — because a card that points at a chat thread is a card that goes stale the moment someone leaves.
Butler automation: build three rules before you build twelve
Butler is built into every board on every plan, including Free. The usual mistake is to automate notifications first, which produces noise people learn to ignore. Automate state transitions and board hygiene first; notifications last, and sparingly.
- Open the board menu and select Automation.
- Select Rules, then Create Rule.
- Choose a trigger from the Triggers tab. Card moves, due date changes, checklist completion and label changes cover the great majority of real needs.
- Add one or more actions from the Actions tab, selecting the + beside each to attach it to the rule.
- Select Save, then test on a throwaway card before letting the rule touch live work.
Three rules earn their place on day one: mark the card complete and clear the due date when it lands in Done; move a card to Blocked and post a comment when a specific label is applied; and a scheduled weekly rule that archives everything in Done so the list does not become an archaeological dig.
For sequenced work, Atlassian’s own guidance uses linked cards plus rules such as when checklist "Pre-requisites" is completed, add the yellow "Ready" label to the card. That works, but it is a convention you maintain, not behaviour the product enforces. When rules silently stop firing, the cause is almost always a quota ceiling, a renamed list, or a rule owned by someone who has left the Workspace — our walkthrough on diagnosing Butler automations that stop running covers the checks in order.
Automation quotas are the limit you will actually hit
Runs and operations are not the same thing. One rule firing counts as one automation run; each action inside it consumes at least one operation. A rule that sets a label, sets a due date and posts a comment burns three operations every time it fires. Quotas are pooled across the entire Workspace and reset on the first day of each month at midnight GMT.
| Automation quota | Free | Standard | Premium | Enterprise |
|---|---|---|---|---|
| Runs per month | 250 | 1,000 | Unlimited | Unlimited |
| Operations per month | 2,500 | 20,000 | 150,000 plus 10,000 per user, capped at 250,000 | 150,000 plus 10,000 per user, capped at 250,000 |
| Emails per month | 250 | 1,000 | 1,000 per paid user, capped at 100,000 | 1,000 per paid user, capped at 100,000 |
| Pooling | Across Workspace | Across Workspace | Across Workspace | Across all Enterprise members |
Several structural limits bite in practice, all set out in Atlassian’s automation quotas and limits documentation: a single automation run performs at most 20 actions and operations on every plan; no more than 20 card buttons and 20 board buttons can be enabled at once; the send email action is capped at 50 recipients and consumes quota per email sent rather than per action; and every automation one user creates shares a single 64,000-character storage budget, roughly 750 average rules.
Power-Ups: three is a working number
Every plan now includes unlimited Power-Ups per board, which sounds generous and is mostly a trap. Each one adds weight to board load times and another integration to re-authorise when tokens expire, and some partner Power-Ups carry their own separate subscription fee on top of your Trello plan.
A disciplined board runs three: one reporting or calendar surface, one file-storage connector pointing at wherever documents actually live, and one connector to the system that holds the source of truth for the work. Anything beyond that should be justified by a named person who will notice when it breaks. Our assessment of which Trello Power-Ups are worth enabling goes through the shortlist by job to be done.
Views, and what Premium is really buying
Board view is available everywhere. Table, Calendar, Timeline, Dashboard and Map views are Premium and Enterprise features, and Atlassian’s Timeline view documentation states there are no current plans to make Timeline available to free Workspaces. Timeline also runs on web and desktop only; it is no longer accessible on mobile, which matters if your delivery leads plan from phones.
Timeline is the view that changes how a project is managed rather than merely displayed, but it requires start and end dates on cards, not just due dates. Set those deliberately or the view is empty. Grouping by list, member or label turns the same data into a schedule, a workload sketch, or a workstream map.
| Plan | Price per user/month, billed annually | Core limits | What it adds |
|---|---|---|---|
| Free | $0 | Up to 10 boards and 10 collaborators per Workspace; 10MB per file | Unlimited cards, unlimited Power-Ups, 250 Workspace command runs per month |
| Standard | $5 ($6 billed monthly) | Unlimited boards; 250MB per file | Custom Fields, advanced checklists, card mirroring, list colours, saved searches, 1,000 command runs |
| Premium | $10 ($12.50 billed monthly) | Positioned for teams up to 100 | Calendar, Timeline, Table, Dashboard and Map views; Workspace Table and Calendar views; unlimited command runs; Observers; Collections; simple data export |
| Enterprise | $17.50 ($210 per user per year) | Unlimited Workspaces | Organisation-wide permissions, public board management, Power-Up administration, multi-board guests, attachment permissions, SSO and user provisioning via Atlassian Guard |
Current figures are on the official Trello pricing page. Note that Atlassian Guard, which provides the SSO and enforced 2FA that Enterprise buyers usually assume is bundled, is a separate subscription starting at $4 per user per month. If you are weighing Standard against Premium specifically, our full Trello review works through which tier justifies itself at which team size.
Where Trello is the wrong tool
Trello has no built-in task dependency management. That is Atlassian’s own wording in its task dependency documentation, which recommends representing prerequisites with checklists, linked cards and automation rules. The workaround is serviceable for a handful of sequenced tasks and unworkable for a schedule where one slipped date must cascade through fifty downstream items. If you are managing a critical path with contractual dates attached, use a tool with genuine predecessor logic.
Resourcing is the second gap. There is no capacity model, no native time tracking, and no view that tells you a person is already committed to sixty hours next week. Teams patch this with an estimate Custom Field and a third-party time-tracking Power-Up, which produces numbers without producing constraint — nothing stops the eleventh card landing on an already-full person.
Reporting depth is the third. Dashboard view is board-scoped and counts cards; it does not handle budget, earned value, or programme-level rollup. Workspace Table and Calendar views on Premium do let you look across boards, but they are filtered card lists rather than a portfolio layer, and they will not satisfy a PMO that expects variance reporting.
Cost deserves an honest look too. A 25-person team on Premium is $3,000 a year at list price, which is competitive — but it buys views and automation headroom, not the scheduling and resourcing engine that a heavier tool includes at a similar price. And if your work is really structured records with typed fields, relationships between tables and calculations across them, a relational tool will do less damage to your data model; our Airtable and Trello comparison maps where that boundary sits.
Common questions
How many lists should a Trello board have?
Six or seven is the practical ceiling. Past that, lists scroll off screen and people stop maintaining the ones they cannot see. If you genuinely need more states than that, the work almost certainly spans two distinct flows and belongs on two boards, connected by linked or mirrored cards.
Is the free Trello plan enough for a small team?
For up to ten collaborators running fewer than ten boards per Workspace, generally yes. The binding constraint is automation: 250 runs and 2,500 operations per month, pooled across the whole Workspace, disappears quickly once a few rules fire on every card move. Views are the other gap — Free gets board view only.
Does Trello support task dependencies?
Not natively. Atlassian’s documentation states directly that Trello has no built-in task dependency management, and recommends modelling prerequisites through checklists, linked cards and automation rules instead. That holds up for short sequences. For schedules where a slipped date must cascade automatically through downstream tasks, choose a tool with real predecessor logic.
What happens when a Workspace exceeds its automation quota?
Rules stop running until the quota resets on the first of the month at midnight GMT. Because quotas are pooled, one badly written rule on one board can exhaust the allowance for everybody. Check consumption by opening the board menu, selecting Automation, then Activity, then the Workspace activity tab.
Should a project manager use Trello or a database tool?
Trello suits work that moves through states and reads naturally as a queue. If your work is fundamentally records with typed fields, relationships between them, and calculations spanning those relationships, a relational tool fits better. In practice the two are complementary more often than competitive: Trello for flow, a database for the underlying records.
Sponsored
