Slow Down to Speed Up
- rayliu16
- Jul 1
- 2 min read

Early in an engagement, I ask a lot of questions that might seem obvious.
"Wait โ who exactly is responsible for that decision?" "When you say 'aligned,' what does that actually mean?" "So the deadline is EOW โ does that actually mean by close of business 5pm ET on Friday or anytime before Monday at 9am ET?"
I've had people in rooms visibly impatient at these questions. And I get it. Everyone is busy. The instinct is to move fast, stay high-level, and figure out the details as you go.
But here's what I've learned after 10+ years of managing complex, cross-functional initiatives:
๐จ๐ป๐ฐ๐น๐ฒ๐ฎ๐ฟ ๐ป๐ฒ๐ ๐ ๐๐๐ฒ๐ฝ๐ ๐ฑ๐ผ๐ป'๐ ๐๐น๐ผ๐ ๐๐ต๐ถ๐ป๐ด๐ ๐ฑ๐ผ๐๐ป ๐ฎ๐ ๐๐ต๐ฒ ๐ฒ๐ป๐ฑ โ ๐๐ต๐ฒ๐ ๐๐๐ผ๐ฝ ๐๐ต๐ถ๐ป๐ด๐ ๐ฐ๐ผ๐น๐ฑ ๐ถ๐ป ๐๐ต๐ฒ ๐บ๐ถ๐ฑ๐ฑ๐น๐ฒ.
You get two weeks into execution and suddenly nobody knows who owns the next deliverable. Or two teams were both waiting on each other. Or the "agreement" in the meeting was actually three different people hearing three different things.
The scramble to recover from that confusion takes far longer than the five minutes it would have taken to get specific at the outset.
Slowing down to get clarity โ on who does what, by when, and what "done" actually looks like โ is one of the highest-leverage investments you can make at the start of any project.
It's not about being slow. It's about making sure that when you move fast, you're all moving in the same direction.
A few questions I've learned to always ask before leaving any meeting:
1. ๐ช๐ต๐ฎ๐ ๐ฎ๐ฟ๐ฒ ๐๐ต๐ฒ ๐ป๐ฒ๐ ๐ ๐๐๐ฒ๐ฝ๐? (Note: be clear on the action, not just the intended goal.)
2. ๐ช๐ต๐ผ ๐ผ๐๐ป๐ ๐ฒ๐ฎ๐ฐ๐ต ๐ผ๐ป๐ฒ? (Note: Make sure to name a specific person, not a team.)
3. ๐๐ ๐๐ต๐ฒ๐ป? (Note: Make sure you have a clear date and time, including time zone for initiatives with regionally scattered teams, marked.)
Three questions. Every meeting. No exceptions.
The answers are almost never as obvious as people assume.
Comments