Posts tagged “research”

Steve interviewed for “People of Research”

Thanks to Research Loop for interviewing me as part of their People of Research series. The interview is here, and I’ve reposted it below.

Big thanks for accepting the invitation, Steve, a pleasure to have you on #PeopleOfResearch interview series! Let’s start!
You have more than 19 years’ of experience, how user research changed and evolved since the beginning of your career?

When I started out, user research was primarily being done in consultancies. If you wanted to do this work, you went to work at an agency. As I progressed and people would come to me for advice, I was always sending them to Adaptive Path, frogdesign, IDEO, Jump Associates, and so on. And as we’ve collectively raised awareness of the value of research, companies have invested in building their own teams. I can’t even guess at the numbers these days, I feel like Facebook had 700 user researchers at some point? How many hundreds of user researchers do we think Google has? So when you have that kind of scale, the job opportunities are in those organizations.

It means that you have leadership roles in user research, which maybe we take for granted now, but that wasn’t always the case. That was the inspiration for me to start my podcast, Dollars to Donuts, to shine a bit of a spotlight on a relatively new role in the field of user research.

To be honest, it’s so interesting to me to speak with people inside of an organization about research and hear them talk (as you’d expect) like corporate people, people who spend all of their time inside that culture. Back in my early days, as a researcher/consultant, our job was to bring that outside in, to surface the language of the real world, not the language (and mental model) of the producer of the tool for the world. So when the person whose job it is to bring the outside in is actually part of the inside, the producer culture, they’re going to do that very, very differently. Their own professional success, their financial incentive, is tied to the performance of the company, or the product. And yet the work is about telling truth-to-power. So how I practice that as a consultant is going to differ from how someone who leads an internal team and reports to the VP of Product will. I mean, we’ve long had consultants and internal people in the world of business, but in user research, it’s still a relatively recent change.

We are living in a high speed society, therefore startups and companies work in a very agile development environment, trying to deliver products or features as quickly as possible. How can user research fit in this fast paced context?

Agreed, we’re under pressure to work quickly. And so we respond with new methods that aren’t the “best” method but that work within the constraints that others are placing on research. Teams are understaffed so this means pressure to work more quickly. We even adopt the terminology, like “sprints” which is not an effective word choice if you want to be given time to work through your process. This willing compliance with unrealistic expectations doesn’t serve the practice and it doesn’t serve us individually that well.

I see this as an issue of leadership, though, and not something that an individual researcher can impact that easily. There needs to be someone with authority, responsibility, and credibility to help the organization best utilize research. Without a peer to the leaders in (say) design, product, engineering, then researchers are relegated to taking instructions from people who may be less conversant with the operations of user research. A research leader will work proactively to understand upcoming design and product activity in order to prioritize and allocate resources so that the research that gets done is research that will have the most impact at the right time.

There are a lot of ways to learn research and juniors often feel overwhelmed and discouraged because of that. What would you tell them to do?

Practice. Do as much research as you can. Create your own practice occasions: maybe it’s that chatty person you meet in public like an extroverted cashier – ask them a question and then ask them follow up questions! Also, reflect, just like a sports team coach who reviews game films; watch your videos, read your transcripts, and look at what worked well and what you might have improved.

Take the opportunity to be interviewed yourself – whether it’s for a survey or a usability study or a poll, find an opportunity to experience the interview from the other side of the lens. Keep reflecting by observing others at work — including both great and poor interviewers in your work context, and in the media (for example, what do you think works in a particular Terry Gross interview?)

Junior researchers need guidance at the beginning of their career, what advice do you have for them?

Take advantage of all the ways you can learn more about research (meetups, articles, conferences, mentorship, discussions) but look for adjacent ways to learn. Read widely. Go to museums. Travel. Watch documentaries. Or whatever it is for you that helps you encounter ways of living, being, creating, thinking outside your own as it can inform your own research practice in surprising and joyful ways.

What qualities do you think a researcher should have?

At a fundamental level, there’s an essential inherent curiosity about people (which may be more of a leaning than a skill). There’s the ability to deeply listen. We need patience. We need to think quickly on our feet, to be in the moment and creative in how we ask questions.

