Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

3. Techniques

3.15 Problem Shaping and Reframing

Guide to Business Data Analytics

3.15.1 Purpose

Problem shaping and reframing are creative applications of problem analysis techniques that result in alternative formulation of the problem faced by an organization. Problem shaping specifically requires refining the problem to a state where a solution process can be applied. Problem reframing refers to re-stating the problem in a different context. Both techniques are interdependent and allow deeper problem analysis leading to simpler or more creative solutions to the problem.
3.15.2 Description

When conducting data related investigation and analysis, there may be a predisposition to review the available data without giving enough attention to the problem. The process followed by data analytics teams may be scientific, comprehensive, and technologically advanced, but may not validate whether the right business problem is being solved. Problem reshaping and reframing helps in understanding the problem from different viewpoints and contexts so that the real business problem or more concrete sub-problems can be uncovered.

Many root cause analysis techniques used during problem analysis are reductive in nature, for example 5 Whys and Fishbone (Ishikawa). These elaborate the business context in which the techniques should be applied, while iteratively developing a detailed understanding of the underlying causes. While such analysis is useful to narrow down the problem, a completely alternate framing of the problem may enable better or easier solutions.

Both problem shaping and reframing require the application of critical thinking and logical deductions that are best explained through examples. Consider a health insurer trying to fix the premium amount for health insurance products:

3.15.2-Description.jpg


Reframing a problem through a change in the context in which the problem is studied often leads to an alternate understanding of the problem and additional new ways to solve it. In this example, changing the perspective from how the insurer views the problem, to considering the customer perspective that includes the customer lifestyle, demographics, medical history, and so forth.
3.15.3 Elements
 
.1    Problem Frame and Context

Context refers to the circumstances that influence, are influenced by, and provide understanding of the problem or the solution. The problem is typically analyzed within a context of industry, perceptions, assumptions, best practices, processes, goals, regulations, and any other element that influences the problem or the solution.

When shaping a problem, context is analyzed with additional focus on the problem’s symptoms, root causes, constraints, risks, and so on. The underlying context is consciously challenged for problem reframing. As a result, assumptions, perceptions, and business goals may need to be restated.

.2    Problem Statement

The original problem, reshaped problem, or reframed problem is clearly stated and documented. A well-documented problem eliminates any ambiguity in stakeholder perception of the problem and allows focus on the real problem. The problem statement ensures that enough ownership is attributed to respective stakeholders affected by the problem.

A typical reframed or reshaped problem statement may be formed in the following way:

  • Problem statement: key statements describing the problem or the opportunity.
  • Impacted stakeholders: stakeholders impacted or influenced by the problem.
  • High level description of the solution or key needs: for a business data analytics problem, it may contain the analytics approach, required data, and the type of analytics problem (for example, descriptive, predictive, or prescriptive).
  • Comparison to an alternative formulation of the problem.
3.15.4 Usage Considerations

.1    Strengths

  • Provides a robust analysis of the problem context so that business data analytics engagements are aligned to business objectives.
  • Provides an outsider view of the problem, which attracts new and fresh solution approaches.
  • Can uncover new data sources that may be needed for analysis.
  • Can uncover non-analytics solutions to the problem, which might be simpler or more feasible.
.2    Limitations

  • It can create potential conflicts with stakeholder perception of the problem. It is crucial that the data analytics team gets buy-in from key stakeholders.
  • It is limited to individual creativity and knowledge while reshaping or reframing the problem. This can be addressed by conducting a group exercise, preferably through brainstorming sessions or stakeholder workshops.
  • It may ignore the data cues from previous analysis or introduce the personal bias of influential stakeholder.