Solving IT Problems Faster - Let me count the ways
New project managers can add value when solving problems on projects, but experience counts for a lot when it comes to resolving problems efficiently.
IT projects are about solving problems under the constraints of time, cost, and quality. In over 20 years as a project manager, I’ve been involved in a lot of problem-solving.
Here are some practical ways to deal with problems on your projects:
Clarify the Problem Precisely
Define who, what, when, where, and why. Who does it affect? What does the solution look like? Misunderstandings waste time and money. Take notes.
Involve Your Architect
IT architects and solution designers are stakeholders in the solution. The sooner they are involved, the better—if they exist on your project.
Gather Facts, Beware of Assumptions
Use your communication skills to talk to team members, stakeholders, and users. Review data and project metrics to separate fact from opinion. Be open to the possibility that assumptions may be part of the problem.
Break the Problem into Smaller Parts
Breaking complex problems down makes them manageable. Identify where you can start making progress and gaining momentum.
Speak to Stakeholders Early
Stakeholders often have unique insights into the problems being experienced. Aligning with them early prevents political and emotional derailments later.
Use Problem-Solving Frameworks and Techniques:
Mind Mapping – Visualise system connections and generate insights.
Brainstorming – Generate multiple ideas in a non-judgmental environment before filtering down to practical solutions.
5 Whys – Ask “Why?” five times to drill down to root causes.
Root Cause Analysis – Combine methods to uncover problems.
Risk Register Analysis – Track, categorise, and mitigate risks before they escalate.
Pareto Analysis – Identify the 20% of causes responsible for 80% of issues.
Other useful techniques include Business Process Modelling, Fishbone Diagrams, Impact vs. Effort Matrices, SWOT Analysis, Failure Mode and Effects Analysis (FMEA), and Kanban bottleneck analysis.
Agile Problem-Solving Techniques:
Agile techniques are practical, lightweight, and people-focused, aligning with continuous delivery and fast feedback cycles:
Retrospectives and Daily Stand-ups – Surface issues early for immediate action.
Swarming – The team tackles a problem together instead of waiting for one person to resolve it.
Timeboxing – Set a time limit to investigate or address a problem, preventing analysis paralysis while encouraging iterative learning.
Spikes – Allocate a “spike” (time-boxed research or prototyping) to test approaches to complex problems before committing to a solution.
Refine the Definition of Done – Many problems arise from unclear expectations. Reviewing and refining the DoD helps prevent quality and scope misunderstandings.
Evaluate Options and Prioritise
List potential solutions and prioritise actions that deliver high value with manageable effort.
Communicate Clearly
Share updates transparently—what is being done, why, and by when. Transparency builds trust and prevents the rumour mill from taking over.
Test and Iterate Quickly
Pilot solutions on a small scale to validate them before full rollout, reducing risk and adapting to unforeseen challenges.
Monitor and Adjust
Set measurable indicators to confirm the problem is resolved. Be ready to pivot if new issues surface.
Capture Lessons Learned
Record what worked and what didn’t. This prevents recurrence and strengthens your team’s maturity and capability.
Solving problems well as a PM isn’t about having all the answers immediately. It’s about asking the right questions, engaging the right people, and systematically testing solutions under real-world constraints.
What is your favourite problem-solving technique?
#ProjectManagement #Leadership #ProblemSolving #PMO #Delivery #ContinuousImprovement