Best practices for task naming - start with a problem, how to link to the solution?

[lpb]

@anon68308835,

Yes, you need a task to represent each project to enable you to do a number of interesting things with multi-project reporting, but that doesn’t mean you need to relegate all other work to subtasks; that decision should be made on its own merits. Simply use an extra task to represent the project as a whole.

See also:

OKR Tracking in Asana

I spent time a few months ago designing a quite powerful and very flexible solution for my clients to handle either OKRs or Goals/KPIs (and initiatives generally), that is quick to implement and maintain weekly or monthly, and works company-wide with roll-ups at the company- and department-levels. An optional third tier, sub-department-level, is optionally available too. Unlike both Goals and Portfolios, which both require the Business tier, this solution only requires Premium, and still includ…

Larry