Design procress – the User research [research notes]

User Research

Appear in the early design process.

Not always full fledged process is deployed obviously – depend on the focus of the project, on its complexity and on its budget.



Focus on:

User research main focus is on:

  • user behaviors
  • user needs
  • motivations


Why you need it

To deliver a service that meets your users’ needs, you have to understand:

  • who your likely users are
  • what they’re trying to do
  • how they’re trying to do it now
  • how their life or work influences what they do and how
  • how they use and experience existing services



They said

Mike Kuniaysky defines it as : “the process of understanding the impact of design on an audience.”


Usability answers the question, “Can the user accomplish their goal? – Joyce Lee, Human Factors Design at Apple


If a picture is worth 1000 words, a prototype is worth 1000 meetings. – Tom & David Kelley, Creative Brothers at IDEO


Most business models have focused on self interest instead of user experience. – Tim Cook, CEO at Apple


Find what works, not what’s popular, UK Gov Guidelines


Methods & tools used :


  • Card Sorting
  • Contextual Interviews
  • First Click Testing
  • Focus Groups
  • Heuristic Evaluation
  • Individual Interviews
  • Parallel Design
  • Personas
  • Prototyping
  • Surveys
  • System Usability Scale (SUS)
  • Task Analysis
  • Usability Testing
  • Use Cases

That’s a lot of methods. Here is a diagram to know which one should be used where :


Attitude vs Behaviour is “what people say” versus “what people do”

Card sorting help understand how users think about information, which then can help building a more adapeted information architecture for the product, application, or website.

Surveys may help collect data which can help discover issues to address.

Focus groups are not very much useful for usability purposes, but is very suited for branding conversation or product concept in a group setting.


Like all research process – data is can be about quantities and can be about qualities:

Quantitative research : “how many people clicked here” or “what percentage of users are able to find the call to action?” or what is happening on a site or in an app.

Qualitative research : Stuff like : “why didn’t people see the call to action” and “what else did people notice on the page?” – Goal is to understand users motivations – why people do the things they do, and often takes the form of interviews or conversations.





User Research Basics

When to Use Which User-Experience Research Methods

Complete Beginner’s Guide to UX Research


Books :

The User Experience Team of One (Leah Buley)

The Essentials of Interaction Design (Alan Cooper, Robert Reimann, and Dave Cronin)



Right to repair – 4 videos to make you think

more people should be talking about this

Apple is working to prevent people from repairing the iphone they bought.

This is a 15 min video on a legal case where Apple lost – and is very well explained.

kudos to @RossmannGroup for it

For the record, #apple is not the only one doing that

Car companies are too.

Check this one :

Sony as well who sued George Hotz for playing around with his Playstation:

In a world where electronics are gonna be more and more fundamentals elements of our day to day life – it makes sense we pay attention that the stuff we buy belong to us (AKA the people who buy it) and not to the manufacturer.

Oh, and here is a funny addition to – the following video was released in a very similar timespan as the first one – where Apple refused to fix one of ther product, even when the customer was ready to pay for the repair.

Which I think is pretty telling…

Extra references

if you want to know more about the right to repair, check these below.

“Right to Repair” Is About a Whole Lot More Than iPhones

Research notes : Design for trust

So, here are some of my notes on designing for trust.

It is more and more important to look at design beyong its usability function and start to think about the emotional state of the user.

(Funny enough I just found a video from a designer talking about that 8 years ago… so yeah… it is really time then…)

As I was working on design principles for a project the other day – I started to dig into this concept of trust and design.

And I was pleasantly surprised (well, not that surprised… but still) to realise quite a lot of litterature out there with some interesting insights.

Crossing Africa and learning about trust

First – this 10 min on designing for trust with quite some interesting points on trust and design.

Trust – requires to give up things

Trust is made out of micro-moments of trust

The world doesnt work without trust

Environnement define the level of expected trust

