When I was first introduced to Asana in early 2025, I was told that it was “for people who can’t quite figure out Jira" 
The company already had Asana, but there were no real champions, no shared way of using it, and certainly no clear process behind it. I wondered, then curiosity got the better of me.
I started exploring Asana Academy, mostly to understand what the tool was actually designed to do. One course led to another, and before long I found myself participating in the Asana Ambassador Program—the moment my Asana journey truly began.
What changed my perspective wasn’t the technology itself, but the thinking behind it
Through earning my Asana Foundations, AI Studio Foundations, AI for Work, and Workflow Specialist badges 
, I began to see Asana not as a “simpler” alternative, but as a platform built around intentional workflow design 
. It’s not about complexity—it’s about clarity 
. And clarity, I’ve learned over a long career, is often the hardest thing to achieve.
I started small, using Asana for my own individual work management. For someone who spent years keeping priorities, dependencies, and next steps neatly stored in her head (a system that worked—until it didn’t 
), having work visible and structured felt surprisingly freeing.
By Q4, I applied those same principles to roll out a defined process using Asana. Nothing theoretical—real work, real timelines, real people. Goals that were visible instead of assume.
The results were impressive 
Enough so that in 2026, the entire team will be using Asana to track goals 
. And yes—quietly, I’m hoping it doesn’t stop there. With the right foundations, there’s no reason this couldn’t scale to the business unit level. (A secret wish… for now 
)
The biggest lesson for me?
Learning first really does lead to impact.
I used to carry everything in my head.
Now I’m helping build a system that doesn’t rely on any one person doing that—and that, to me, is real progress 