Speed Beats Perfection in Problem Solving
- Jun 24
- 7 min read
Companies encounter various challenges across departments. In human resource management, over 70% of HR professionals identify people challenges and talent gaps as major obstacles. In change management, 70% of initiatives fail and 88% of business transformations don’t meet their original goals. Cash flow management is also a concern, with 49% of finance professionals worried about unreliable data.
Overall, 82% of businesses report facing at least one significant challenge each year. The "Do It Wrong Quickly" principle addresses challenges by encouraging project teams to experiment with solutions iteratively, avoiding overanalysis. This approach helps teams try solutions early, learn from mistakes and adjust swiftly, encouraging quick feedback and adaptability in fast-paced environments.
What if you could turn your biggest challenges into opportunities for growth? Imagine a world where failure isn’t feared but embraced as a stepping stone to success.
1. Clarify the Objective
Before moving into solutions, ensure your team clearly understands the project’s overall goals. At this stage, detailed plans are not essential, but a high-level understanding of the problem and the desired outcome is vital for alignment.
During the project kickoff, establish a clear problem statement, define a timeline and set practical constraints. This structure keeps your team focused, supports quick iterations and helps them move efficiently towards solutions without unnecessary delays or complications.
Establish a clear problem statement and communicate it to the team
Define a realistic timeline and practical constraints to guide progress
Ensure all team members understand the desired outcome and their role in achieving it
How well does your team grasp the overarching goals before diving into solutions?
Example: A marketing team clarifies the objective of a campaign to increase brand awareness within three months, sets key performance indicators and aligns tasks accordingly, resulting in more focused efforts and measurable impact.
2. Prioritise Speed over Perfection
With this approach, your aim is to generate solutions quickly, accepting that the first attempt may be flawed or incomplete. Taking action drives learning and reveals practical insights that help your team improve with each iteration.
Encourage your team to produce rough prototypes, mock-ups, or simple processes to address the problem. Avoid waiting for perfection and focus on ideas that are “good enough”. Use time-boxing by setting a fixed period, such as 12 hours, for each attempt.
Encourage rapid prototyping and quick implementation of ideas
Set fixed time limits for each iteration to maintain momentum
Learn from early attempts and refine solutions based on feedback
How effectively is your team balancing speed with learning to improve outcomes?
Example: A product team creates a basic app prototype within 24 hours, tests it with a small user group and iterates based on feedback, accelerating development while avoiding costly delays.
3. Run Small, Quick Experiments
Once you have a solution, test it quickly by running a small experiment. Apply a limited version or try it in a low-risk environment so you can gather fast, valuable feedback for future improvements.
Break large tasks into smaller, manageable sub-tasks that you can test individually. For example, when developing a feature, test one function first before moving on to the full implementation of the entire feature set.
Break large tasks into small, testable sub-tasks
Run experiments in controlled, low-risk environments to gather feedback
Analyse results quickly and iterate on improvements based on insights
What small experiment can you run today to validate your solution before full-scale implementation?
Example: A software team tests a single search function of a new app with a small user group, collects feedback and refines the feature before rolling out the complete update.
4. Embrace Failure and Learn
With this approach, you should expect some failure and that is completely acceptable. Treat each setback as a learning opportunity, as every failure reveals what does not work and moves you closer to an effective solution.
After each test, collect feedback quickly and reflect on what went wrong. Record the key learnings to guide improvements and shape the next iteration, supporting continuous progress and stronger decision-making in future tests.
Treat failures as opportunities to gather insights and improve
Collect feedback promptly after each test to understand what went wrong
Document key learnings to guide future iterations and decisions
How can you use recent setbacks to refine your approach and strengthen outcomes?
Example: A design team launches a pilot feature that receives negative user feedback, reviews the issues and adjusts the interface, resulting in a significantly improved second version.
"Sometimes big problems are best solved with lots of small and creative solutions." - Ricardo Salinas Pliego
5. Iterate Quickly Based on Feedback
If a solution does not work as expected, revise it quickly and try again. Focus on small, incremental improvements instead of starting over, so you can adapt without overhauling everything and losing momentum.
After receiving feedback, identify small, manageable tweaks for the next iteration. Use short feedback loops, such as daily or bi-weekly check-ins, to enable quick adjustments and keep your project moving forward with efficiency and clarity.
Make small, incremental adjustments based on feedback rather than overhauling completely
Use short feedback loops, such as daily or bi-weekly check-ins, to guide iterations
Prioritise rapid revisions to maintain momentum and continuously improve
How can you incorporate feedback efficiently to enhance your solution without losing progress?
Example: A development team receives user input on a beta feature, implements minor adjustments each day and steadily improves usability without delaying the full launch.
6. Keep Communication Open and Fluid
To keep the process moving quickly, maintain open communication with your team. Share findings and updates in real time to keep everyone aligned, encourage collaboration and support effective problem-solving as you move forward together.
Use tools like Slack, Microsoft Teams, or Trello to monitor and manage ongoing experiments. These platforms help you track progress, outcomes and updates, keeping your team aligned and informed throughout the process.
Share updates and findings in real time to maintain team alignment
Encourage collaboration by keeping communication channels open and accessible
Use project management tools to track progress, outcomes and updates efficiently
How well is your team staying informed and connected throughout the process?
Example: A product team uses Trello to log experiment results and Slack for instant updates, enabling quick decisions and keeping everyone aligned on the next steps.
7. Encourage a Safe Environment for Experimentation
For this principle to work, you must create an environment where your team feels comfortable experimenting, knowing there are no negative consequences if something fails. Encouraging risk-taking without fear is essential for success.
Build a culture where mistakes are seen as learning opportunities rather than failures. Lead by example: if you, as the project manager, make a mistake, share it openly, discuss the lessons learned and encourage your team to grow from the experience.
Create a culture where experimentation is welcomed and failure is seen as a learning opportunity
Lead by example by sharing your own mistakes and the lessons learned
Encourage risk-taking without fear of negative consequences to spark innovation
How safe does your team feel in trying new ideas and learning from mistakes?
Example: A development team openly discusses a failed feature rollout, analyses what went wrong together and applies the insights to improve the next version, boosting confidence and creativity.
8. Know When to Pause and Reflect
While acting quickly is key, you must also pause periodically to assess overall progress. The "quickly" mindset can dominate, so set regular intervals to reflect, review lessons learned and ensure alignment with the bigger picture.
After several iterations, hold a brief retrospective meeting to assess what approaches are working. Use this time to identify what needs adjustment and how you can improve the overall strategy for better results moving forward.
Schedule regular pauses to review progress and assess overall strategy
Conduct brief retrospective meetings to identify successes and areas for improvement
Use reflections to adjust approaches and align future actions with objectives
How often are you taking time to step back and evaluate whether your efforts are moving in the right direction?
Example: A marketing team holds a weekly reflection session after multiple campaign tests, reviews what resonated with audiences and adjusts messaging and channels for the next round, improving overall performance.
The Unexpected Benefit of Celebrating Failure | Astro Teller (CEO @ X The Moonshot Factory)
Sample Case: Dropbox
Before building a single line of code for its cloud‑storage platform, Dropbox used a rapid experiment to test whether anyone actually wanted the product concept. Rather than develop a full product first, founder Drew Houston created a three‑minute explainer video that showed the core functionality of seamless file synchronisation across devices. This video served as the minimum viable product (MVP) and was used purely to gauge real market interest rather than demonstrate a finished product.
The video was posted on tech forums and the Dropbox landing page with a call‑to‑action to join the beta waiting list. Within 24 hours, sign‑ups on the waiting list increased dramatically - from around 5,000 to approximately 75,000 people - providing clear evidence that users wanted the product concept before it even existed.
This outcome validated the core assumption that there was real customer demand for a simple file‑syncing tool, allowing the team to continue development with confidence and focus on the features users cared about most. The data from this rapid MVP experiment helped Dropbox secure further investment and refine product design based on actual user interest.
Key takeaway: Dropbox’s early MVP successfully validated demand quickly with minimal cost and effort, demonstrating how a simple experiment can provide far more actionable insight than months of upfront development trying to build a “perfect” product.
"Identify your problems, but give your power and energy to solutions." - Tony Robbins
There are a number of benefits to the 'do it wrong quickly' principle that can help drive project management success. It allows teams to deliver solutions faster by focusing on action rather than lengthy analysis. Regular feedback loops encourage continuous improvement, enabling incremental progress. This adaptability also helps teams to pivot based on real-time feedback, while encouraging engagement and creativity through a culture of experimentation.
However, there are challenges to be aware of when using this approach. Fear of failure can hold team members back, so it's important to emphasise learning over perfection. Regular check-ins help to maintain focus on both short-term and long-term goals. In addition, over-correction can occur if teams make too many changes too quickly, so it's important to track the outcome of each experiment and avoid repeating mistakes.
Ultimately, the "Do It Wrong Quickly" approach empowers teams to find solutions faster and more efficiently. It encourages a culture of creativity and continuous improvement, where experimentation leads to real-world success. Embrace failure as part of the learning process and iterate with confidence.