There’s also something very individualistic about research. My style as a researcher is connected to my way of thinking and speaking and listening in all of my interactions and in all of my relationships. We’re all unique that way. Of course, in research we are making choices about how to express or not some of our tendencies, but there’s no perfect choice, and over time researchers can develop an authentic style that will continue to evolve with them.

But the most important thing I’ve learned about research is about myself. Research is a person-to-person activity and every time I go talk to somebody I come in with my own experiences and my own biases – my own expectations about what I’m going to see based on (for example) what the research project is about and I have had to learn to hear my own judgment. It’s actually one of my favorite things about research – that feeling you get when you discover an assumption you have made. It could be about anything. It’s just so rewarding that I feel like I am learning about the world and learning about myself because I have dismantled a presumption that I didn’t know that I had. So that keeps happening – I keep discovering my own biases, prejudices, and assumptions and so it feels like I’m always growing as a person.

Thank you again, Steve, for sharing your story and your experience, very insightful!

About #PeopleOfResearch

#PeopleOfResearch is a series of mini-interviews for the Research Loop Community where researchers all over the globe share their vision, experience and advice.

How to Grow and Thrive as A User Researcher

Check out an interview with me in How to Grow and Thrive as A User Researcher on the Adobe blog. An excerpt is below

What are the benefits of sharing career failures and mishaps rather than just successes?

We need to share both! Thinking about the field of user research, it’s important for practitioners to continue our development. Examining what went wrong (or what was different from what we expected) can highlight practices that might have avoided any particular mishap. But user research is so much about people and all their quirks, personalities, strengths, flaws, emotions, and so on — it’s what the work is about! There are inevitably surprises, and failures, and so another way to think about improving our skills is in accepting the lack of control, and even embracing it.

Researchers are often ‘selling’ the benefits of the practice to colleagues and stakeholders, and while I’m probably not going to lead with failure stories, it’s helpful to have a framework for considering them. ‘Failures’ are inevitable and while we work hard to prevent them, they are still coming for us, and reframing them as part of the messy people experience that we’re out there to embrace can help us discuss more realistically with our collaborators. There’s no reason any of us should feel alone with these experiences; as Doorbells, Danger, and Dead Batteries illustrates, they are part of this work.

Some well-known and very successful designers don’t do any user research. What do you think about that approach?

Let’s assume that’s true. It’s foolish to declare that the only way to innovate is through research. Even when we do research, there are many other factors at play that determine success. What does concern me is that approaches championed by ‘well-known and very successful’ individuals won’t succeed for everyone. It’s real swell that Steve Jobs (or substitute your favorite successful innovator) did it this way. But you’re not Steve Jobs!

Special thanks to Oliver Lindberg for the interview!

Making an Impact with UX Research Insights

I wrote a short piece for UX Mastery about ensuring the results of user interviews have the most impact. I’ve included an excerpt below, but you should read the whole piece here.

In your analysis, how do you decide what’s important?

Take time at the beginning of the research to frame the problem. Where did this research initiate? What hypotheses – often implicit ones – do stakeholders have? What business decisions will be made as a result of this research?

What research reveals doesn’t always fit into the structure that is handed to you ahead of time, so knowing what those expectations are can help you with both analysis and communication. Some things are important to understand because they’re part of the brief. But other things are going to emerge as important because as you spend time with your conclusions you realise “Oh this is the thing!”

Whose Job is User Research?

I was interviewed by Laura Klein and we discussed Whose Job is User Research?

Not every research study requires an expert at the helm. Quite a few products would benefit from having somebody on the main product team who could quickly get feedback or answers to simple questions. “Even a newbie researcher should be able to answer some factual questions about what people are doing or might want to do. They also have the opportunity to reflect on what assumptions they were holding onto that were incorrect,” Steve explains. “You’ll always get more questions to go with your answers, but hoo boy–it’s better than never talking to users and acting with confident ignorance.”There are some questions you’re better off bringing in an expert, though. “The more help you need in connecting the business problem with the research approach and connecting the observations to the business implications, the more expert help you need,” Steve explains.

Check out the whole article.

Epic FAIL: Takeaways from the War Stories project

