Recommended Listening (Content warning – this isn’t the edited version):

Before we jump into our thrilling Tomb Raider-themed exploration of problem-solving, I’d like to share a bit of personal insight. One of the most valuable skills I’ve acquired throughout my career is the ability to methodically approach a problem, strategize a solution, and execute it effectively. Whether it’s resolving an issue, enabling a new capability, or streamlining an existing process, this strategic problem-solving approach has been a common thread in my professional journey.

I remember training new hires in call centers to support BlackBerry customers back in my early corporate days. A key part of this training involved understanding the BlackBerry messaging process, end-to-end. We literally required new hires to memorize and draw the process diagram for technical support positions. At first, the importance of this deep dive was lost on most of us, including myself. However, as I delved deeper, I realized its inherent value. Knowing what SHOULD happen versus what IS happening is half the battle won in problem-solving. This principle holds true across a spectrum of scenarios, not just in technical support.

Regardless of the problem you’re trying to solve or solution you’re trying to design, understanding the current state (“what IS happening”) and the ideal state (“what SHOULD be happening”) is crucial. Once you identify where these two states diverge, you’ve found your starting point. This applies whether you’re troubleshooting an issue or designing a new process. To truly tackle a problem, you need to understand the current situation, identify what needs to change, and define measurable criteria for success.

One word of caution: don’t let your existing skills or lack thereof limit you (note to self: consider writing an article on transforming “I can’t” into “I’m learning how to…”). It’s easy to fall into the trap of Maslow’s Hammer (one of my favorite cognitive biases – the other is the Dunning-Kruger Effect; Great images for that one if you want a laugh), thinking that your familiar tool is the only solution. Conversely, don’t assume a problem is unsolvable because you lack a specific skill or tool. Instead, view these scenarios as opportunities to expand your ‘toolbox’. Broaden your skillset, explore different approaches, and remember that every problem, like a stage in Tomb Raider, has multiple paths to the solution. It’s all about finding the path that works best for you.

Now, with that in mind, let’s strap on our metaphorical backpacks, gear up with our analytical tools, and set off on our problem-solving adventure!

Jeff

In this quest, you’re not just a data analyst, a software developer, a sales strategist, or a home improvement enthusiast – you’re a Solution Raider, armed with procedural thinking and a resolute determination to uncover the treasure of resolution.

Just as Lara Croft meticulously plans her moves, approaches enigmas with a curious and strategic mindset, and persists against all odds, effective problem-solvers deploy structured thinking, analyze their environment in detail, and tenaciously work around roadblocks.

In this article, we’ll discuss procedural and methodical ways of approaching problems, and explore problem-solving and solution-finding strategies through the adventurous framework of Tomb Raider, applying them to a wide range of scenarios. So, strap on your metaphorical backpack, ensure your analytical tools are at hand, and prepare to embark on a universal problem-solving quest!

Mapping the Unknown: Identifying the Problem

Lara Croft, our intrepid adventurer, wouldn’t set off on a quest without first identifying her goal, would she? In her case, it could be a lost artifact, a hidden city, or the solution to a historical mystery. Similarly, the first step in any problem-solving endeavor is to clearly identify and understand the problem you’re facing.

Just as Lara studies ancient texts and maps, you need to gather as much information as possible about your problem. This could involve researching existing documentation, speaking to those who are experiencing the problem, or conducting initial analyses. Only by clearly defining the problem – what needs to be accomplished, or what’s not working – can you hope to find a fitting solution.

In the world of data analysis, for instance, a well-defined problem could be the need to identify the factors leading to increased churn rate over the past quarter. In contrast, a poorly defined problem might simply be a desire to “improve customer retention,” which doesn’t give much direction on where to start.

This stage of problem-solving sets the tone for the entire process, so it’s crucial to get it right. Don’t rush it; take your time to examine the issue from all angles and gather as much relevant information as possible. It’s better to spend extra time clarifying the problem than to rush into a solution that might not work.

Remember: our goal isn’t just to find any solution; it’s to find the most effective and efficient solution to our specific problem, and with all of the automation we’ve discussed becoming more prevalent in the business world today, it also needs to be robust and repeatable. Just as Lara wouldn’t be satisfied with finding any old artifact, we aren’t aiming for a quick fix that doesn’t truly address the underlying issue, or a temporary solution that will be easily disrupted in the future.

Let’s take a moment to adjust our metaphorical backpacks, and prepare to descend into the depths of the problem-solving process. We’ve identified our problem – now it’s time to start strategizing our approach to find a solution!

Choosing Your Equipment: Analyzing Possible Approaches

Having clearly defined the problem, Lara would next consider her resources. Depending on the nature of her quest, she might need climbing gear, weapons, puzzle-solving tools, or even a trusty friend. In the same way, the next step in problem-solving is to consider what resources and approaches are available to tackle the problem.

At this stage, it’s important to think creatively and consider multiple possible approaches. For example, when looking to automate a data ETL (Extract, Transform, Load) process, you might consider custom code to enable automation, a simpler process using a tool like Power Automate, or leveraging something more robust like Azure Data Factory. You might also consider whether to handle the automation in-house or whether to bring in external consultants or software solutions.

Analyzing possible approaches involves not only considering their effectiveness in addressing the problem but also the resources they require. An expert ‘archaeologist’ wouldn’t carry an unnecessarily heavy load of equipment through perilous terrains if a lighter, simpler toolkit would do the job. Likewise, an organization shouldn’t invest in a complex and expensive solution if a simpler, more cost-effective approach would be equally effective and reliable.

