Asana co-founder Justin Rosenstein wrote an article in the latest issue of Wavelength in which he discusses Roadmap Week at Asana. I feel inspired to share some of his thoughts with you and also ask how you all manage Roadmap weeks - or the equivalent depending on your processes or industry - in Asana.
Key workflow-y quotes from Justin’s article include:
Ultimately, organizations exist to accomplish goals. Succeeding at those goals comes down to being clear about exactly what you’re trying to accomplish (“clarity of purpose”) and how you’re going to get there (“clarity of plan”).
Learn from your failures…We look carefully at our ideas and goals set forth during our previous Roadmap Week, and inevitably, many of them won’t have come to fruition.
But also from your successes… Looking at how ideas were implemented successfully means we can use similar approaches that will lead to more successes.
Once we identify the ideas that have staying power, we sketch out a realistic work plan, and put individual next steps in Asana.
At Asana we track most of our work, and that means most if not all of our Roadmap week work, in Asana. We are able to track our failures and successes to a tee because we record who is doing what by when in Asana. Now, this doesn’t mean people are inherently punished if something goes awry (sometimes accountability makes people feel afraid). Instead, it means that we can use Dashboards and advanced search to track our work and monitor how we’re progressing overtime and at designated checkpoints. The gift of tracking our work in this way is it allows us to hit our Roadmap week goals, learn, adjust, and be more realistic for future endeavors when we need to be.
I’m curious to learn how you run Roadmap or Planning weeks at your companies and how you execute these processes in Asana. Based on what you read in the article, how are our processes similar to yours? What works well for your team that you think could work well for others?