How to Effectively Use the TOSCA Framework for Problem-Solving
Written on
Chapter 1: The Importance of Problem-Solving Skills
How proficient are you in solving problems? This skill is often undervalued, yet it ranks as the second most critical competency, as highlighted in a Harvard Business Review survey of 300,000 managers. Interestingly, IQ only accounts for about 20% of the variance in one's problem-solving effectiveness. These findings indicate that the ability to solve problems will become increasingly vital in both professional and personal contexts.
Defining Problem-Solving Skills
When I refer to problem-solving skills, I mean the capability to systematically apply approaches across various fields to generate effective solutions. During my university years, I was fortunate enough to take a comprehensive course on systematic problem-solving, led by a senior partner from McKinsey Management Consulting. That experience was invaluable.
Throughout my career as an engineer, entrepreneur, consultant, and manager, I have developed a passion for problem-solving. A crucial element of this process is articulating the problem accurately, which I will elaborate on in this article. If I cannot express the problem clearly, I likely do not understand it well enough.
Understanding the TOSCA Framework
So how do I approach defining a problem? The answer lies in the TOSCA framework, which stands for Trouble, Owner, Success, Constraints, and Actors.
Trouble
The "trouble" represents the symptom rather than the actual problem. It is the gap between the current state and a desired future state, initiating our problem-solving journey. For instance, while advising a web agency owner, I noticed their revenue stagnation despite a goal of 20% annual growth. This discrepancy is the trouble that needs precise definition.
To effectively define the problem, it's crucial to avoid jumping to conclusions and to ask open-ended questions:
- What are your goals?
- What have you attempted so far?
- Why didn't those efforts succeed?
- What else might be relevant?
Being specific is key. A vague statement like "We need to be more customer-focused" isn't a problem. In contrast, "10% of our customers discontinue service after one year" is a tangible issue I can address.
Owner
Determining who owns the problem is vital. While the owner can often be obvious, it isn't always the case. It might be an individual or a group. Identifying the owner allows for critical discussions on their goals. For example, in the web agency scenario, the CEO is the primary owner of the issue.
Success
It's essential to know the goal of the problem-solving effort to measure success later. I achieve this by asking specific questions:
Imagine we have successfully resolved this issue. What does that future look like?
For example, when consulting with the agency's CEO, I would ask:
- What date are we looking at in the future?
- What changes do you observe?
- How will you measure success?
In this case, the CEO might envision a future where customer retention is high, leading to a surge in positive reviews and revenue growth.
Constraints
Understanding the limitations surrounding the problem is crucial. I typically examine three dimensions of constraints:
- Success Criteria Constraints - Often, there are conflicting goals to balance.
- Solution Constraints - What solutions are not viable due to resource limitations?
- Process Constraints - Are there limitations on whom I can consult or how long I have to solve the problem?
Identifying these constraints early on can prevent frustrating iterations later.
Actors
Lastly, recognizing the various stakeholders is essential. These actors often have different objectives and can either aid or hinder problem-solving efforts. Mapping out power dynamics can help clarify support and resistance levels among stakeholders.
...
Chapter 2: Crafting the Core Problem Statement
After thoroughly exploring the TOSCA components, I consolidate my insights into a core problem statement. This involves deciding whether to frame the question as open or closed, which significantly influences the potential solutions available.
For instance, consider:
- "How can we increase our revenue?" (open)
- "Should we hire quality consultants to enhance customer satisfaction?" (closed)
In general, a broader question is preferable when addressing significant problems early in the process.
When crafting the core question, I use a checklist:
- Does it address the trouble?
- Is it framed from the owner's perspective?
- Will it facilitate achieving the defined success?
- Does it account for existing constraints?
- Is it scoped to include various actors?
A potential core question for the web agency might be:
"How can we achieve a 20% revenue increase while also enhancing customer satisfaction by 30%, without hiring new staff and maintaining current profitability within two years?"
Final Thoughts
There is no single correct method for defining a problem, but numerous incorrect approaches exist. As Albert Einstein famously said, "If I had an hour to solve a problem, I would spend 55 minutes thinking about the problem and five minutes thinking about solutions."
Employing the TOSCA framework allows me to analyze the problem from multiple angles, ensuring I address the right issues effectively. Remember, problem definition is an iterative process that involves:
- Engaging with stakeholders
- Conducting interviews
- Integrating diverse perspectives
- Regularly reassessing the core question
A well-defined problem is halfway to a solution. What is your next significant question to tackle?
For further insights like these, consider subscribing to my newsletter, Lead & Succeed!
The first video provides a beginner's guide to the TOSCA framework, illustrating common errors and solutions to enhance your problem-solving skills.
The second video offers top tips for leveraging TOSCA structure, emphasizing optimization techniques that can improve your problem-solving capabilities.