DEV Community: Atul

Stop asking users to introspect their behaviors

Atul — Thu, 22 Oct 2020 16:23:17 +0000

People like to think that their decisions are rational and made with deliberate thought.

But, in reality, people are very bad at introspecting their behaviors & decisions.

People want to tell a good story—a “narrative”—of their life and will change what they say to fit the view of who they are and to whom they are talking.

Instead of asking people to examine the reason behind their behavior, we should run experiments where we can observe them & find how they are currently solving their problem. We try to map their needs, goals, and pain points, typically in their home/ where the action happens.

Don’t just listen to what users say they do. See what they do while they do it.

You call it writer's block. Professionals call it writing.

Atul — Fri, 09 Oct 2020 16:36:21 +0000

The writer’s block is not real.

When you can’t lift a weight at the gym, you don’t say you’ve got a lifter’s block. The weight is just heavy.

So, you start by lifting weights that are just slightly above your ability, so that you provide your muscles enough stress for it to grow stronger; and you slowly move up from there.

It’s the same with writing. Writing is a muscle.

The only difference is – sometimes, your writing sessions feelings effortless. Like the muse is passing right through you/ You are able to write exactly what you are thinking, just the way you want it. You are in that “zone” like all the real writers are, right?

The concept of “being in the zone” has killed more aspiring writers. than anything else. You think if you were any good at writing, every session should be like this.

But the reality is, that happens only 5% of the time. The other 95% of the time, you just sit on your chair & bleed.

That’s what turning pro is – it means you ship.

Every professional writer will confirm this.

Here’s the thing — What you are calling writer’s block, that’s what professional writers call writing.

Madness of David Lynch

Atul — Wed, 30 Sep 2020 15:43:59 +0000

David Lynch is one of the best filmmakers of this time. I watched the Twin Peaks series early this year and it still makes my heads turn. It’s his masterpiece.

Today, I stumbled upon this beautiful video showing the madness behind the screen. Here are some lines that caught my attention:

On getting ideas & embracing boredom

“Ideas are so beautiful and they’re so abstract. And they do exist someplace. I don’t know if there’s a name for it. And I think they exist, like fish. And I believe that if you sit quietly, like you’re fishing, you will catch ideas. The real, you know, beautiful, big ones swim kinda deep down there so you have to be very quiet, and you know, wait for them to come along. …

Never let good ideas go to waste.

If you catch an idea, you know, any idea, it wasn’t there and then it’s there! It might just be a small fragment, of, like I say, a feature film or a song of a lyric or whatever, but you gotta write that idea down right away. And as you’re writing, sometimes it’s amazing how much comes out, you know, from that one flash…

Listening to the muse

So, you get an idea and it is like a seed. And in your mind the idea is seen and felt and it explodes like it’s got electricity and light connected to it. And it has all the images and the feeling. And it’s like in an instant you know the idea, in an instant…

Sharing your idea with the world

Then, the thing is translating that to some medium. It could be a film idea or a painting idea or a furniture idea. It doesn’t matter. It wants to be something. It’s a seed for something. So, the whole thing is translating that idea to a medium. And in the case of film, it takes a long time and you always need to go back and stay true to that idea…”

P.S. If you haven’t watched Twin Peaks series, I highly recommend it.

Think like a Detective

Atul — Sun, 27 Sep 2020 06:08:41 +0000

If you want to be a better UX Researcher, you have to start thinking like a detective.

Here is a five steps method of doing so:

Understand the problem to be solved

Questions are more intriguing. Answers tend to bring everything to a halt.

When we fixate on the solutions too early, we risk losing sight of the actual problem we were trying to solve.

It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. – Sherlock Holmes

You need to be clear about the problem you are trying to solve and create an explicit research question before you start doing any research.

Don’t assume that your problem is unique and no one has asked the same questions before. Interview the company and team about what they already know, read the background and prior research reports, synthesis it in a way that makes sense.

Leave nothing to guesswork.

Collect the facts

Opinions ≠ Facts
Speculation ≠ Evidence

Holmes primary method of collecting facts was careful observation

Observation is a key tool for UX researchers. During field visits, it can help you see the unmet user needs – often which the users can't even articulate properly or know is even there.

We approached the case, you remember, with an absolutely blank mind, which is always an advantage. We had formed no theories. We were simply there to observe. – Holmes

It's best to observe with no judgment, expectations, or prior assumptions or theories. Don't try to interpret things or try to fit things together at this stage. Start with a blank slate and don't worry about what you are noticing & capturing.

Develop a hypothesis to explain the facts

Sherlock Holmes was a specialist. He had a deep knowledge of a very narrow field. His understanding of Chemistry, footprints, bloodstains, and various poisonous flowers ( but not general gardening) was unparalleled. But, he didn't bother knowing that the Earth revolves around the Sun.

What the deuce is it to me? You say that we go round the sun. If we went round the moon it would not make a pennyworth of difference to me or to my work. – Holmes

We need to have deep knowledge of human behavior, technology advances, market trends, and our company's business goals so that we can develop strong hypotheses that best fit the facts we collect from our UX research.

Our hypothesis helps us identify the gaps in the way people work — a gap being the opportunity emerged when we compare the way something is currently being done, and the improved way it might be possible to do it in the future.

To help the team see these gaps, we need clarity on our users, their tasks, and their environment of use (Who? Doing what? Under what circumstances?)

Our models, personas, scenarios, and stories should include:
• The primary goals that people have.
• The workflow of tasks people carry out.
• The mental model's people build.
• The tools people use.
• The environments people work in.
• The terminology people use to describe what they do.

When our analysis is completed, we should have clear answers to these. This will allow us to see the gaps and the opportunities for improvement, and then, finally, we can start working on solutions.

Eliminate the Least Likely Hypotheses to Arrive at the Solution

It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth.” The Adventure of the Beryl Coronet (1892).

At this stage, if we have done our work right, we will have a number of potential design solutions, product ideas, and improvements.

Now we start eliminating the weaker solutions by asking:

Does our hypothesized solution fit the results of our investigation?

Eliminating potential solutions is a high stakes game, as the evidence for or against a solution must be compelling — it needs to be reliable, valid, and unbiased.

Experiments are our friends. It helps us test the strength of our hypotheses, ideas, and solutions. As you move into the development cycle, controlled testing should continue as an iterative process.

Act on the Solution

You have understood the problem, collected the facts, came up with potential hypotheses & solutions, eliminated the least likely hypotheses, now how do you ensure that your recommendations are carried out by the development team?

Here are a few recommendations:

Conduct a one-day UX research and design workshop to “explain what we found and how we did it” and to transition the user experience findings and solutions to the development team.
Provide the development team with specific and actionable design recommendations.
Agree on accountability for implementing your user experience recommendations.
Promote iterative design by arranging to test multiple versions of the prototype.
Create and present a clear series of next user experience steps—both tactical and strategic.
Educate the team on UX research methods.
Don’t just attend design meetings: chair them.