Asana

Tested Asana over four weeks running an 8-person product squad with two parallel feature initiatives plus a marketing collaboration thread. Baseline was Linear for the engineering side and a Notion database for the marketing collab. The goal was to see whether Asana could replace both with one cross-functional system, especially the Timeline and Goals features plus the new Smart Status AI rollup. Spent roughly six focused hours weekly inside the workspace across sprint planning, review, and ad hoc syncs.

Timeline view with dependency arrows turned out to be the single biggest win - dragging a milestone slid every downstream task automatically and surfaced two conflicts I had been missing in Linear. Custom fields covering effort, blocker reason, and stakeholder owner made cross-team status calls dramatically tighter. Rules automation handled the boring routing well, for instance auto-assigning design tickets to the right designer based on a category field, and Goals tied weekly check-ins back to quarterly OKRs without manual rollup. Smart Status produced a usable summary of the week roughly 70 percent of the time, enough to seed Friday updates.

Mobile experience is genuinely slow on older Android handsets and lacks several desktop features such as portfolio rollups. The pricing wall hits early - timeline view, custom fields beyond three, and Goals all require Business tier at 24.99 USD per user monthly, which adds up fast past ten seats. Search relevancy is surprisingly weak compared to Linear, returning archived tasks above active ones too often. Permissioning around private projects has confusing inherited defaults that almost caused a leak when a contractor was added to a parent portfolio. Smart Status hallucinates blocked-state language when no one has updated a task in two weeks.

Better than Linear for any team mixing engineering with marketing, design, or operations - the cross-functional ergonomics are real. Linear stays sharper for engineering-led product orgs that live in pull requests. Pick Asana when your project portfolio is the system of record and the engineers tolerate a less keyboard-driven UI. Skip if mobile is the primary device.