Agile, Have You Met Design Thinking?

In a recent blog post, Joshua Kerievsky introduces what he calls “Modern Agile”. In his words, modern agile “simplifies and streamlines traditional agile processes while making them sturdier”. Joshua presents four primary modern-agile principles:

  • Make Users Awesome
  • Make Safety a Prerequisite
  • Experiment and Learn Rapidly
  • Deliver Value Continuously

When I read the descriptions of these principles, I see a huge overlap with Design Thinking. The principle of making users awesome basically restates the importance of user-centeredness. Empathy?—?e.g., user-centeredness?—?lies at the very heart of Design Thinking.

Making safety a prerequisite emphasizes the importance of feeling safe to make mistakes. Design Thinking is fundamentally about design. Design is a creative process through which solutions are uncovered. Design Thinking actually challenges us to redefine success and failure. An interim attempt at a design that doesn’t satisfy a requirement, yet moves us towards a satisfactory solution, shouldn’t really be called a failure.

Experimenting and learning rapidly neatly captures the Design Thinking activities of iteration and user testing. The only way to validate empathy is to test how well we’ve seen our users’ perspectives. Design Thinking takes an adaptive approach, by which we incrementally validate our understanding through a circular try-test-refine feedback loop.

Delivering value continuously is one area where Agile (and DevOps too) can augment Design Thinking. The digital service economy breaks down the boundaries between design, development, and delivery. It creates the opportunity as well as the need to extend iterative user-testing beyond design, and development, all the way into operations. It challenges us to rethink business as a continuous, responsive conversation with our customers.

It is my belief that Agile, DevOps, and Design Thinking need to come together and infuse each other. Any two of them are incomplete. We need empathy, and speed, and feedback loops, at all stages of the service delivery process. Without all of them together, we will just making the industrial assembly line faster, and just overwhelm our customers more completely.

When we unify them, on the other hand, design becomes continuous. Continuous design gives us the ability to design (and operate) for complexity. In the post-industrial world, characterized by service ecosystems, digital-physical infusion, and economic disruption, nothing less will suffice.

要查看或添加评论,请登录

Jeff Sussna的更多文章

  • Cracking the Jobs to Be Done Mystery

    Cracking the Jobs to Be Done Mystery

    "Jobs to Be Done" is a powerful framework for shifting focus from product features to customer needs. Applying it…

  • How Do We Know When We're Done?

    How Do We Know When We're Done?

    More than 20 years after the Agile Manifesto was published, and more than 30 years since the introduction of Scrum…

    1 条评论
  • Rescuing DevOps (From Myself)

    Rescuing DevOps (From Myself)

    I have wasted more time than I care to admit arguing about the definition and proper use of the term "DevOps". I will…

    5 条评论
  • A Manifesto for Outcome-Driven Agile

    A Manifesto for Outcome-Driven Agile

    We are uncovering better ways of creating customer value by doing it and helping others do it. Through this work we…

    2 条评论
  • EmpathyOps: Serving Customers By Serving Each Other

    EmpathyOps: Serving Customers By Serving Each Other

    The DevOps community has been exploring the idea that DevOps is really bigger than dev and ops. If this is true (I…

    2 条评论
  • Snowballs, Jobs To Be Done, and the Four Dimensions of Service

    Snowballs, Jobs To Be Done, and the Four Dimensions of Service

    At their re:Invent user conference this year, Amazon Web Services touted their Snowball data import service. Microsoft…

  • Design Thinking In Three Words

    Design Thinking In Three Words

    There are as many definitions of design thinking as there are articles about it. Its power and its curse lie in the…

    3 条评论
  • A Better Approach to Bimodal IT

    A Better Approach to Bimodal IT

    I first encountered the ideas behind Bimodal IT about two years before Gartner coined the term. I was doing a speaking…

    1 条评论
  • Why the CIO Needs to Become the Continuous Design Officer

    Why the CIO Needs to Become the Continuous Design Officer

    I recently participated in an episode of the #c9d9 podcast hosted by Electric Cloud. The topic of discussion was the…

  • DevOps As Design

    DevOps As Design

    The DevOps movement has encountered a certain amount of criticism for not being more prescriptive. “The principles…

社区洞察

其他会员也浏览了