Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Pursuing Lagom: Finding Balance Between Extremes

Pursuing Lagom: Finding Balance Between Extremes

These days it is not uncommon to feel overwhelmed by the sheer amount of, well… everything. We seem to tackle our daily problems by adding more processes, more policies, more systems, and more work-in-process. This ends up accumulating disappointment instead of success when we don’t stop to understand what gets in our way. We don’t consider that, at least some of the time, more isn’t always better.

It’s time to bring a little balance to the workforce with the concept of lagom (lah-gom). This tiny Swedish word represents the powerful concept of “not too much, not too little, just right.” At first, the concept can seem paradoxical. How can anything other than more of those processes, policies, systems, etc. result in more desirable outcomes? But, once you give it a try, a lagom approach to work can be liberating and allow us to achieve more than we ever could through the relentless pursuit of “more.”

Julia Wester
PRO

February 26, 2019
Tweet

More Decks by Julia Wester

Other Decks in Business

Transcript

  1. @everydaykanban | @TeamLagom
    Pursuing Lagom
    Finding Balance
    Between Extremes
    #LeanAgileUS19
    Julia Wester

    Co-Founder, Lagom Solutions

    LeanAgile US, February 2019

    View Slide

  2. @everydaykanban | @TeamLagom !2 #LeanAgileUS19
    Pretty much a normal day?

    View Slide

  3. @everydaykanban | @TeamLagom !3 #LeanAgileUS19

    View Slide

  4. @everydaykanban | @TeamLagom !4 #LeanAgileUS19

    View Slide

  5. @everydaykanban | @TeamLagom !5 #LeanAgileUS19
    Inattentional Blindness

    View Slide

  6. Understanding how unintended
    consequences come about and give us
    some insight into what to do differently.
    @everydaykanban | @TeamLagom !6 #LeanAgileUS19
    Systems Thinking
    https://john-lewis-artist.deviantart.com/

    View Slide

  7. @everydaykanban | @TeamLagom !7 #LeanAgileUS19
    most
    most
    negative outcomes
    Let’s consider consequences on a spectrum…
    fewest fewer
    fewer
    where we should operate
    Start
    everything
    ASAP
    Only 1 item
    in progress
    not ideal not ideal

    View Slide

  8. @everydaykanban | @TeamLagom !8 #LeanAgileUS19

    View Slide

  9. @everydaykanban | @TeamLagom !9 #LeanAgileUS19
    I’ll tell you when I’ve
    had enough

    View Slide

  10. @everydaykanban | @TeamLagom !10 #LeanAgileUS19

    View Slide

  11. @everydaykanban | @TeamLagom !11 #LeanAgileUS19
    most
    most
    extreme extreme
    negative outcomes
    Lagom is somewhere in a spectrum between extremes,
    but not always in the middle…
    fewest fewer
    fewer
    lagom

    View Slide

  12. https://www.engadget.com/2014/04/02/spotifys-quest-for-balanced-design/
    The guiding philosophy was that of “lagom” … A
    balance between being distinctly new and modern, but
    not unfamiliar; feature rich, but not overwhelming;
    beautiful, but not over-designed.
    @everydaykanban | @TeamLagom !12 #LeanAgileUS19
    on redesigning the user experience

    View Slide

  13. The Agile Manifesto
    @everydaykanban | @TeamLagom !13
    http://agilemanifesto.org
    #LeanAgileUS19

    View Slide

  14. @everydaykanban | @TeamLagom !14
    where should you operate?
    Spectrum-Thinking is crucial to understanding Agile
    Extreme
    Extreme


    ⚠ ⚠
    No Documentation
    working software is
    our documentation
    Comprehensive
    Documentation
    Manifesto says
    left of center…
    #LeanAgileUS19

    View Slide

  15. @everydaykanban | @TeamLagom !15 #LeanAgileUS19
    Finding Lagom: An art and a science

    View Slide

  16. @everydaykanban | @TeamLagom !16 #LeanAgileUS19
    #YesAnotherCanvas (Version 1.0)
    First,
    Discovery

    View Slide

  17. @everydaykanban | @TeamLagom !17 #LeanAgileUS19
    Decision
    What decision are you
    trying to make?

    View Slide

  18. @everydaykanban | @TeamLagom !18 #LeanAgileUS19
    How much work should we have in process at once?

    View Slide

  19. @everydaykanban | @TeamLagom
    Too Little
    Too Much
    What consequences
    occur when you
    operate at this
    extreme?
    What consequences
    occur when you
    operate at this
    extreme?
    #LeanAgileUS19
    !19
    Think about the positive and negative!

    View Slide

  20. @everydaykanban | @TeamLagom !20 #LeanAgileUS19
    Lagom
    What ideal outcomes
    will happen if we have a
    well-balanced approach
    for this decision?

    View Slide

  21. Finding Lagom on a Spectrum
    @everydaykanban | @TeamLagom !21
    Extreme
    Extreme
    Signals you’re operating in
    the “Lagom Zone”





    Early Warning Signs of
    being too close to extreme
    ⚠ ⚠ Early Warning Signs of
    being too close to extreme









    Negative results
    at the extreme
    Negative results
    at the extreme
    Positive results from
    focusing on this extreme
    Positive results from
    focusing on this extreme
    ✅ ✅
















    #LeanAgileUS19
    adapted from worksheet from Troy Magennis

    View Slide

  22. @everydaykanban | @TeamLagom !22 #LeanAgileUS19
    How much work should we have in process at once?
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    View Slide

  23. @everydaykanban | @TeamLagom !23 #LeanAgileUS19
    Natural Tendency
    If left unmanaged, would
    you operate at lagom,
    too little, or too much?

    View Slide

  24. @everydaykanban | @TeamLagom !24 #LeanAgileUS19
    How much work should we have in process at once?

    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    View Slide

  25. @everydaykanban | @TeamLagom !25 #LeanAgileUS19
    How much work should we have in process at once?

    Now,
    PDSA
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    View Slide

  26. @everydaykanban | @TeamLagom !26 #LeanAgileUS19
    Hypothesis!
    What could you do to push away from
    your natural tendency towards lagom?

    View Slide

  27. @everydaykanban | @TeamLagom !27 #LeanAgileUS19
    How much work should we have in process at once?
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    Introducing a WiP limit of 20 items for the team as a whole will provide more lagom outcomes.

    View Slide

  28. @everydaykanban | @TeamLagom !28 #LeanAgileUS19
    How will you test your hypothesis? What steps will you take?
    How will you know if you are closer to lagom?
    When will you review?
    Plan - Do - Study - Act

    View Slide

  29. @everydaykanban | @TeamLagom !29 #LeanAgileUS19
    How much work should we have in process at once?
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    Introducing a WiP limit of 20 items for the team as a whole will provide more lagom outcomes.
    • 20 Item Limit; exceed only
    for stop the line events
    • Monthly metrics review: Flow
    Efficiency, Throughput, Cycle
    Time, Quality, Team Satisfaction.

    View Slide

  30. @everydaykanban | @TeamLagom !30 #LeanAgileUS19
    What do your success metrics tell you?
    Are you closer to lagom, farther away
    or the same distance?
    Plan - Do - Study - Act

    View Slide

  31. @everydaykanban | @TeamLagom !31 #LeanAgileUS19
    How much work should we have in process at once?
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    Introducing a WiP limit of 20 items for the team as a whole will provide more lagom outcomes.
    • 20 Item Limit; exceed only
    for stop the line events
    • Monthly metrics review: Flow
    Efficiency, Throughput, Cycle
    Time, Quality, Team Satisfaction.
    Keeping better pace with
    requests and reducing burnout.
    Quality is static. Adhered to WIP
    limit 60% of time.
    on the right track

    View Slide

  32. @everydaykanban | @TeamLagom !32 #LeanAgileUS19
    Do you need to tweak the plan &
    continue or make a new hypothesis?
    Plan - Do - Study - Act

    View Slide

  33. @everydaykanban | @TeamLagom !33 #LeanAgileUS19
    How much work should we have in process at once?
    • Fast delivery ✔
    • Keeping pace ✔
    • Bored People
    • Mediocre quality
    • Seen as overstaffed
    • Slow delivery
    • Not Keeping Pace
    • Team Burnout
    • Poor quality
    • No time for improvement
    • Fast delivery
    • Keeping pace
    • Team challenged, not overwhelmed
    • Low # of bugs / High Customer
    Satisfaction scores

    Introducing a WiP limit of 20 items for the team as a whole will provide more lagom outcomes.
    • 20 Item Limit; exceed only
    for stop the line events
    • Monthly metrics review: Flow
    Efficiency, Throughput, Cycle
    Time, Quality, Team Satisfaction.
    Keeping better pace with
    requests and reducing burnout.
    Quality is static. Adhered to WIP
    limit 60% of time.
    on the right track
    Reduce WiP Limit to 15 until we
    can reduce stop the line events.
    Check in 30d.

    View Slide

  34. @everydaykanban | @TeamLagom !34 #LeanAgileUS19
    Celebrate!

    View Slide

  35. @everydaykanban | @TeamLagom !35 #LeanAgileUS19
    Work to
    maintain
    Lagom

    View Slide

  36. @everydaykanban | @TeamLagom !36 #LeanAgileUS19
    Bringing it all
    together

    View Slide

  37. Drucker’s Law
    You will achieve the greatest results
    in business and career if you 

    drop the word “achievement” 

    from your vocabulary and 

    replace it with “contribution”.
    @everydaykanban | @TeamLagom !37 #LeanAgileUS19

    View Slide

  38. @everydaykanban | @TeamLagom !38 #LeanAgileUS19
    [email protected]
    @everydaykanban & @TeamLagom
    https://lagom.solutions
    http://everydaykanban.com
    https://www.linkedin.com/in/juliawester/
    Contact me to talk more

    View Slide