Suite des cinq billets dédiés au MOOC ‘Du manager Agile au designer leader‘ (ou ‘From an Agile manager to a designer leader’, il est traduit en version anglaise) avec ce deuxième post consacré à la semaine 2 : ‘Digitaliser le management‘.
Vous pouvez y lire mes notes prises grâce aux vidéos, contenus textuels et quiz diffusés tout au long des 5 semaines qu’a duré le MOOC.
Ce premier post correspond donc à la semaine 1, avec pour sujet : ‘Le métier de manager‘.
What is interesting here is that it gives an introduction to the Six Sigma methodology, without going into (annoying) detail. On the contrary, these short notices invite reader to know more, especially about tools and real use cases.
Here are some notes I took when reading this course material.
Have you already my post about ‘ What is UX? What are UX Research and Design? ‘? Or maybe you know what is User Experience, so you read first this overview of ‘ Methods of UX Research ‘. This third post complete notes I took during the MOOC ‘ Introduction to User Experience ‘ delivered by the edX platform. We focus there on the methods to produce a plan or a prototype of what will be the final product or outcome.
There is also a quiz with 10 questions to assess your knowledge about this topic.
Further to my previous post “What is UX? What are UX Research and Design?“, here are some notes about the second part of the MOOC “Introduction to User Experience” featured by the edX platform. This post introduces some methods of UX Research, like User testing and Micro-usability test. There is also a quiz with 10 questions to assess your knowledge about this topic.
Because I used to attend some MOOCs for several years now, like ‘Learn HTML5 from W3C‘ or ‘Development with Android‘, and also because I have a strong interest in User Experience, I would not have missed this ‘Introduction to User Experience‘ featured by the great edX platform.
You will find my notes through three blog posts; here is the first part: What is UX? What are UX Research and Design?
There is also a link to a 9-questions quiz at the end of the post.
When talking about Agile, Scrum and Kanban are among the most notorious frameworks. One used to hear: “I want to do Agile, let’s perform Scrum or Kanban”. Because they distinctly bring added-value to specific contexts, this is relevant to keep in mind their very own particularities.
When facing with end-users issues, some cases do not really require bringing a ‘technical’ or even a functional solution. Indeed, the key is often to let users talking and expressing their concern. Actually, they need to be listened by someone they consider as “expert”, and they need to be listened carefully.
The simple fact to describe their trouble actually solves a large part of the situation; sometimes it even solves at 100%. Because when users talk about trouble they are facing, they realize:
- either they realize they know the solution, but they have requested for support too quickly. Typically, emergency obscures clear mind.
- either they did not diagnose correctly the problem. Their explanations are a little bit confusing, so they rephrase, they ask (to themselves) new questions. Usually, this sudden brainstorming ends up with new insights that bring them the solution.
Providing support is as acting as a coach, it means having the attitude that helps users getting a solution on their own.
In a short, “active listening” is the key: listening carefully, asking relevant questions at the right moment will conduct users to solve an issue by themselves.
Some days ago, a colleague told me:
– « Some people in my department run a daily meeting of one hour, sometimes even more. No agenda, barely some actions to be taken, only debating about ideas. »
– (Me): « Why do not they use Scrum approach and especially the Daily Stand-up meeting? »
– « This would be the same problem, daily meeting is not useful. This is better to do meeting when necessary. »
– « A short (and timeboxed) meeting is very useful », here is why…
The Daily Stand-up meeting (DS) must be done in 15 minutes maximum and involve maximum 9 people. It is a mandatory components of Scrum framework and is very enriching and useful for these reasons:
More and more professionals use collaborative digital solutions to perform their daily work: intranet, wikis, blogs, shared documents, internal social media.
A high number of ‘active’ users (readers and contributors) combined with an important volume of data require reliable, maintainable and scalable system. When it comes to upgrade it with major changes, how to keep providing a satisfying User Experience to all end-users?