“Ok, here’s the roadblock, but we can totally figure this out. I have a plan on how we can tackle it.” ⏳ 4 hours later…..
“Ok team, thanks for the rapid problem-solving meeting. We’ve now prosecuted the plan. Triage is underway. To recap, I’ll do this. You take that. She’ll own this part. He’ll own that other part. Now let’s go deliver! We’ve got this. See you back here in 24 hours to confirm our collective resolution and success.”

What to do when you hit that inevitable project roadblock
The above are conversations that transpired on a super thorny, complicated, tech project. Hitting a roadblock on a technical project itself is never a surprise. C’mon, you know the kind – tons of systems, tons of competing priorities, tons of stakeholders, not enough time, unforeseen downstream impacts of something not operating as intended (say what? never). Then that heat that envelopes a team nearing the go-live deadline – and 💥 – big roadblock emerges and someone has to call an audible.
We overcame such a project this week and it had me thinking about what makes a team high-functioning. I saw it in action. I was in the thick of it with them (and I’m morbidly captivated to moments like this because I’m obsessed with the power of human connection and its resulting achievements). Days later, I’m still reflecting on how proud I am of what the team overcame and ultimately accomplished – not just the ‘what’, but our ways of working (and treating each other) while doing the ‘what’.
I’ve routinely noticed 2 FEELINGS that make all the difference:
- Trust (I trust my co-worker to do his/her part and they can count on me to do mine)
- Winner’s Mindset (I believe we can conquer this and find a successful path forward)
High functioning team members have innate accountability
My next observation after calling the audible was our Head of Product Marketing saying, “I understand the roadblock and I have a triage plan we could rapidly execute to navigate this. It comes with tradeoffs so let’s assemble the team now and prosecute it.” She did this unasked with total ownership. Then our Senior Technical Product Manager did the same thing, but on the technical side.
Back the “what” – here’s what the team did:
uh-oh moment ➡️ project audible called ➡️ roadblock identification ➡️ areas of ownership established ➡️ rapid problem-solving as a group ➡️ plan created ➡️ tradeoffs explored ➡️ expectation setting ➡️ stakeholder alignment on triage-plan ➡️ divide and conquer to execute ➡️ plan activated
This all happened in hours – not days and weeks, HOURS.
Today we celebrated that we ‘did the thing’. Internal comms went out about our go-live and the action plan to finalize all the remaining to-dos. Remember those tradeoffs? People typically won’t be upset about tradeoffs so long as you set clear expectations and get buy-in along the way.
This is where it’s important to have durable skills, not only hard technical skills.
