Design Thinking for Business Innovation — Lesson 4: User Testing, Learning Loops, Business Value, Experiment Roadmaps, Storytelling, and Adoption

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing prototype testing and learning loops.
• Perform and validate business value, storytelling, and adoption using reviewable system evidence.
• Evaluate the condition where a promising idea advances because senior stakeholders prefer it even though user evidence and prototype tests reveal unresolved needs and select proportionate corrective action.

Detailed Topics

• User Testing applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Learning Loops applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Business Value applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Experiment Roadmaps applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Storytelling applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Adoption applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a cross-functional team redesigning a frustrating business process around real user needs and measurable outcomes. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the design-thinking research, prototype, and innovation decision portfolio. It also tests the exception where a promising idea advances because senior stakeholders prefer it even though user evidence and prototype tests reveal unresolved needs.

Hands-On Exercise

Complete a controlled SAP exercise covering User Testing, Learning Loops, Business Value, Experiment Roadmaps, Storytelling, and Adoption and preserve the verified result in the design-thinking research, prototype, and innovation decision portfolio.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences prototype testing and learning loops.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the design-thinking research, prototype, and innovation decision portfolio should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “a promising idea advances because senior stakeholders prefer it even though user evidence and prototype tests reveal unresolved needs” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The design-thinking research, prototype, and innovation decision portfolio connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply User Testing, Learning Loops, Business Value, Experiment Roadmaps, Storytelling, and Adoption, explain the resulting SAP behavior, and defend the outcome through the design-thinking research, prototype, and innovation decision portfolio.