Asana is where a lot of studios land after spreadsheets. Clean interface, sensible task hierarchy and good notifications. For a while, it feels like the studio finally has a system.

Then the seams show. Where do specifications go? Which task holds the finishes schedule? How does a client approve a selection? Where’s the fee for this phase? Asana’s answer to all of these is in a task, or a custom field, or a linked doc, or somewhere else. Because Asana’s world is made of tasks while a design practice is made of projects, phases, rooms, specs, products, clients, drawings, and money that relate to each other in ways a task list can’t express.

What breaks when the unit is “task”

• Specs and FF&E become tasks or attachments. But a material or product isn’t a to-do; it’s a record with a supplier, a price, a room, an approval status, a cut sheet, a lead time — used across schedules and budgets. Task tools flatten it into a checkbox with a link.

• Phases become sections. SD/DD/CD/CA carry fees, deliverables, and billing logic. In a task tool they’re headers.

• Clients become guests. Inviting clients into your task board exposes your internal chatter, or forces you to keep a separate “client-safe” project. Neither is a portal.

• Documents are generated elsewhere. Schedules, transmittals, proposals — the artifacts your practice issues — are not something a task manager produces.

• CA doesn’t fit. RFIs, site instructions, submittal reviews, issue logs need structured records with numbering, status, and history — not tasks with tags.