12 Problem-Solving Techniques For Tough Challenges

Triangulate Multiple Perspectives Then Test Solutions

When faced with a problematic problem, my go-to technique is what I call “triangulated iteration.” Roughly: obtain three perspectives, attempt a lean iteration, learn fast, repeat. It keeps me out of a one-trick pony mindset, and enables me to discover solutions I never would using single-source intuition or only one input of data.

Here’s a real example from Legacy: we were fielding complaints from families that some learners were navigating our learning platform too quickly, while others were left behind. There was nothing simple about the problem–some classes were yawningly boring and others felt slow, and of course, one pacing could never satisfy all learners.

So, I drew on three lenses: 1) teacher feedback (what they observed in class interactions), 2) student surveys (how they felt week to week), and 3) usage data (drop-off times, duration of logins, assignment completion). We then created a small pilot to test some “adaptive pacing” in three core classes; teachers would embed micro-checkpoints within lessons that would provide students with either optional extension materials or invite them to try faster, problem-based “challenge tasks” when they were working ahead, and provide additional systems of support to those students working at a slower pace.

We began with one group of 50 students. Within a month, student satisfaction in such classes was up 25% and mid-lesson abandonment dropped more than 30%. Teachers reported fewer “one size fits none” comments, and parents e-mailed expressing thanks for making their children feel heard.

My advice to other leaders: don’t try to get to the bottom of knotty problems with a single source of truth. Seek out multiple viewpoints, build a light test, see what moves the needle, and iterate. It’s messy, but that messiness is where the real solutions live.

Apply First Principles To Rebuild Solutions

My go-to problem-solving technique is to break complexity down into first principles, stripping the issue to its fundamentals and rebuilding the solution from the ground up.

When challenges feel overwhelming, it’s often because we’re looking at them through layers of assumptions, legacy processes, or emotions. By asking “What do we know for sure?” and “What outcome do we really need?”, I can cut through the noise and see the core problem clearly.

One example: In our early days at Esevel, a client needed to onboard a large distributed team across multiple countries in a matter of weeks. At first, the complexity seemed unmanageable—different regulations, varying device logistics, and time zone coordination.

Instead of trying to fix everything at once, we stripped the problem back to first principles:
– Every new hire needs a secured device on day one.
– The device must be compliant with local laws.
– The process must be trackable and repeatable at scale.

From there, we rebuilt the workflow, setting up centralized procurement with local deployment partners, automating tracking, and standardizing compliance checks. The result? The client’s entire team was onboarded smoothly, on time, and with full visibility.

For me, first-principles thinking isn’t just a technique; it’s a mindset. It allows me to navigate uncertainty with clarity and build solutions that scale.

Map Behaviors Before Addressing Process Problems

I have what I call behavioral mapping whereby I use DiSC tests in establishing the way various stakeholders process and make decisions. This lets me know about who requires more data than the rest, who prefers seeing the big picture, and who needs social confirmation before taking action. Then I overlay the ADKAR model created by Prosci to realize where resistance may show up.

I was hired by a 40-person manufacturing company with quality control problems that were losing customers last year. I had to map the behavioral styles of the production team and the management rather than getting into process fixes, and then I found out that their quality manager (high C in DiSC) was not being listened to by their production director (high D) who only valued speed and not accuracy.

I did not introduce new procedures but instead did a redesign of communication. Then I assisted them in the development of a reporting structure where quality information was available in the executive dashboard to the D-style director and process sheets to the C-style manager. Regular check-ins were also added which did not discriminate against either communication style.

Three months later, the defect rates were reduced by 60% and customer complaints decreased by 75%. The actual breakthrough was possible since we were able to get the people’s problem sorted out first and naturally, then the process problem was addressed.

Test Solutions Before Full Implementation

When I face complex issues, my go-to technique is running small-scale trial implementations before full rollout. I’ve found that testing new processes or solutions with a limited group first helps identify potential problems that weren’t obvious in the planning stage. For example, when our company needed significant process improvements, I insisted on piloting the changes with a small team before company-wide implementation. This approach allowed us to catch several unforeseen issues and refine our solution before scaling up. The method not only prevents costly delays but also reduces resistance since employees see a more polished final product. I consistently use this technique because it transforms abstract planning into practical reality where real problems can be solved before they affect the entire organization.

Consult Trusted Mentors For Outside Perspective

