How this differs from the general Trello guide, stated up front
The general Trello guide teaches the mechanic: boards, lists, cards, and one personal worked example. This guide assumes the mechanic and teaches running a team project on it, which is a different discipline: intake control, limits on parallel work, a blocked protocol, and reporting. If a card's journey through your board involves other people's handoffs, deadlines you report on, and work that can stall, you are in the right article.
| Your situation | Your honest starting point | What this guide gives you |
|---|
| Team of 3 to 15, one project at a time | Full build | The complete project system below |
| Team juggling several projects | One board per project plus the portfolio habit | The cross-board reporting section |
| Solo, but client-facing delivery | Intake, blocked handling, closing review | Client visibility without client chaos |
| Your current board is a shared junk drawer | Rebuild with the list design in step 2 | Stage discipline and a WIP limit |
| You need Gantt charts and dependencies | Read the views section, then decide | What Premium gives, and what it still does not |
Plans, priced when we checked Trello's pricing page on November 18, 2026: free covers small boards with caps on collaborators and boards per Workspace; Standard ($5 per user per month billed annually) adds custom fields and more automation; Premium ($10) adds the views this guide uses (Timeline, Calendar, Dashboard) and unlimited boards. The system below works on free for a pilot project; Premium is what a team running several projects will feel.
Step 1: One board per project, named like a project
Create a board per project, in a team Workspace. Not one mega-board with a list per project: projects end, and boards archive whole, which is the cleanest record a team can keep. Name it with the deliverable and the date: "Website Launch, March". The board background and description carry the project brief in one paragraph: what ships, by when, and what is out of scope. Link the full brief document on a pinned first card; Trello holds the flow, the document holds the depth.
Step 2: The list design, stages only
Project boards use stage lists, one meaning, left to right: Intake, Planned, In progress, Blocked, In review, Done. Two of these deserve comment. Intake is a controlled door, not a suggestion box; the next section gives it rules. Blocked is a list, not a label, because a list can be counted at a glance in a standup and a label cannot. Resist adding a stage for your project's special case until the second project asks for it too; every extra stage is a place cards hide.
Step 3: Intake discipline, where project boards live or die
Anyone can add a card to Intake, with a rule: the card must say what done looks like in its description, in one or two sentences, before it can be promoted. The project lead (or the team in planning) promotes cards from Intake to Planned, splits the ones that are really three cards, and rejects or parks the rest with a comment saying why. This ten-minute gate is the difference between a board that represents a plan and a board that represents everyone's passing thoughts. Butler helps: a rule that adds a checklist ("Definition of ready: outcome written, owner named, estimate set") to every new Intake card makes the standard self-enforcing.
Step 4: Card anatomy for a team
A project card carries more than a personal card. Owner: exactly one member, the person who answers for it. Due date: the committed date, with a reminder two days before. Checklist: the handoff steps, especially the last one, which is usually "review requested". Custom field or label for size: a rough estimate (S, M, L) so planning can count load, not just cards. Attachments and links: the working documents, on the card. Comments: decisions and blockers, written on the card, not in chat, so the card remains the record. A card a new team member can open cold and understand is the standard; anything less is a rumor with a title.
Step 5: Work-in-progress limits, the practice that finishes projects
Set a limit per stage, written in the list title: "In progress (max 5)". When the list is full, nobody pulls new work; the team's job becomes finishing or unblocking. This feels slower and is measurably faster, because cards stop aging in parallel. Blocked gets a daily look: every card in Blocked has a comment naming the blocker, the person who can clear it, and the date it was raised. Butler can stamp blocked cards automatically when they are moved to the list (add a red label, post a comment prompt, set a date), and can escalate by mentioning the project lead after two days untouched. The base guide covers Butler basics; here it runs the protocol.
The worked project: a website launch, intake to review
A six-person team, six weeks. The board opens with 31 cards in Intake from a kickoff brain dump; planning promotes 19, splits 4 into 9, parks 8 with comments. Planned holds the 28-card scope. In progress never exceeds 5; twice, the limit forces a design review to finish before new build cards start, which is the limit working as designed. Blocked peaks at 3 cards (legal copy, image licenses, one staging access), each with a named clearer; none ages past three days because standup reads the Blocked list first. In review is where the project lead earns their keep: cards do not cross to Done on the author's word. Launch day, 26 cards sit in Done, 2 were descoped mid-project with comments recording why. The closing review, next section, takes forty minutes because the board already contains the whole story.
Step 6: Views and reporting on Premium
Premium's views turn one board into several reports. Timeline shows dated cards as bars: the Gantt-like picture stakeholders ask for, honest about overlaps and gaps. Calendar shows due dates monthly, the view for spotting the week everything lands at once. Dashboard counts cards per list, per member, and per due state: the standup and the status email in one screen. For several projects, a Workspace-level table or a saved advanced search gives the portfolio glance, and the discipline is a weekly fifteen-minute pass across boards, reading Blocked lists and overdue counts only. Reporting in Trello is counting done well; if your stakeholders need earned value or dependency chains, that is the honest edge where a dedicated project tool wins, and Trello vs monday.com grades that trade.
Step 7: Time, with Planner and due dates
Dates on cards become a schedule when the team uses Trello Planner, the built-in panel that shows due cards beside a Google Calendar and lets you drag cards into focus-time slots. The project use is personal load management inside the team system: each member blocks their own week from their own cards. Our Planner guide teaches that workflow in full. Project leads should know it exists because a card due Friday that nobody scheduled time for is a hope, not a plan.
Step 8: The closing review, and archiving the board
When the project ships: hold the review while memory is fresh. Walk the board left to right. What did Intake reject that it should have caught earlier? Where did cards block, and was the cause a person, a dependency, or a decision? Which estimates were fiction? Write the answers on a Retro card, copy the three changes you will actually make into the next project's board template, then archive the board. Archived boards are the team's institutional memory, searchable forever. A team that skips the review pays tuition for the same lessons every project. For document-heavy projects where the brief and decisions outweigh the flow, the Notion project management guide builds the other shape, and many teams run both.
Related guides
Frequently asked questions
How is project management in Trello different from personal use?
Control points. A project board adds an intake gate with a definition of ready, work-in-progress limits per stage, a Blocked list with a named clearer per card, and a closing review. The mechanic is identical; the discipline around it is the entire difference, and it is what lets a board survive contact with a real team and a real deadline.
One board per project, or one board for all projects?
One per project, in one team Workspace. Projects end and archive cleanly, lists stay stage-shaped, and reporting per project stays readable. The portfolio view across projects comes from Workspace tools and a weekly pass, not from a mega-board whose lists must serve five projects at once and end up serving none.
Which plan does a project team actually need?
Pilot on free. Move to Standard when you need custom fields for estimates and more Butler automation. Move to Premium when you need Timeline, Calendar, and Dashboard views for reporting, which for most teams is the moment a second concurrent project starts. Premium lists at $10 per user per month billed annually when we checked on November 18, 2026.
How do we handle dependencies between cards?
Lightly, and honestly. Link dependent cards in their descriptions and checklists, name the dependency in standup, and let the Blocked list surface stalls. Trello does not enforce dependencies or auto-shift dates; Timeline shows the collision but will not prevent it. Teams whose projects are dependency chains should use a dedicated project tool for that layer.
What should the closing review produce?
Three concrete changes, written down, applied to the next board. Not a feelings document: intake criteria tightened, an estimate habit fixed, a review step added. Copy them into the board template the team duplicates for each new project, archive the finished board, and the review has done its job.
Can clients see the project board?
Yes, as guests or members on that board only, and many teams keep a separate client-facing board with milestone cards, synced manually at the weekly pass, rather than exposing the working board with its blocked cards and internal comments. Decide deliberately: transparency is a feature, but an unfiltered work board reads as chaos to anyone outside the team.
Photo credits: Mikhail Nilov (Pexels). Photos are served from this site; follow the credit to the library page for the original.