Additionally, it’s crucial to consider the potential impacts of each approach. Every action has consequences, and it’s important to anticipate these as best as possible. Lara might need to consider the possibility of traps or ambushes. In a business setting, these “traps” might be potential risks or downsides of a particular approach, or even what impact will be felt on surrounding processes; will other teams be impacted with work process changes? Will additional network activity or server utilization impact other systems? The list goes on, but the idea is that nothing happens in a vacuum, especially in a business setting.

It’s also essential to involve the right people early and often when exploring options. Just as Lara might consult experts or allies, it’s beneficial to involve those who understand the problem and the potential solutions. This might include IT professionals, data analysts, and stakeholders from various parts of the organization.

Now, with our metaphorical backpacks filled with the most effective tools and a clear strategy, we’re ready to dive into the implementation phase of our problem-solving quest. The stage is set, and it’s time for action!

Unearth the Solution (Test and Implement Your Approach)

Once you have explored the different paths available to you, it’s time to start testing your chosen approach to see how it fares. This step in the problem-solving process equates to Lara venturing into unexplored ruins or treacherous caves to find the coveted artifact. You’ll need to bring all your tools, wits, and dedication to bear on the task at hand.

Remember, not every venture will lead to success immediately. The agile philosophy of ‘failing fast’ holds true here; quick iterations and learnings from failure are key to navigating towards a successful solution. In practice, it’s incredibly beneficial to break the solution down into functional modules or steps. This allows you to set successful completion of each step as a milestone. Just as you wouldn’t expect to run a full marathon without training and building endurance step by step, each part of your solution deserves its attention and focus.

Consider, for example, retrieving data from an API for use in reporting. This process can be broken down into several steps: accessing the API, iterating through partial queries to build a complete data set, cleaning the data, ensuring compatibility, dropping the data into an Azure container, routing it through a pipeline in Synapse to convert the raw data into a query-able format, connecting the data to Power BI, and scheduling automated refreshes. While at a glance this task can be summarized as ‘Present data from ABC123 API in Power BI to support XYZ’, by tackling it in a modular, iterative fashion, you can spot problems as they come up and focus efforts on making incremental progress. Instead of ‘going from A to Z’ where A is the API and Z is the finished, automated solution, you give yourself room to work through A to B, B to C, and so on.

You might run into roadblocks, or the approach might not yield the expected results. In a business scenario, if the tool you’ve chosen for your automated ETL process doesn’t meet your expectations, or the custom code isn’t delivering the results you want, it’s okay to reassess and try a different approach. This modular approach to problem-solving makes it easier to identify the parts of your solution that need tweaking and those that are functioning as expected.

Once your chosen solution has been tested and refined, and you’re satisfied it will effectively address the problem, it’s time for full-scale implementation. This might involve a larger rollout of your automation solution, full deployment of your custom code, or moving ahead with an external software solution. This phase might also involve training for staff, or changes to procedures and processes to accommodate the new solution.

By the end of this stage, you’ve made your way through the treacherous caverns, navigated the deadly traps, and you’re standing in front of the artifact. But the journey isn’t over yet! Once the solution is in place, it’s important to monitor its effectiveness and be prepared to make adjustments as necessary.

Implementation and Testing: Building Your Way Out of the Tomb

When you have a promising plan, it’s time to put it into action, just as Lara Croft would delve into the depths of a tomb to unravel its secrets. The implementation stage involves building your solution and putting it to work to see how it performs. This is the ‘doing’ stage, where your problem-solving strategy meets reality.

In your professional role, implementation could be writing the script to retrieve data from an API, configuring Power Automate or Azure Data Factory, or adjusting your team’s sales strategy to address a shift in market trends. It’s putting the pieces together in the way you’ve mapped out, and turning theory into practice.

At the same time, testing is critical to make sure your solution works as intended. It’s like when Lara finds a secret lever or dilapidated rope bridge in a tomb – she wouldn’t just assume it works or trust that it won’t break. She’d pull the lever, or toss a rock onto the bridge to see what happens. Testing helps identify any flaws or oversights in your solution, and it provides an opportunity to refine and improve before full-scale implementation.

In our previous example, you might test your solution by retrieving a small set of data first, or by running a single data transfer in Power Automate. Testing in a controlled environment allows you to identify and rectify issues without impacting the broader system.

Just as Lara would tread lightly in an unexplored tomb, it’s crucial to approach implementation and testing with care. Be patient and methodical, and always be ready to learn from any missteps along the way.

Review and Optimization: Perfecting Your Adventure

Every great adventure requires reflection. For Lara Croft, this might involve replaying past events in her mind or recording them in her journal, honing her skills, and considering different tactics for the future. For you, the final stage of the problem-solving process is review and optimization. Here, you’ll take a step back to assess the effectiveness of your solution and identify opportunities for improvement.

Consider the example of automating a data ETL process. After implementing your solution, you might realize that while the system works well overall, there are certain areas that could be more efficient. Perhaps the data retrieval could be optimized, or the data cleaning process could be streamlined. In such a case, it’s back to the drawing board – but with the advantage of having a functioning solution and specific areas to improve.

It’s important to remember that problem-solving is rarely a linear process. Just as Lara might retrace her steps to uncover missed opportunities and loot, you too may need to revisit earlier stages of the process to refine your solution. This isn’t a sign of failure, but rather an integral part of iterative problem-solving.

By consistently reflecting on and optimizing your solutions, you’ll continue to grow as a problem solver, and your solutions will become increasingly effective. Remember, problem-solving isn’t just about reaching the destination – it’s about enjoying and learning from the journey.

As we wrap up our quest, I hope that this framework not only empowers you to tackle the challenges you face with renewed vigor but also transforms the way you view problem-solving. Like a great adventure, it’s a process filled with discovery, creativity, and continuous learning. So, equip yourself with these strategies, brave the tombs of problem-solving, and unleash your inner Lara Croft.

Let the adventures begin!