Asana's Head of Engineering emphasizes creating alignment through three types of clarity: purpose (why), plan (how), and responsibility (who/what). The company uses OKRs methodology with both bottom-up and top-down approaches, ensuring goals connect to daily execution rather than existing as isolated planning documents. Key
Table of contents
Q: How does the Asana engineering team approach goal setting and how has that approach changed since going remote?Q: What are some of the roadblocks that teams run into when implementing OKRs or other types of goal setting frameworks?Q: What’s your advice for setting team goals when you’ve only been given vague direction or overly ambitious aspirations?Q: What advice do you have for senior leaders looking to set non-product goals in areas like mentorship, process, or quality?Q: Should goals always be quantifiable?Q: How do you set goals for high performers?Q: How much should dev teams be involved in goal setting?Q: What’s Asana’s framework for prioritizing team and company goals?Q: How do you balance exciting engineering goals with business imperative engineering goals?Q: Any tips for setting diversity and inclusion goals on an engineering team?Uplevel your goal setting process todaySort: