Investigating Your Ability To Iterate

“This is our first build. If we hear from users that we need to refine, we can always iterate based on their feedback.”

When you hear this, ask your product team the following questions:

  1. If users tell us our solution doesn’t meet their needs, what’s the economic cost of pivoting and redoing this work to better meet customer needs?
  2. Will we have capacity to immediately pivot and quickly redo this work if our initial solution fails?
  3. Assuming we don’t have immediately available capacity, where will this rework fall in our product development pipeline? Would its cost of delay justify jumping the queue to the top of our backlog, or will this work sit in the queue waiting to be reworked?
  4. If this work will jump to the top of the backlog, what’s the cost of the delay of the work that will be pushed back?
  5. If we determine this rework will sit in the queue for a certain period of time, will the rework still be relevant after that wait period? Or will we have missed our window of opportunity?

Do the answers to these questions scare you?

Iterative. Pivots. Agile. Trendy words that are fun to talk about, but hard to achieve.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.