In this talk, I argue that admitting “we don’t know” isn’t a weakness in software development, but a way of clearly seeing where progress, learning, and value are most likely to be found. Using real project experience, I show how recognising uncertainty allows teams to design experiments, seek fast feedback, and move forward with intent—replacing over-planning and ego with action, adaptation, and informed decision-making.