Відео

Thank you for sharing your story and experience, I really learned a lot.

Very interesting and informative. Thanks

Insightful video! Hello from Port Harcourt Nigeria. Learning Green Digital Skills!

Wow, the speakers did an amazing work on the topics . Thank you Tobi, I felt like I was in a physical speaking event and you were so detailed . Weldone 🎉

Hello, thanks for sharing. I'm currently studying Green Digital Skills in Cameroon.

Hi. I am learning on Green Digital skills. Greetings from Nigeria.

Thank you so much for this and providing examples. This helps me understand better.

Wow what an incredible presentation! Accessibility and Inclusivity are so important, and I can't wait to learn more! Thank you! :)

Hello, greetings from Caracas, Venezuela. Very clear and insightful video. I am also in the Green Digital skills course. As a designer, it has opened my eyes to be a more green designer. Thank you!👍💚🌎

In about 10 years the new developers will be destroying this approach saying " who make this cr**p", I personally don't like it the fanatics destroy the simplicity of the front end, before was the more simple part of a system now is a hell of libraries forcing something to be what is not, stop the micromadness please

Thank you for sharing, Greeting from Nigeria. I'm learning with Green Digital Skills.

This is awesome

thank you !

😎 *PromoSM*

Great talk and insights, I learned a lot - thank you!

Hi, I'm here learning with Green Digital Skills! Greetings from Peru! Neat and tidy presentation... 😎👍

Such a great presentation that introduces OOUX in a really UNCOMPLICATED way! This is a must watch!

I see that it is normal to invade other countries and then be invited to do tech talks with westerns. Hypocrisy.

This is a brilliant talk, full of valuable advice and a practical approach.

I am just watching this today. Your storytelling was sweet and your explanation of concepts was really simple.

Ótimo vídeo

michael scott?? that you?

Had to emmit the like

This really isn't Participatory Design. The slide about what PD is and is not shows a lack of understanding of PD as a methodology/approach. What was actually described are new research tools that are more user centered. This is very different from PD and it lacks some core tenants around participatory methods. It looks like Uber has a lot of well-meaning people working in their leadership and research teams, but instead of engaging in true collaborative approaches in interacting with end users, Uber is really just co-opting language while designing products that have caused a loss of goodwill and harm to the relationship with end users, particularly drivers. It's sad.

I liked it as first 😀🙃

I was already using the template, really like answer that the journeys need to have a levels. We cannot expect one Journey to cover everything

Thank you! This was very insightful and no, you didn't put everyone to sleep 😅

Thanks UXDX for creating such a great informative video on participatory design....It's Magnificent...!

Great and enjoyable speech. Leaving with insights and smile 😊

