Projects, Sections, and Task Organization
Structure before scale
Projects are the primary organizing unit. Each project has a layout (list, board, calendar, timeline), a set of members, and sections that order the work. Sections can be reordered and tasks moved between them; on a board, each section is a column. Understand that a project can be public to the workspace, private to members, or shared with specific people, and that this visibility affects who can find and join it.
Organizing tasks well
Know the hierarchy: project → task → subtask, with approvals and milestones as task types. Milestones mark key dates and behave like tasks that can be completed; approvals add an approve/reject decision. Use task dependencies to express blocking relationships, and understand that a dependent task cannot be marked complete until its blockers are complete (unless overridden).
Traps in questions
Questions often test the consequence of deleting versus completing a task, or of moving a task between sections versus between projects. Deleting removes it from all projects; completing keeps history. Moving a task to another project can strip fields that don't exist there. Another frequent trap is confusing sections with columns in a board view - they are the same thing, but a list view shows them as headers, not columns.
Worked example
A marketing team tracks campaigns. One project holds all campaigns as tasks; sections are Brief, In Production, Review, Launched. Each campaign's individual assets are subtasks. Milestones flag launch dates. This keeps a single source of truth and lets the board view show pipeline stage at a glance.