An industry-agnostic L1-L2-L3 framework for decomposing complex processes and problem landscapes into actionable issues, attaching demand and complexity data, and identifying where root-cause analysis, process redesign, automation discovery or transformation prioritization should begin.
Includes a fully populated retail-banking example with 13 L1 domains, 46 L2 categories and 185 L3 issues to demonstrate how the methodology can be applied in practice.
High-level labels such as “claims,” “payments,” “billing,” “onboarding,” “order management,” “customer service” or “finance operations” are usually too broad for good process-redesign or automation decisions. The opportunity becomes actionable only when the landscape is decomposed into specific issues, volumes, complexity and problem paths.
The underlying issue-tree logic is reusable for process mapping, problem decomposition, demand analysis, root-cause structuring, automation discovery and transformation prioritization across industries and business functions. The included banking dataset is a worked example of the method, not a limitation of the framework.
A structured master dataset using L1 domains, L2 categories and L3 issues, with demand share, roll-ups, complexity, automation score, opportunity tier and recommended action. The supplied workbook is fully populated with a retail-banking example.
A browser-based explorer that loads the Excel workbook and provides domain navigation, search, filters, sorting, L1/L2/L3 score roll-ups, automation ranking and detailed issue inspection.
The framework is deliberately hierarchical so teams can move between executive-level process or demand views and individual problem statements without losing the relationship between them.
Broad process, service or problem domains such as Customer Service, Claims, Payments, Billing, Onboarding, Order Management or Operations.
More actionable issue categories that divide a broad domain into meaningful workstreams, demand types or failure modes.
Concrete issue statements that are specific enough for root-cause analysis, process mapping, automation feasibility or intervention design.
The banking example demonstrates how the method can be applied end-to-end, including demand allocation, complexity and opportunity scoring. You can replace the taxonomy with your own process, function, customer journey or industry while retaining the same structure.
The included model uses issue-volume share and a simple ease factor derived from complexity to create an automation-priority score. That helps transformation teams identify where deeper analysis should begin.
The score is deliberately an opportunity-screening mechanism, not a substitute for feasibility assessment. Issues that look attractive here should move into path-level process, API/data, risk and ROI assessment before implementation decisions are made.
Expand banking domains and categories to understand how individual customer issues sit within the larger demand structure.
Search across domains, categories, issue statements and any additional metadata loaded from the workbook.
Filter the explorer to one banking domain when a transformation workstream has a narrower scope.
Surface high-volume issues, automation-priority candidates or complex problem areas for further review.
The explorer aggregates issue volume, automation score and weighted complexity at domain and category level.
Select an L3 issue to see its full path, volume, complexity, automation score, tier, recommended action and additional Excel metadata.
A good issue tree is not merely a reporting taxonomy. It should create a common problem language across operations, transformation, digital, technology and analytics teams so that demand can be measured, root causes can be investigated and interventions can be matched to the right level of the problem.
Teams should know what each issue includes and excludes so volume data and analysis remain comparable.
L3 issues should be specific enough that teams can investigate workflow, policy, system and customer-experience causes.
Volume should roll from individual issues to categories and domains so leaders can see both concentration and detail.
The issue tree should tell you where to investigate first; deeper feasibility work should determine what should actually be automated or redesigned.
The included workbook provides a banking customer-service starting point. Adapt L1, L2 and L3 definitions to reflect the target operation.
Check that issue definitions reflect how customers actually present problems and how the operation currently classifies demand.
Use contact-reason, CRM, speech/text analytics, case-management or operational data where available so prioritization reflects the actual environment.
Use a consistent view of complexity to distinguish simple information or status issues from multi-step, exception-heavy or judgment-intensive problems.
Open the connected HTML file, click Load / Refresh Excel and select the workbook. The explorer reads the taxonomy directly from Excel.
Focus first on high-demand, lower-complexity issues or categories with concentrated demand, then validate them through workflow and automation-feasibility analysis.
Move promising L3 issues into process mapping, automation feasibility, technology-readiness, business-case and roadmap sequencing work.
Break a broad end-to-end process into progressively more actionable problem categories before detailed workflow mapping begins.
Identify a comprehensive candidate-intent universe and distinguish high-volume simple issues from complex or exception-heavy demand.
Use L3 issues as the starting point for root-cause analysis, journey mapping and process redesign rather than treating broad categories as problems.
Prioritize where deeper feasibility assessment should begin based on demand and complexity.
Create a consistent taxonomy that can be linked to volumes, repeat demand, complaints, defects, failure points and other operational evidence.
Translate a large universe of customer problems into structured workstreams and candidate initiatives for roadmap development.
The same L1-L2-L3 structure can be applied to customer journeys, back-office processes, operational workflows, product issues, service demand or enterprise problem landscapes across industries. Replace the domain taxonomy, issue statements, demand volumes and complexity inputs while keeping the decomposition and prioritization logic intact.
The transferable principle is to create a sufficiently granular problem architecture before choosing the intervention. A high-level process tells you where the problem sits; an L3 issue tells you what must actually be understood, fixed, redesigned or automated.
An issue tree creates the bridge between broad process or performance metrics and actionable transformation design. It helps leaders see where demand is concentrated, gives cross-functional teams a common taxonomy and creates a disciplined starting point for deeper process, technology and value analysis.
I use this type of issue-tree work at the front end of process transformation, root-cause analysis, customer-service transformation, automation discovery, Conversational AI and operating-model redesign — before individual solutions are selected or roadmaps are committed.
An issue tree organizes a complex process, problem or demand landscape hierarchically, moving from broad domains to issue categories and then to specific actionable problems. This makes the landscape easier to map, measure, analyze and prioritize.
L1 is the broad service domain, L2 is the issue category within that domain, and L3 is the specific customer problem statement where deeper process or automation analysis can begin.
The included model multiplies issue-volume percentage by an ease factor based on complexity: 3 for low complexity, 2 for medium and 1 for high. The result is used as an initial opportunity-screening score.
No. It means the issue deserves early validation based on the model's demand and complexity inputs. Workflow, data/API, risk, business-rule and ROI feasibility should still be tested before implementation.
Yes. Banking is the supplied worked example. The HTML explorer reads the Excel workbook, so you can replace the L1, L2 and L3 taxonomy, volumes, complexity and metadata with your own process, function, product, service or operational problem landscape.
Yes. The issue tree can help create and validate an intent universe, identify where demand is concentrated and provide a starting point for deciding which intents should remain informational, move into guided workflows or progress to deeper transactional automation.
The issue-tree toolkit sits within a broader body of work on customer operations, process redesign, AI, automation economics and enterprise transformation.
Download the toolkit and use it to structure complex process or demand landscapes, identify priority problem areas and create a stronger starting point for root-cause analysis, process redesign, automation discovery and transformation prioritization.