Time codes with short Q&A's: 0:48 Q: Marty, what you define as Discovery? A: We need to come up with a solution which is Valuable, Usable, Feasable, Viable (and Etical) 2:52 Q: What do you notice that people who do Discovery are missing? A: Addressing a Value risk ("will they buy or choose to use it?") is the hardest and its often missed by the teams 5:15 Q: Difference between Features Teams and Empowered Product Teams? A: Features Teams are given features to build, Empowered Product Teams are given real problems to solve 6:25 Q: Could you explain dealing with uncertainty, learning, outcomes and failing more than 50% of the time? A: (1) In Discovery most of the time you learn, and most of the time you learn that your your idea is not a great idea (2) But the point is not to learn, the point is to solve the problem that's why when we learn why our idea doesn't work, we learn what we can do to fix that, (3) Discovery is about figuring out if it worth building in hours and days rather than weeks and months 10:18 Q: How much should Developers get involved in Discovery? A: Every day. But a few minutes a day. And we often don't need every developer, but at least Sr. or Tech Lead to be involved daily. What they to do is to play up to 15 minutes with the prototype every day (because a new prototype is every day) and answer 2 questions: (1) is anything that in prototype that makes them nervous from technical feasibility point of view, is there anything that we don't know how to do, does it imply any changes to the legacy system? (2) do they see any better way of solving this problem solved by a prototype? 13:08 Q: Any thoughts on "Shape Up" book? A: I haven't read that book yet, but I will. As a principle it's bad when 2 different groups work on the product: one for Discovery, another for Delivery. It has to be 1 and the same group 14:42 Q: How do we track the effectiveness of Discovery? If we don't track effectiveness, then what do we track? A: No track except: are we solving the problem? And we know that by business results. 17:35 Q: Any recommendations for the team starting Discovery? A: Discovery is not the phase and Delivery is not the phase. We Discover and Deliver all the time. But what we do inside are different techniques. Book "Inspired" for example lists a number of them 19:35 Q: Explain a role of Design and Development in addressing Viability risk? A: They don't. Product Manager does. Designers address Usability risks and Developers address Fasibility risks. Product Manager addresses Value and Viability risks, working with different stakeholders, showing them prototype to make sure they have no issues with that 21:25 Q: How Product Managers gain the experience to be able to do their jobs on Discovery? A: They have to understand Product Strategy, the Vision. Usually it takes up to 3 months for a Product Manager to get at the speed of the company to make good decisions and this includes: (1) really get to know Users and Customers (how do they make a purchase decision, what is the dynamics of the business, etc), (2) learn the Business with all the stakeholders and what their concerns are, (3) learn the Data to know how the product is actually used, (4) learn the Industry (competitive landscape, enabling technologies and trends, etc.) 24:05 Q: Isn't that too much for a person? A: First of all, Product Manager of an Empowered Product Team is not the same as so called "Product Manager" of Features Team. In Features Team it's usually a Project Manager. Anyway, doing great products is not a trivial thing and it takes real skills. And these are 3 skills we need in. 27:02 Q: How do you split time between Discovery and Delivery? How do you know if this is enough? A: We need to use judgment. Every situation has different risk profile. And addressing those risks of Value, Viability, Feasibility and Usability what the consequence if we mess up? If we mess up and can deliver a fix tomorrow, then not a big deal. If we mess up and the company'll loose millions of dollars or will be at legal risk, will be sued, that's a big deal. So, Product Manager, Designer and Tech Lead decide: do we have enough evidence that it worth building? 30:24 Q: What is the best way of mentoring Product Managers? Is this coaching or what? A: The single biggest problem in the industry right now is that there are not enough managers that are skilled and motivated enough to do the proper coaching. I had coaching for the first 10 years of my career: every single day there was at least 1 manager was assigned to get me better at my job. But most people I meet today have never had real coaching. The issue is weak leaders in Product Management, Product Design and Engineering. 32:17 Q: Is this your role, Marty? A: Yes and I also know a dozen Discovery Coaches who teach teams to do the Discovery. But those Design Coaches must have experience of working in the best technology companies and seen it done well. For example, if you join Google as a Product Manager it takes 2 years of real coaching before you get to the state you need to be 33:47 Q: Can you recommend anyone to follow in such coaching? A: Teresa Torres, Melissa Perry, Petra Willie 35:35 Q: Looks like Discovery is great for B2C. Have any recommendations for B2B? A: As to me B2B is easier to good work than in B2C. The main difference is traffic. As a startup B2C has more traffic than B2B. For B2B we usually use qualitative techniques. And my favorite is Customer Discovery Program Technique. I tell about it in "Inspired" book as well 37:33 Q: Any words about your books? A: "Inspired" is for Product Teams and it's about how the best teams work. And as I found that many companies don't allow their teams to work this way. So, I wrote "Empowered" to help those leaders to understand how to change, to start working as the best

Amen

Nu am urmărit tot spiel-ul, dar sper să o fac altă dată. Pe mine mă durea întotdeauna capul când trebuia să vorbesc în l. engleză cu clienții nemți 🙂. Dar asta a trecut. Supărarea mea cea mai mare este idioata „romglish”. Nu știu dacă va mai veni vreodată o vreme când o să ne fie cald sau frig în loc să suferim de „disconfort termic” !@#$%^ ! În altă ordine de idei, aveți un accent englezesc superb. Mi se pare însă mai degrabă american, decât britanic. Numai bine!

Good stuff, thanks for sharing.

First time I see you speak about work QB. Youre indeed a geek 😊

GREAT stuff!

Really interesting. I'm the lead of a service experience design team at the leading bank in Peru. This was very useful to come up with ideas on how to increase the value we deliver to business people and designers from other disciplines. Thanks!!

Instructional designer and professor of practice here from University of Arizona: excellent video. Especially when looking at Quality Matters review under Specific Review Standard 8.3 Appreciate the explanations!

I appreciate this video a lot.

Tom Segura has really changed his content.

Thanks

Thank you very much, Claire! It´s been very interesting and inspiring listening to you.

Live how passionate Claire is about all this info that she is sharing with us. It is lovely when someone finds a life purpose and builds on it - a better future for all. Truly inspiring!!

Man, the audio is really messed up for this video! Seems like attenuation or normalization settings are way off or that the mic volume is under control of a misconfigured PiD controller that is oscillating all crazy or something? 😢

FANTASTIC SESSION

thanks for sharing thoughts

That reminds me the situation from series "the Good Place" where they were "calculating" good and bad behaviors and these "good ones" were cousing a lot more damage than assumed at the beginning

The talk mentioned collaborations with OpenAI. When we talk about health data ownership, it would be critical to consider AI models trained on health data. We may revoke our permission to share data with a certain party, but how would that impact trained AI models? Would models need to 'untrain' those data points from its model? That seems unworkable. Similarly, having such control over seems fantastic from a data privacy point of view, but it would complicate health research based on large datasets. Would we have to constantly be logging in every day to give permission to have our data used in large clinical studies? Will this have a similar effect as countries that have explicit and implicit consent? Countries that require consent have far lower rates of people willing to be a donor.

Is it possible to get the slides to this presentation? Thanks.