What is your project's need for speed?

Enjoy delivering highly successful projects.Connect with moments of inspiration.

I am working on a project right now where the sponsor is adamant, they want a working version as quickly as possible.

On the face of it, the expectation feels intense. Concept, design, testing, working version - in 8 weeks.

My first reaction was the one you might be having too: That sounds unrealistic.

---

The Behaviour I noticed

I stepped into their shoes.

"If we are slow, they may lose a lot of money. Speed matters."

And while getting it right matters, it is not the highest priority. The bigger risk is not having anything in the real world, quickly.

• How important is it to get it right?
• How painful is it if we are slow?

Once you see that, the 8 week push becomes easier to explain.

Tuesday Action

Spend 5 minutes on one live project.

• Are the timeframe expectations explained by the grid below?
• Or does the grid show your project should be treated differently than it is today?

​

Use this model to inform your thinking on:

• How much design depth you need.
• How many versions you should expect before you go big.

​

Next week, I will share a tool that gives you the full picture and a wider set of Prove It Works tools.

See you next week,

Greg

P.S. If you're interested to explore our core discovery, the four Success Factors, it's free and the basis now for everything we build.

Download the 12 Steps (free) →

Check out the APEX-4 Project Expert Formula, it gives you the 12 steps to deliver against each success factor.

You won't regret using this guide to and readiness assessments to level up your projects.