Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
Create a Trello board by choosing its Workspace and visibility before adding lists or cards. Creating a useful board starts with its Workspace and visibility, then a small workflow that reflects the team's real decisions rather than decorative columns.
Create a Trello board in the right Workspace
Select Create, Create Board and enter the title and Workspace. Trello boards must belong to a Workspace. Current guidance says new boards default to Workspace visible, so inspect the setting before adding client information; Private is a separate choice with its own administrative access context.

Add a small set of meaningful lists
Use Add another list to create the stages the project needs. List names should communicate what qualifies a card to enter and leave. A simple To do, Doing and Done arrangement can work if completion has a clear definition, but avoid treating every column as a new department.
Test the workflow with a sample card
Create a harmless sample and move it through the lists. Check the card's owner, due date and completion expectations. Review who can see and act on the board, because an attractive layout does not guarantee the right membership or a reliable project process.
A practical checklist
- Choose the intended Workspace.
- Inspect visibility before adding private details.
- Use meaningful lists with entry criteria.
- Test one sample card through the workflow.
- Review board members and responsibilities.
Worked example
Illustrative example: a freelancer creates a client delivery board with Draft, Review and Approved lists. A sample card demonstrates that moving to Approved requires the client's recorded decision. The board is not made public merely because the workflow is easy to understand.

A practical client-delivery board
Use this illustrative setup for a small client project. Start with synthetic card titles until you have checked the board’s audience and the client has approved the information to be shared.
- Draft: work is in progress; the card names an owner and the deliverable.
- Review: a draft is ready for the agreed reviewer; include the version and a decision deadline.
- Approved: the reviewer has explicitly approved that version; record the decision in a comment or link to the agreed record.
- Blocked: optional; describe the dependency and who can unblock it. If the board is small, a label may be enough instead of another list.
Before using the board, move a sample card through the stages. Ask whether a new collaborator could tell who owns the next action and what constitutes approval. If a card can reach Approved without a decision, revise the rule before using it for client work.
Visibility: choose an audience, not a label
Private, Workspace and Public are different audiences. Atlassian says private boards are visible to board members and, in paid Workspaces, Workspace admins; Workspace-visible boards are visible to Workspace members, with editing affected by board settings. A public board can be seen by anyone on the internet. Check the current plan, members and settings before adding sensitive material; verify the intended view with an authorized collaborator using a test card.
Further reading: Atlassian: board visibility; Atlassian: create a board.
Common questions
Is a list a separate board? No. Can a board exist outside a Workspace in the current workflow? No. Does a Done column prove client approval? Not unless the agreed completion rule and evidence are present.
What to do next
Keep the first board small and inspect permissions before inviting collaborators. Adjust lists when the work requires it, rather than adding complexity in anticipation of hypothetical projects.
Sources and further reading
Related reading
- Project Management Scheduling: Dependencies Before Dates
- Selling Technical Documentation as a Professional Service
