This deck introduces structured approaches used to analyze and solve complex problems. Learners discover how frameworks help clarify issues, identify root causes, and evaluate possible solutions. The cards explain how systematic approaches improve decision-making and reduce confusion in complex situations.
Flashcards combined with spaced repetition improve active recall. You review at the right time, retain knowledge longer, and track progress card by card.
Card 1
Describing the current gap or issue without implying a solution
Explanation
A problem statement neutrally describes the gap between current and desired states, without prescribing remedies.
Common mistake
Many people jump directly to their preferred fix and write a solution statement instead of clarifying the underlying issue.
Card 2
It specifies what is explicitly out of scope as well as in scope
Explanation
Stating both inclusions and exclusions prevents scope creep and keeps analysis tightly focused.
Common mistake
Teams often define what is included but forget to state what will not be analyzed, leading to endless expansion of work.
Card 3
Providing measurable conditions that indicate the problem has been solved
Explanation
Measurable success criteria align stakeholders on what “good” looks like and guide solution evaluation.
Common mistake
People often confuse success criteria with tasks or milestones instead of defining the end-state to achieve.
Card 4
The primary decision maker who owns the outcome
Explanation
Framing the problem around the decision maker’s needs ensures the analysis answers the right question.
Common mistake
Analysts often frame the problem around available data or vocal stakeholders instead of the true decision owner.
Card 5
It disappears temporarily when you treat it, but later comes back
Explanation
Symptoms recur if the root cause remains; durable fixes require addressing the deeper drivers.
Common mistake
Teams often celebrate quick wins on visible symptoms without checking whether the issue later reappears.
Card 6
Each branch answers a single, clearly defined question from the level above
Explanation
Issue trees break a main question into subquestions, keeping a strict logical relationship between levels.
Common mistake
People often create lists of tasks or topics instead of genuine question-driven branches.
Card 7
They should not overlap and together fully cover the whole
Explanation
MECE ensures subcomponents are mutually exclusive and collectively exhaustive, avoiding gaps and double-counting.
Common mistake
Analysts frequently create categories that overlap, causing confusion and inconsistent metrics.
Card 8
One organizes reasons or drivers; the other shows temporal workflow steps
Explanation
Logic trees decompose questions into drivers, while process maps depict sequences of activities over time.
Common mistake
Teams sometimes try to use process steps as if they were causal drivers, blurring analysis and workflow.
Card 9
Starting from the main question and iteratively breaking it into subquestions
Explanation
Top-down decomposition keeps analysis anchored to the core question, guiding which details matter.
Common mistake
Analysts often dive into data bottom-up without a guiding question, leading to unfocused exploration.
Card 10
Group closely related issues that can be investigated by one focused team
Explanation
Workstreams cluster related questions so each team can own a coherent piece of the problem.
Common mistake
Projects often mirror the org chart instead of grouping logically related analytical questions.
Create your Memia account to unlock this deck and start focused practice sessions with progress tracking.