When I’m up against a really complex problem, my first instinct is usually to reach out to a mentor. I’ve been lucky enough to build relationships with people who’ve been through things I haven’t, and sometimes just talking it out with someone a step removed makes everything clearer.

One time that really stands out was early on at Tall Trees Talent, when we were weighing whether to expand into a new vertical in the energy sector. On paper, the numbers looked good, and internally, the team was excited. But something about the move felt off to me. I was more nervous than I should have been.

So, I picked up the phone and called a mentor who’d scaled his own firm years before.

What he said shifted my thinking. Instead of asking whether we could move into that space, he asked me whether we had the bandwidth to sustain it without losing focus on what was already working. That simple question reframed the entire discussion. We ended up pausing the expansion for a year, doubling down on our core, and honestly, it was the best move we could’ve made at the time.

That experience taught me that sometimes the best problem-solving technique isn’t grinding away at the numbers. It’s high-touch, experience-based advice from someone you trust.

Break Complex Issues Into Manageable Parts

My go-to problem-solving technique is breaking the issue down into smaller, manageable parts and then addressing them one at a time. Complex problems often feel overwhelming because we look at them as a whole, but when you isolate the pieces, patterns and solutions emerge more clearly.

For example, when AI transcription tools started flooding the market, it created a complex challenge for us: how do we position GMR Transcription as a 100% human-powered provider in a space suddenly obsessed with automation? Instead of tackling it all at once, we broke it into smaller problems: messaging clarity, SEO positioning, client education, and internal team alignment.

By solving each of these step by step (updating service pages, creating content that highlighted accuracy and confidentiality, and hosting open discussions with clients), we not only refined our positioning but also saw a boost in organic visibility and stronger client trust.

The lesson? Big problems feel less intimidating when you dissect them, and solving them piece by piece often creates a stronger, more lasting solution than chasing one “big fix.”

Tackle Small Steps To Build Success Chain

My go-to technique for complex problems is breaking them down into the smallest possible parts. I once worked with a rescue dog who had severe anxiety and aggression towards strangers, making vet visits impossible. Instead of tackling the “vet visit” as one big issue, I broke it down. First, we just worked on getting comfortable in the car. Then, we focused on calmly sitting in the vet’s parking lot. After that, we practiced walking into the empty waiting room and leaving immediately. We slowly added duration, the presence of a receptionist, and then the vet tech.

By isolating each trigger and creating a positive association for every tiny step, we successfully turned a terrifying ordeal into a manageable, stress-free experience for both the dog and its owner. It’s all about building a chain of successes.

Map Case Timeline For Complete Clarity

I work with clients who often face overlapping legal and emotional challenges, so I focus on clarity first.
I map the entire case timeline on a whiteboard—deadlines, risks, required documents—so we can see the big picture.
In a recent family-based immigration case with multiple dependents, this approach let us stagger applications in a way that minimized processing delays and kept the family together through the process.

Learn From Mistakes With Preventative Measures

My go-to problem-solving technique is to first accept that a mistake has happened, treat it as a lesson, and focus on preventing it from happening again. For example, at our corporate merch company, we once accidentally mixed up two clients’ specifications. Since we don’t just print on ready-made T-shirts but sew everything from scratch, the end result was one company’s logo on the front and another company’s logo on the back. We only realized the mix-up when we opened the boxes with the T-shirts.

I could have spent hours blaming myself and the team, but that wouldn’t have solved anything. Instead, we immediately fixed the issue and established a new golden rule: always double-check specifications. Now, we verify every detail before moving forward.

This experience reinforced my belief that mistakes can become turning points. And if you address them quickly, learn from them, and put the right processes in place, they can strengthen your business in the long run.

Start Fresh To Avoid Tunnel Vision

My technique might vary a little bit depending on the exact issue I’m dealing with, but what I tend to do is once I realize it’s a complex issue without an easy solution, I’ll restart from scratch. I’ll try to scrap what I’ve thought or even done up until that point and reassess the situation from the baseline with a clear perspective. This helps me quite a bit with preventing tunnel vision, and it also gives me the freedom to ask for opinions from others if I need it. Recently this technique helped me solve a budget-related issue.

Factor Problems Into Atomic Components

My go-to problem-solving technique is always ‘factoring the problem’.
The core idea is to take a large, complex, and often overwhelming issue and break it down into the most atomic, solvable components you can. By refusing to engage with the large problem and instead focusing on the smallest possible sub-problems, you can make steady progress, isolate points of failure, and build momentum toward a complete solution. It turns an intimidating challenge into a manageable checklist.