I have read all the Asana content about the Goals feature and searched the forum, but haven’t yet seen concrete examples of how to cascade from company-level Goals down to discrete Projects in a way that feels seamless. Does anyone have good examples of this working well?
Things seem to break at the Goal to Project connection. I really like the drop down view that shows sub-Goals nested under Goals on one page, but that doesn’t seem to exist for Projects (though it’s partially there, since you can connect projects directly to goals, but you have to drill into the goal to see the projects).
As a hypothetical example, let’s say I had a Company Goal related to various people initiatives, and a sub-Goal for the Recruiting team to hire all P0 role this quarter. I could create a Project for each open role that I connect to that sub-Goal. Or should that be a Portfolio of Projects? Should the roles each be a sub-Goal with a connected Project (which feels duplicative)? That is where things start to get murky.
Other tangible examples of this working would help a lot!
It’s true that there may be multiple, viable ways to set things up; that’s ok. Pick the one that fits best according to the suggestions below and to best integrate with other existing goals and work you already have.
Goals (your org’s mission and your org- and team-wide goals and their measures) and work (portfolios, projects, tasks) are two different things. Goals are the intent/purpose, and work are the concrete steps to get there. That should provide an overall distinction.
Why do you feel you know a closer tie between goals and projects than what’s offered? I don’t commonly find myself having to make this navigation; I’m either creating/tracking my goals, or doing the work, not intensively navigating between the two.
Re your people initiatives/hiring example, your goals and sub-goals seem reasonable to me, but you could simplify by having only top-level goals and for each, having one or more sub-goals that are your measures (e.g., OKRs or KPIs). I usually have each “leaf” (sub-goal in this case, but could be a sub-sub-goal in a two-level goal example) be the measure. Re your portfolio and project alternatives, any could work. To decide, focus less on the goals relationship and more on how you carry out the work. Is a small group charged with carrying out the main hiring steps and doing so all at once for multiple positions? They’d want that in a single project, likely. Are these discrete efforts and very involved, maybe a project for each and track work across them more easily in a portfolio. In either case, you’ll be able to see monthly/quarterly/etc. how you’re progressing on the goals regardless.
Please consider my quick-read on goals when Asana first released it here:
And if you haven’t already studied it, I recommend this eBook for the mission/goals part of the equation: