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.
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 inviting them to try faster, problem-based "challenge tasks" when they were working ahead, and provide additional systems of support to those students wearing a slower pacing. 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.
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.
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 realise where resistance may show up. I was hired by a 40 people 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 then process sheets to the C-style manager. Regular check-ins were also added which did not discriminate either communication taste. Three months later, the defect rates were reduced by 60% and customer complaints decreased by 75% and the actual breakthrough was possible since we were able to get the people's problem sorted out first and naturally, then the process problem came into being.
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.
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."
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.
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.
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.
As I apply to the more complex problems, I will tap into the iterative problem solving that involves solving the problem step by step and doing additional modification in regard to the new information. All one needs is to be nimble, concentrate on the most useful things, and ensure that the solution to all the problems passed the short run requirements as well as the long run objectives that can assist in the long term. An excellent possibility to use this practice came when we were to develop our eCommerce to accommodate the significant rise of demand at Davincified. We have already known that we had to scale up but without affecting the quality of customer experience. We could choose to solve the problem little by little instead of having to make a overarching decision. To begin with, we discussed the performance of the web: we sorted out the shorter time of loading and provided the system with the capacity to address more traffic. Then we automated our order fill out in the attempt to focus our energies on the optimized way of advanced quantity of individualized packages. Over an iterative approach and being agile we met the demand without trying to lower up the quality. This was a solution not only to this immediate problem but regrettably it was the start of the solution on scalability in the future as we widen even more.
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.
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.
My go-to is reframing the core question driving my thinking. Most complex problems aren't actually about finding new information--they're about training your brain to look in the right direction using your Reticular Activating System (RAS). I had a client stuck in what seemed like an impossible financial situation during a business rebuild. She kept asking "Why isn't this working?" which trained her brain to find evidence of failure. I shifted her question to "What would success require from me today?" Within one session, she identified three revenue opportunities she'd been blind to before. The technique is simple: write down the question looping in your head, ask if it opens you up or shuts you down, then reframe it toward solutions. Your brain will literally start filtering for different information based on the question you feed it. I used this same approach when deciding whether to invest in a strategist I couldn't afford. Changed from "Can I afford this?" to "How can I make this work?" By week's end, I'd closed the financial gap through opportunities that were always there--my brain just wasn't programmed to see them.
My approach is "reverse engineering the emotional journey" - I start from the desired end feeling and work backwards through every touchpoint. After losing three pets and seeing how broken the industry was, I learned that complex problems usually have simple emotional cores. When we were scaling from one facility to 11 markets, we hit a wall with inconsistent service quality across locations. Instead of diving into operational manuals, I mapped out what a grieving family experiences minute-by-minute: the initial call, the pickup, the waiting period, receiving their pet back. Each step needed to feel dignified and transparent. The breakthrough came when I realized families needed control during their most powerless moment. We implemented optional viewing during cremations and 24-hour tracking - not because they were operationally easy, but because they addressed the core emotional need. Our Tampa franchisees saw immediate improvements in customer feedback once we focused on feelings first, logistics second. This method works because most business problems stem from unmet human needs, not technical failures. When you reverse engineer from the emotion you want to create, the operational solutions become obvious.
After a decade in property restoration, my go-to technique is the "immediate stabilization plus systematic investigation" approach. I tackle the urgent damage first, then methodically work backward to find root causes while the crisis is contained. Perfect example happened last month with a client who had water "everywhere" after returning from vacation. My project manager Chris found what looked like a simple bedroom leak, but our thermal imaging revealed moisture extending into three rooms. Instead of just drying the obvious spots, we traced the source through the attic and finded a decades-old broken ring in an antiquated tub fixture that had been slowly destroying structural elements. The key is never accepting the obvious answer when you're seeing complex damage patterns. We stabilized with industrial dehumidifiers and air scrubbers within 2 hours, but spent the next 48 hours systematically testing every potential source. This prevented what could have been a $50K structural repair turning into a $200K foundation issue. Most people want the quick fix, but in restoration the real problem is usually upstream from where you see damage. I always tell my team: contain the crisis fast, then become a detective.
My go-to is the "rhythm method" - sounds weird, but after 50+ years as a drummer and decades in accounting, I've learned that complex problems have patterns just like music. I break everything down to find the underlying beat, then build solutions layer by layer. When I started FZP Digital at 60, I had a nonprofit client whose website was hemorrhaging visitors and their donation numbers were tanking. Instead of jumping into design fixes, I mapped out their entire digital ecosystem like counting measures in a song - social media posting schedule, email campaigns, website traffic patterns, donor engagement cycles. Turns out their "complex web problem" was actually a timing issue. Their email blasts went out when their audience was least active, their social posts had zero rhythm, and their donation asks were completely out of sync with their content calendar. We restructured everything around a consistent 4-week cycle that matched their audience's behavior patterns. Revenue jumped 40% in six months. Most business owners try to fix everything at once, but like drumming, you nail the basic rhythm first, then add the fancy fills.
My go-to problem-solving technique is the "systematic breakdown approach" - I break complex issues into smaller, manageable pieces and tackle them one at a time. Having dealt with everything from solar installations in California to roofing challenges across Idaho's harsh weather conditions, I've learned that most "impossible" problems are just multiple smaller problems stacked together. Here's a specific example: Last year, we had a commercial roofing project in Twin Falls where the client was dealing with persistent leaks, but three previous contractors couldn't figure out the source. Instead of doing another general inspection, I systematically mapped the building into grid sections and tested each area during different weather conditions over two weeks. Turns out the issue wasn't the obvious damaged sections everyone kept repairing - it was a small gap where the TPO membrane met an HVAC unit that only leaked during specific wind directions. We fixed a $50 flashing issue that had caused thousands in water damage. The key is patience and documentation. I keep detailed notes on each step because what seems unrelated often connects later. This approach has helped us maintain our 4.6/5 customer satisfaction rating - people appreciate when you actually solve their problem instead of just treating symptoms.
My go-to is systematic triage - I assess severity, resources needed, and timeline constraints before taking action. Running a 24/7 towing operation means every problem needs immediate classification: life-threatening emergency, major disruption, or manageable issue. Last winter we got slammed with a 6-vehicle pileup on I-25 during a blizzard, plus three separate breakdowns within 30 minutes. Instead of sending trucks randomly, I mapped out response times, equipment needs, and safety priorities first. The accident got our heavy-duty wrecker immediately, while the breakdowns got consolidated into efficient routes for our light-duty trucks. This system cut our average response time from 45 minutes to under 30 minutes that night. We handled all situations without any secondary accidents or stranded customers, even though we were operating with limited visibility and dangerous road conditions. I apply the same logic to equipment failures and staffing issues - always categorize the urgency level first, then allocate resources based on real impact rather than whoever calls loudest.
My go-to is the "roof inspection approach" - I physically get up there and see the problem before making any decisions. Too many contractors quote jobs from the ground or make assumptions, but I've learned that complex problems reveal their true scope only when you're looking directly at them. Last month, a homeowner in Bellingham called about "a small leak" that three other contractors quoted as a $25,000 full replacement. When I got on the roof, I found the real issue: poorly installed flashing around their VELUX skylight that was letting water track along the rafters. The actual problem was a $800 skylight seal replacement, not a new roof. I document everything with photos and measurements while I'm up there, then walk the homeowner through exactly what I found. This eliminates the back-and-forth guessing that kills projects. In 20+ years, this approach has saved my customers over $2 million in unnecessary work because I'm solving the actual problem, not the symptoms. The key is never trusting secondhand information when the stakes are high. Whether it's a roof or any complex issue, get your eyes on it personally before committing resources to a solution.
When I'm faced with a complex problem, my go-to technique is to break it down into its smallest possible parts and attack them one at a time. I've always found that complexity is usually just a collection of smaller, solvable problems disguised as one overwhelming challenge. It's a mindset I carried into entrepreneurship after realizing that if I focused only on the big picture, I'd quickly get paralyzed by the scale of it. One example that stands out was early in Zapiy's growth. We had a client in the SaaS space who came to us with a major issue: their customer acquisition costs were rising while conversions were dropping. At first glance, it felt like a tangled knot—pricing, messaging, funnel design, ad targeting, all seemingly broken at once. If we had tried to solve everything simultaneously, we would have spread ourselves too thin and probably missed the root cause. Instead, I mapped the problem out step by step, almost like tracing a leak in a pipe. We started by isolating each stage of their customer journey. Where were prospects dropping off? What messaging wasn't connecting? By doing that, we discovered the issue wasn't with their pricing or product at all—it was with how their value proposition was being communicated in the first interaction. Their ads focused heavily on features, but customers were craving clarity on outcomes. We adjusted the ad copy and landing page messaging to focus on what their software enabled users to achieve, rather than what it did. Within two months, conversions jumped by more than 30 percent, and the acquisition costs started trending back down. That experience reinforced something I've seen repeatedly: when you dissect a complex issue into smaller questions—almost like a checklist—you not only make it manageable, but you also uncover insights you'd miss if you stayed at the surface level. For me, problem-solving isn't about rushing to the fix; it's about patiently unpacking the problem until the solution feels almost inevitable.