Integrating Design Thinking, Lean, Agile, and DevOps: A Value‑Driven Approach

Design thinking, lean, agile, and DevOps have become popular topics in the Chinese IT field in recent years, accompanied by debates about their relative merits. After a series of studies and practice, I have formed some thoughts on the relationships among the four and how they can be combined, which I share here for feedback.

1. Conceptual Overview

1.1 Design Thinking

“Design Thinking (DT) is a human‑centered innovation method distilled from designers’ accumulated methods and tools, integrating human needs, technical feasibility, and business success.”

— Tim Brown, CEO of IDEO

1.2 Lean Thinking

Lean thinking can be summarized in five principles: precisely define the value of a specific product; identify the value stream for each product; keep the value flowing without interruption; let the customer pull value from the producer; and continuously pursue perfection.

— “Lean Thinking” by James P. Womack and Daniel T. Jones

The key starting point of lean thinking is value, and value can only be determined by the ultimate customer.

— “Lean Thinking” by James P. Womack, Daniel T. Jones

1.3 Agile Development

Our top priority is to satisfy customers by delivering valuable software as early and continuously as possible.

— “Agile Manifesto 12 Principles”

The professional goal of every software developer and team is to deliver the maximum possible value to their employer and customers.

— “Agile Software Development: Principles, Patterns, and Practices” by Robert C. Martin

1.4 DevOps

DevOps is a cultural movement that changes how individuals think about their work, values the diversity of tasks, and supports accelerating the delivery of value while measuring the impact of social and technical changes.

— “Effective DevOps” by Jennifer Davis and Ryn Daniels

2. Common Goal of the Four

Although each framework has its own focus, all are driven by user needs and aim to achieve frequent, small‑batch, and flexible value delivery through systematic cultural, organizational, and methodological improvements.

3. Combined Application

3.1 Define Value

First, identify target users based on corporate strategy and apply design thinking to empathize deeply with them, establishing value hypotheses through reasoning and validation.

1) Empathize with target users: conduct interviews, observations, and experiences to capture behaviors, stories, and emotions.

2) Organize empathy data into user personas.

3) Infer user journeys from the empathy data, identify opportunity points driven by user needs, and define value hypotheses.

3.2 Map the Value Stream – Lean Value‑Stream Diagram

After defining value, use systems thinking and a lean value‑stream map to trace the process from user need to value delivery, analyzing activities such as value creation, verification, and hand‑off, and drawing the current value‑stream diagram.

3.3 Value‑Stream Analysis – Value Quadrants

Using the value‑quadrant tool, the current value‑stream is classified into four quadrants: non‑necessary non‑value‑adding, non‑necessary value‑adding, necessary non‑value‑adding, and necessary and value‑adding.

3.3.1 Non‑necessary non‑value‑adding activities – essentially waste, which should be eliminated.

3.3.2 Non‑necessary value‑adding activities – lower priority, can be ignored for now.

The focus is on the remaining two categories.

3.3.3 Necessary and value‑adding activities – such as requirement gathering, definition, planning, and coding; these create value and should be supported by empowering knowledge workers (e.g., SAFe principle 8).

At the team level, form full‑functional agile teams, define roles, artifacts, and ceremonies to foster self‑organization, achieve shared value definition, consensus, and creation.

3.3.4 Necessary but non‑value‑adding activities – such as testing and building; they do not add direct value but are essential for verification. Automation can free human resources to focus on creative value work.

4. Automation and Integrated Platform to Accelerate Value Flow

1. Select automation tools.

2. Connect tools to form a toolchain.

3. Trigger pipelines automatically at each state node.

4. Standardize, modularize, and enhance extensibility to build a DevOps platform.

5. Create an end‑to‑end value‑delivery process via an integrated platform.

6. Break down functional silos, reduce collaboration costs, and improve efficiency.

7. Automatically extract data from each stage and provide a unified visual metric view.

8. Present layered data to support decision‑making for managers at all levels.

5. Platform Fusion Forms an End‑to‑End Lean Value Chain

The DevOps platform further integrates with human‑resource and financial management platforms under the IT4IT philosophy, linking company assets to support continuous improvement, portfolio management, and strategic goal achievement.

6. Closing Remarks

Each framework—design thinking, lean, agile, and DevOps—has its own focus and unique practices, yet they complement each other around the shared goal of delivering customer value. The views expressed here are personal reflections; feedback and discussion are welcome. The tools mentioned are illustrative, not exhaustive. Thank you for reading!