AirBnB talks a lot about trust

Also some interesting articles on trust and design here :

Designing for Trust

Hospitality requieres mutual trust

Designing for friends – or as a friend.

Make the users looks like friendly people.

Add a smile.

Building for Trust

Designing for trust –

General UI/UX elements to think about


  • Design quality
  • Let your users know what is going to happen
  • Use trust indicators
  • Social proof

Pyramid of trust

Last stuff I found here from NNGroup (a known UX design group)

with the concept of pyramid of trust – which is a nice way to model the different stages of trust.

Psychology of Trust

Other stuff to review :

It’s time to design for trust! MobX Conference and UX Alive! Berlin

Machine learning : digging into recommendation system

Gotta build on of these for a complex and content rich elearning site.

So did some research.

Here are some of my findings.

Here is a good start :

How to Build a Recommender System by Martin Kihn

The Components of a Recommender System on a site with quite some articles on the topic – like this one on Impression Discounting

Or this one :

Beginners Guide to learn about Content Based Recommender Engines which is from 2015 but still cover the general basis.

Then you have some actual building – for example here in R : A recommendation system in R, applied with respect to the movielens database by Nelson Manohar who seems to specialised in machine learning based on his online profile.

Then we have an old plugin writen for WooCommerce Perso Recommendation Engine Plugin for Woocommerce which is nice to see how it is integrated in WordPress.

Then on youtube, we have quite some tutorials providing some interesting insights with some practical applications – usually movie recommendation engines.

Here we have a good intro from Standford university:

Overview of Recommender Systems | Stanford University

Then finally we can do one :

A really short tutorial (40 min total) to make a python movies recommendation system :

Recommendation Systems – Learn Python for Data Science #3

And the same guy but different stack :

Build a Movie Recommender – Machine Learning for Hackers #4

Then a different approach, with more algorithm into it :

Coding Challenge #70.1: Nearest Neighbors Recommendation Engine – Part 1

Coding Challenge #70.2: Nearest Neighbors Recommendation Engine – Part 2

Coding Challenge #70.3: Nearest Neighbors Recommendation Engine – Part 3

Then a long one of an hour+ integrating with tensor flow (the google library for deep learning) : Recommendation Systems / Engines with TensorFlow – Google Cloud Platform User Group Singapore

Probably more to come, but that’s a good start for now.

Do not hesitate to suggest stuff – either in the comment or on social somewhere

JS tooling

The web is evolving.

Here are some element to catch up on VueJs and NodeJS


Building a RESTful API with Node.js

NodeJS Shopping Cart

Vue.js 2 – Getting Started

Build a Chat Room from scratch (vuejs, nodejs,

Full Stack Web App using Vue.js & Express.js

Hotel system in Vue.js

Vue.js 2 & Vuex (Basics)

Site map vs content architecture (content map – IA)

IA – information architecture

“Structural design of shared information environments”


Site map

A site map is a list of pages of a web site.”

Source for images

Make your own Operating system


Writing your own OS – nobody does that.

That’s why it is interesting 🙂


Reference post for later.


OS general intro – pretty good.


Tutorial – Step by step




From the guy who did the 1h tutorial.

Full list :

A pretty interesting book on lecture from Birmingham university on the topic here.

Then Mike Saunders reference here: How to write a simple operating system

Erik Helin, Adam Renberg’s book :

The little book about OS development

Baking Pi – a course from Cambridge on Rasperry pi’s OS – doesn’s seem up to date but could be still relevant

Beginner Mistakes when writing your own OS :

The stackoverflow refernce :







Startup culture or HR marketing scam

Just watch the following talk…

Trends sell.

Sometime they sell bulshit.

Startup culture and entrepreneurship is trendy now.

But now always for good reasons…

cofounding and company ownership over time

Very good talk about how company founders should think about equity and capital shares.

“Founders, don’t fuck up your cap tables!” by Oussama, Founder @The Family