Problem Mapping

From The Foundation for Best Practices in Machine Learning
Jump to navigation Jump to search


Hint
To view additional information and to make edit suggestions, click the individual items.

Problem Mapping

Objective
To determine and define an appropriate, feasible and solvable business problem through consideration of several interacting analyses.
Item nr. Item Name and Page Control Aim
4.1. Problem Statement & Solution Mapping

Document and define clear problem statements in terms of (i) User needs, (ii) Organisation problem, and/or (iii) Organization opportunity. Subsequently, document and define clear solutions to the problem statements, inclusive of the contextual needs and/or variants of the problem statements and/or their solutions.

To ensure Products have clear scopes to warrant (a) their effective oversight, management and execution, as well as (b) allow for the accurate evaluation of Product risks and controls.

4.2. Data Capacity Analysis

Map and document the state of the data delivery pipeline and available databases required to support the problem statements and solutions.

To (a) ensure that the data pipeline is sufficient to support Product(s) and enable the desired Outcomes; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.3. Product Definitions

Data Science Managers, Product Owners, Business Stakeholders and, when relevant, Product employees ought to collectively document and define clear Product definitions, aims, internal deliverables and outcomes.

To ensure Products have clear scopes to warrant (a) their effective oversight, management and execution, as well as (b) to allow for the accurate evaluation of Product risks and controls.

4.4. Outcomes Definitions

Document, delineate, and define clear Product Outcomes and Outcomes deliveries based on the above Product Definitions and the Problem Statement & Solution Mapping analysis, inclusive of subsequent iterations thereof.

To ensure Product(s) have clear scopes to warrant (a) their effective oversight, management and execution, as well as (b) allow for the accurate evaluation of Product risks and controls.

4.5. Product & Outcome Definitions Data & Model Metrics

Document and define the above Product and Outcome Definitions in terms of clear Model and data metrics.

To ensure Product(s) have clear scopes to warrant (a) their effective oversight, management and execution, as well as (b) to allow for the accurate evaluation of Product risks and controls.

4.6. Organisation Capacity Analysis

Document and assess whether the organisation has the requisite capacity to achieve the above Product Outcome and Product Metric Definitions given the Product Team Composition and Product Team Strengths and Skills and Data Capacity Analyses. If constraints detected, reiterate formulations of Product and/or Outcome Definitions to accommodate organisation capacity.

To (a) ensure that the Organization has sufficient capacity to support Product(s) and enable desired Outcomes; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.7. Product Scaling Analysis

Document and assess the estimated degree to which the Product can be feasibly scaled within Product Domains and the Organisation, having consideration for the Organisation Capacity Analysis.

To (a) ensure that the Organization has sufficient capacity to support the Product(s) and enable the desired Outcomes as the Product scales; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.8. Product Integration Strategy

Document and assess the processes needed to integrate and scale the Product into organisational structures based on the Organisation Capacity and Product Scaling Analyses. If constraints detected and/or integration appears unfeasible, reiterate formulations of Product and/or Outcome Definitions and/or review the Organisation Capacity and/or Product Scaling Analyses to accommodate a practical Product Integration Strategy.

To (a) ensure the Product and Outcome Definitions can be achieved within the bounds of the Organisation Capacity and Product Scaling Analyses; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.9. Product Risk Analysis

Document and assess the estimated risks associated with Product design, development, implementation, and operation, inclusive of considerations from the Product Scaling Analysis, and the Product Integration Strategy.

To (a) ensure Products have clear risk portfolios to warrant (i) their effective oversight, management and execution, as well as (ii) to allow for the accurate evaluation of Product risks and controls; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.10. Product Cost Analysis

Collaborate with Finance and purchasing to document and assess the estimated costs associated with Product design, development, implementation, and operation, inclusive of considerations from the Product Scaling Analysis, the Product Integration Strategy, and the Product Risk Analysis.

To (a) ensure a realistic project budget is provided; and (b) highlight associated risks that might occur in the Product Lifecycle.

4.11. User Experience Mapping

Document and assess the user experience and the desired experience for various user groups, when interacting with the Product (e.g. using Norman's Usability Heuristics). Consider mitigation strategies for possible negative impacts on and off platform. If gaps in user experience are detected or a need for process redesign or behavioral changes are uncovered reiterate formulations of Outcome Definition, as discussed in Section 4 - Problem Mapping, Organisation Capacity Analysis, and Product Integration Strategy to accommodate an effective user experience.

To (a) ensure an effective user experience; and (b) highlight associated risks that might occur in the Product Lifecycle.