Lean vs Agile vs Design Thinking vs... YOU

Поділитися
Вставка
  • Опубліковано 29 чер 2024
  • In this video, I'll talk about processes and methods when it comes to product and service delivery. The book I feature is by Jeff Gothelf (the author behind one of the best books for new UX designers - Lean UX) and is called Lean vs Agile vs Design Thinking. It's a super short (just over 40 pages) book that each and every user experience designer, user researcher, developer or product manager should read through. In the video, I'll share my thoughts on each of the different methodologies based on my previous experience as well as give some suggestions on what you should focus most.
    As per usual, pick up this book and give the author kudos: amzn.to/2P8765g
    I recently also created a playlist that contains all my videos on UX portfolios here: • UX Portfolios, design ...
    🙌 If you like this video, you'll definitely like what comes next;
    SUBSCRIBE to this channel and don't forget to share, like, comment: / @vaexperience
    👕 UX design and user research themed merch by yours truly: / vaexperience
    📩 Get my latest (BEST) updates delivered to your inbox: updates.vaexperience.com/
    #vaexperience #uxdesign #userexperience 🎒 Coursera UX courses: imp.i384100.net/dakRLQ

КОМЕНТАРІ • 41

  • @chrissri
    @chrissri 4 роки тому +69

    a few points to clarify on this: anything before or after the lean framework is considered design thinking. In terms of a timeline, lean is used to prototype products in the present whereas design thinking is used to ideate & define products in the future. Example: we use a design thinking framework to figure out that a segment of drivers actually would like to purchase electric cars. Once what we are building is established, we then use a lean framework to create our MVP. So zooming out, here is what it looks like. Design ThinkingUse Lean to create MVPLaunch MVPUse Design Thinking + Lean + Agile to finalize PMF (Product Market Fit)

    • @zoeho3433
      @zoeho3433 3 роки тому +1

      Thank you for sharing!!! I am a junior service designer. It’s easy to confuse how to combine different methods in different stages of process.

    • @omarmohamed2733
      @omarmohamed2733 Рік тому +2

      This is by far the most thoughtful perception of the Ux process

  • @bodurskii
    @bodurskii 4 роки тому +6

    good review & summary, it's good to hear that in general it's all about communication and being on the same page with the team ;) no matter what approach we use, cheers!

    • @vaexperience
      @vaexperience  4 роки тому +4

      The best teams rarely use the strict definitions and work together as a squad with common goal with plenty of respect for each others expertise.

  • @MrRobotoDomo
    @MrRobotoDomo 9 місяців тому +2

    Big budget, big team, long timeline, access to resource => design thinking or ucd
    Tight budget, short timeline, less resource => lean
    Uncertain requirements, short timeline => agile
    Based on experience, any approach will work as long as you hit the desired outcomes.

  • @deckelm
    @deckelm 2 роки тому

    Great as always - the best product channel for me

  • @fingercorgi4848
    @fingercorgi4848 4 роки тому +1

    very good summary, saved me a lot of time. and very useful personal insights.

  • @margaretnicholdesign
    @margaretnicholdesign 2 роки тому +4

    So many great books recommended in this video. I'd love to see a full list of books you think every UX designer should read.

  • @rajeshm6703
    @rajeshm6703 4 місяці тому

    What I take away is that, there is a context for application of each approach. One needs to know that. Also, the question for the industry is how better to provide customer value. Then comes the discussion on tools/approaches. Thanks for tacking this subject in the video.

  • @CosinusBeta
    @CosinusBeta 4 роки тому

    Really good overview - thanks!

  • @tpelielan
    @tpelielan 5 місяців тому +1

    This was so clear and insightful! Thank you!

    • @rajeshm6703
      @rajeshm6703 4 місяці тому

      Totally agree. A clear explanation of key concepts without getting into the weeds as too much details were unneeded for this video.

  • @sabrinaafrinsimi6964
    @sabrinaafrinsimi6964 Місяць тому

    this is very helpful, thanks for sharing.

  • @mujahidomer7071
    @mujahidomer7071 2 роки тому

    Agree with you.
    Thanks for this!

  • @MustafaSheikh
    @MustafaSheikh Рік тому +1

    Totally agree with that.
    I do "Lean Agile Thinking"

  • @maryshipulina6733
    @maryshipulina6733 3 роки тому

    Thanks for so short and clear explanation 🙏

  • @a1ufaso1a
    @a1ufaso1a 3 роки тому

    Thank your video was helpful 👍🏾

  • @HeavyK.
    @HeavyK. Рік тому

    Great delineations. Bought the audio book immediately under your advice. I have found these methodologies separately. And they still seem separate.
    Agile development STILL is 'mis' used to protect software engineering from being falsely accused of refusing to change. That is understandable. However, agile is used to make the software engineers' job easier. The original agile theory was to increase software-product quality. And today, product quality is far down the list of conscious goals. Today's software engineers are 90% focussed on turning in the most user-stories during a sprint. They have become accidentally removed from concerning the selve with helping to deliver happy customers. Most of today's software engineers are dimly away that they are turning stories that are actually called "USER stories".
    Engineers are measured by their speed of turning in stories. They are not measured by the quality of the users' experience nor the delivery of new business.
    And I could discuss similar problems with the other two; lean design; and design thinking.
    And I agree with you.
    People on the same mission perform best when they work from beginning to end of the mission. And everyone enjoys the rewards of succeeding.

  • @Mayaadyby.
    @Mayaadyby. 2 роки тому

    Well said! Thx

  • @jancukon
    @jancukon 3 роки тому +3

    Hi. I'm relatively newbie in ux world and I stumbled upon this video. It's a nice video that helped me understanding about various methodologies in product development. Thanks for making this video!
    I'm just curious about 1 thing in lean methodology, which is how research can be incorporated in it? Since, as far as i know, research took quite a bit of time in prior and may disrupt the velocity of the release

    • @vaexperience
      @vaexperience  3 роки тому +2

      Lean is all about experimentation with (just enough) informed decisions. Followed by continuous learning and iterations. A lot of UX designers and researchers absolute hate lean for the same reasons. But if you are a designer in the midst of agile product development you might be stuck in that rut. Ideally you'd want to do both: be exploitative enough but also nimble to implement and release then the time is right

  • @vincentaboughazale7479
    @vincentaboughazale7479 4 роки тому

    I totally agree

  • @omarcruz6326
    @omarcruz6326 3 роки тому

    Great Video 👍

  • @jerardking3416
    @jerardking3416 3 роки тому

    Outstanding 👍🏾👍🏾👍🏾

  • @mohammedthameem6360
    @mohammedthameem6360 2 роки тому

    i want that book .

  • @alvanortiz10
    @alvanortiz10 3 роки тому

    Excellent video!
    What is the difference between Lean and SAFe?

    • @vaexperience
      @vaexperience  3 роки тому +2

      SAFe is agile at a scale and ability to scale from small agile teams to larger org efforts at once. It's also a trademarked framework which in my eyes makes it repackaged crap. Agile at a scale also means heading back towards the factory worker ways of doing things with severe loss of soul.

    • @kateykaplan325
      @kateykaplan325 3 роки тому

      @@vaexperience is SAFe crap because it's trademarked?
      I think I'd rather stick with your fundamental principle that these are all essentially mindsets/perception/propositions to solutioning, and usage will largely be down to individual preferences, experience and tailoring capabilities. Apart from the ART and Solution Trains, there's nothing in SAFe that's new. Nonetheless, there's no gainsaying that the foundational principles that imbue the SAFe mindset are battle tested.

    • @vaexperience
      @vaexperience  3 роки тому +1

      Not specifically trademark is the issue, it's as you said yourself - a repurposing of other methods, frameworks, etc. but under a new name / private ownership. There's a lot of that already, and besides remarketing existing methods with new names it doesn't seem like adds much else. I might be missing a lot here though, as obviously they do have their own edge its application for bigger organizations might be it

  • @ExtraLayer
    @ExtraLayer 3 роки тому +1

    As a UX designer, I complete support we should be doing quick research and focusing on design delivery and it's evaluation but Product owner hate to hear when we say we are coming up with minimal research and will evaluate it after launch.

    • @vaexperience
      @vaexperience  3 роки тому +6

      That's pretty good problem to have! usually it's the product owners who want to skip the research! Tell them thank you and do the research :D

  • @FaridBoudissa
    @FaridBoudissa 4 роки тому +1

    What about the leadership?

    • @vaexperience
      @vaexperience  4 роки тому +1

      How do you mean?

    • @FaridBoudissa
      @FaridBoudissa 4 роки тому +1

      I mean the one who is responsible of the teams and deliveries coordination like a scrum master.

    • @toddsorenson4679
      @toddsorenson4679 3 роки тому +1

      @@FaridBoudissa @vaexperience did not touch on it in this video, but the author does in the book. Basically his recommendation for managers is the 'Going to Gemba' practice from Lean. That means getting out of your office and experiencing challenges first-hand, of your customers and your employees.

    • @FaridBoudissa
      @FaridBoudissa 3 роки тому

      ​@@toddsorenson4679 thank you for the indication, the team building and the way we work together is an important key of success of the quality continuous improvement. Steering operations, managing metrics or reports, are a good base of communication. I understand the interest of the Gemba practice to coordinate teams that don't necessarily speak the same language and how it can help, effectively.

  • @GCunu
    @GCunu 4 роки тому +1

    Hi, you said the templates are editable. After downloading them, I see they're jpgs. How do you edit jpgs, mr. genius? Why didn't you send the original (Native) files? Those should be editable.