Since 2012, I’ve been collecting War Stories, where researchers share the stuff that happens during fieldwork. There are more than 70 stories (start your reading here) and they’ve proven to be a valuable resource for the practice. I’ve been giving a talk over the past few months about the stories and what I’ve learned from the process of curating the stories as well as from the stories themselves. From UX Australia, here’s the audio, the (minimal) slides, and a few sketchnotes.

If you have a story about an experience you had doing contextual research, please get in touch! We want more stories!


To download the audio Right-Click and Save As… (Windows) or Ctrl-Click (Mac)


Matthew Magain, UX Mastery


Guillaume Hammadi

https://twitter.com/sujeevnotsteve/status/504876135193141248
Suj

Facing Your Fears: Approaching People For Research

intercept

I’ve always found intercepts – where researchers stop people on the street and ask them to participate in a quick study – to be challenging. (I also prefer to have longer interactions with people and even have them prepare for those research conversations, but that is a bit outside the point here). In Facing Your Fears: Approaching People For Research Carolyn Chandler breaks that challenge down into many pieces and addresses each of them. It’s a wonderful article because it gets deeply into the specifics and considers the mindset we bring to the activity and how to reframe that, in many different ways.

Rejection is people’s number one fear when approaching strangers. Hearing no has always been difficult, whether it’s a polite no or an angry no followed by a rant. Either way, it stings. Your response to that sting, though, is what matters. How do you explain the rejection to yourself, and does your explanation help or hurt you?

Martin Seligman, one of the originators of positive psychology, conducted a study in the ’70s that gives insight into the types of mindsets that make people feel helpless. Seligman found that those who exhibit long-term “learned helplessness” tend to view negative events as being personal, pervasive and permanent. In other words, if a person is rejected, they might rationalize that the rejection is a result of their own failing, that everyone else is likely to reject them as well, and that they can do nothing to lessen the likelihood of rejection.

When you prepare to approach someone, consider instead that, if they say no, they aren’t really rejecting you, but rather rejecting your request. It’s not personal. Maybe they’re in the middle of something, or maybe they’re just not in the mood to talk. The rejection is fleeting, and the next person might be perfectly happy to participate.

Portigal year in review, 2013

It’s time to sum up some of the noteworthy writings/happenings of the year. Let’s get to it!

All those years ago: 2012, 2011, 2010, 2009 and 2008.

Interviewing the Interviewer – Steve Portigal talks with Maish Nichani

index

UX Booth has published a two-part conversation I had with Maish Nichani of Pebble Road.

In Part 1, Maish interviews me (excerpt below). We explore a few aspects of the research process, including how a project plan is negotiated.

MN: What is an appropriate response to give clients who insist on specifying aspects of your research methodology?
SP: Whenever a client approaches me and has already specified the approach we should take with their study, that’s usually time for a conversation. Sometimes teams create a research plan as a stake in the ground when what they actually want is feedback and a recommended approach. Sometimes, though, their plan is a good one, and we might just suggest one or two changes to see if they are amenable. I can’t count the number of times I’ve received a detailed request, exclaimed “what?!” and then had a really excellent conversation to better understand the reasons behind it. Obviously, no one should take a project where they don’t believe the method is going to produce results. An examination of a prescribed approach is one of the first tests of (the potential for) good collaboration.

In Part 2, I interview Maish (excerpt below). We talk about how to improve the organizational learning user research.

SP: If you could wave a magic wand and create any kind of tool or artifact to support the research process, what would it be?
MN: Research is really all about creating new knowledge and the more people who have access to that knowledge, the better. Currently, our research findings and insights are all locked up in (what Karen McGrane calls) “blobs.” We need it, instead, to be “chunked” (as Sara Wachter-Boettcher says) so that it can travel more freely and be mixed and mashed up to create, again, new knowledge. I don’t know of any existing project or initiative but I was thinking about using a schema (like what is already available on schema.org) for research findings. That way anyone writing up research findings could use the same markup and then search engines and specialist apps could read and move those findings more efficiently.

Steve interviewed by Tomer Sharon

steve-and-tomer

I was interviewed by Tomer Sharon (as part of his incredible series of interviews for It’s Our Research). Our conversation ranged from about why it’s hard for people to do user research, the collaboration between agency and clients, and how to think about organizational and stakeholder challenges as design problems.

The 22-minute video is embedded below.

Steve Portigal It's Our Research interview

Series

About Steve