Finding the Fastest Path
How to Answer the Impossible Timeline Question
We’ve all been there: you’re in a meeting, and your boss turns to you and asks:
“How fast can we get this done?”
It’s a question that can feel impossible to answer confidently - and yet it comes up all the time.
Earlier in my career, I was in a crowded boardroom when a boss asked that very question.
One of my colleagues spoke up and said something I’ve never forgotten:
“If you want the fastest path, we need to find the critical path first.”
What he was referring to - and went on to explain - was the Critical Path Method, a project management technique that identifies the longest sequence of dependent tasks required to complete a project.
In other words, it doesn’t just tell you what needs to be done - it tells you the fastest possible way to get it done, assuming everything goes perfectly.
Of course, in the real world, projects still encounter delays. You’ll need to account for wiggle room, third-party dependencies, and unexpected friction. But starting with the critical path gives you an objective foundation to build from - and a sobering reality check for even the most eager boss.
So the next time someone asks you,“How fast can we get this done?”, start by identifying the critical path first, and then build the plan from there.
It turns a subjective guess into an objective answer - and sets everyone up for success.
- Seth
About The Author
Seth is the founder and CEO of Kanahoma, a San Diego-based performance marketing agency on a mission to build a better agency for organizations building a better world.
You can learn more about who we are and what we do at www.Kanahoma.com.
Great advice here! A practical way of giving realistic feedback on timelines.
Seth you familiar with the iron triangle? Good, fast, cheap pick two. You want it fast then it's either to be cheap but not very good or good but expensive. It's a good reminder that there is always a sacrifice that must be made.
In the product world we tend to thing more in MVP (minimum viable product). What is the thing that we can build that accomplishes the goal but has the absolute fewest bells and whistles. Maybe it doesn't scale or maybe it makes some assumptions for you on specific variables but once again sacrifices are made to ship it fast. You can always come back and add functionality if the hypothesis holds that there is value (usage/adoption) in it.