Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Discovery Happens!
In each step of a development project, we learn something new, and often the knowledge requires our team to revisit completed work. Here is a matrix tool that helps manage your network of activities to minimize setbacks by anticipating possible discoveries. Envisioning a step back can be like taking two steps forward.
The good news is that as we execute our projects we learn something new every day. The bad news is that as we execute our projects we learn something new every day. Such is the dilemma faced by the project manager of a developmental project. Typically these projects move through requirements definition, specification development, design, product implementation, testing, acceptance and delivery. If it were only so straightforward! The real challenge is that at each step we learn more about what we are doing, which can force us to revisit previously completed work. This is not a result of poor quality. We simply learn as we go, and sometimes it means that what we did previously we later learn is wrong, and rework is required.
For example, we built it and now we test it, but it doesn’t pass. How could that happen? We may have a new interpretation of the specification but tested it to our old understanding. We may reinterpret the specification and find we designed it wrong. We might have erred in mapping the specification to the test procedure. Now we&…
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Humor is but another weapon against the universe." - Mel Brooks |