ResourcesEvents

Workshop overview

In this workshop replay you’ll learn how to run quick, lightweight tests on your product’s copy using Lyssna, and how to get clear, useful feedback in minutes.

No complex setup. No endless research. Just fast answers and little tweaks that lead to real improvements.

About the host

Joe Formica leads workshops and creates educational content at Lyssna, bringing over 10 years of experience in UX and education. His practical, hands-on teaching approach has helped thousands of designers develop their skills and create better products.

Transcript

 Hey, what's up everybody? Welcome. My name is Joe. I'm the design advocate at Lyssna. I'm your instructor guide today. And basically I've been a product designer and researcher for over 10 years. I've worked on. A whole bunch of different projects, especially in, a long span of working as a freelance senior product designer.


I've learned plenty of lessons along the way, learned them the hard way, and have a lot of experience with different industries different team sizes subject matter. And I try to bring that into all of these workshops. Definitely a lot of it in the stuff that we're gonna work through today. My main thing for any workshop, whatever topic we're talking about, we, whatever research method we're learning about I want to provide, these are my goals to give you an enjoyable workshop. I know you guys are spending an hour out of your day or evening or early morning to be here when you could be doing plenty of other stuff.


So these are the two big questions I'll ask you at the end of the workshop. Did you enjoy it? I hope it. Time flies and it doesn't feel like a long, boring webinar, but something that's engaging, fun and applicable. And more importantly, do you feel like a better, more confident designer, ux writer, researcher whatever role you're in than you did an hour ago.


So those are my goals for today's workshop. I'll ask you those two big questions again once we wrap up, and I'll also give you some ways to provide some feedback for things we can improve on. All right, cool. So some tips for getting the most out of our workshop today. Number one, everything is recorded here on contrast.


That's gonna be sent out shortly after the workshop. If you miss anything, if you have to get up and, go get the door, grab a glass of water, everything will be in your inbox after this. And you know whether or not you're here the whole time or miss some of it, it'll all be there for you to review.

And I'll also be sharing some more of the resources and kind of hands-on stuff that we're working through today. Next keep the chat open and active. You guys have done a great job of that, as well as putting the screenshots in Fig Jam. Today's gonna be hands-on. We're gonna dive into a couple quick examples, let you work through some of the ux writing challenges that I set up.

So whether it's the chat, fig jam, the overall message. Participation is good, helpful for me, and also the best way to get as much as possible out of our time together. And finally stay comfortable, hydrated and happy. I got my big water bottle here. Make sure you're comfortable in a good, hopefully quiet environment.


And if you need to get up to run to the bathroom, grab some water, do whatever to take care of yourself and be more focused, go for it. And of course, let me know if there's anything I can do to make it more comfortable and enjoyable for you. All right, everyone good with that? Let's let, gimme a thumbs up in the, oh, I don't know where the reactions went here. All good. Here, I'll type it in the chat. Sound good?


Gimme a thumbs up on that if it sounds good. And if you can still hear me, see me and see my screen. Nice. Excellent. Okay, cool. So let's go down to let's get started with UX writing. Here we are talking about UX writing, that is the title of this workshop, UX Writing that gets results, simple tests for fast feedback. But UX writing, although something that's really been, I'd say popularized in the spotlight recently, over the past, past few years is something that still has some vague borders and definitions. And I think there are a lot of factors to that. But one of them being that people.

In addition to UX writers in all different roles are actually doing UX writing probably many of you here that are not hired in a full-time UX writing position. So I wanted to start off by just giving a super quick overview. I'm sure everyone here is, pretty familiar with the big stuff with UX writing and for some of the specifics, we're gonna get into those in our example.But wanted to set the stage for what we're talking about here. So when it comes to UX writing, unlike traditional marketing, which is one way, communication, apps, websites, digital experiences, the stuff we're working on and researching are two-way interactions or conversations with plenty of back and forth.


So this doesn't necessarily mean it's a conversation as in a chat bot or some kind of chat type thing or AI experience. But even on a much, much simpler level, right? When you are even think of a really old school website, like something from, 25 plus years ago where there's certainly no, chat bots or advanced back and forth conversation there's still a, there is still a back and forth.

It might be, are you sure you wanna delete this file? Yes, no, save as a copy, something like that. Those simple interactions and the feedback and the words and language that's involved in that is something that has been constant and all throughout digital experiences. So whether it's a literal conversation or not the words.


That you're writing, the way that you're communicating with your users through those is something that feels like a conversation and has a lot of the same characteristics in terms of helping them be successful, reach their goals and improving your product. As the dead simple or, simple as possible breakdown between something like traditional copywriting and UX writing or writing something for a digital experience. I wanted to highlight, I think some of the big differences get away from like the name, the naming, like marketing copy, product copy, UX writing, and more. So just get into the characteristics. When I think of traditional copywriting, a billboard to me is like the most, like the perfect quintessential example of that.


In the sense that, number one, it's one way, right? Drive past, walk past a billboard. See this slack ad with a big headline where polishing the pitch deck happens. You receive that message if you read it, and that's about it. Maybe you check out slack later. Maybe it just, lives in the back of your brain until you're ready to think about slack or how you wanna polish your pitch deck.

But there's no response, there's no interaction with UX writing or stuff that we're talking about here. It's two way back and forth conversation, like I mentioned, and it's continuous and everywhere, always throughout the product. I think after this workshop, hopefully when go back to whatever you're doing for work or checking your email or interacting with any digital product maybe you'll notice a little bit more just the sheer amount of.


Back and forth, right? Things that you're doing, responses or choices that you're getting, the amount that you're reading, even if it's in little bits, like some of these slack messages down here. It doesn't read as a traditional conversation, but it's, it is in a different sense. More so just drawn out over the entire lifecycle of interacting with a product.


So you might not think of it as or you might be so used to some of those experiences. You might not think of it as UX writing or a conversation but maybe you will a little bit more after this workshop. Some other differences, traditional copywriting, like a billboard, like a banner ad uses often emotional attractive language, whereas UX writing is going to often be more descriptive, product specific, tailored to the situation and the user.


Not as much aspirational, but more functional. And that gets to the last point down here where I have a typo. Where traditional copywriting more about sales, marketing and promotion, whereas UX writing is more about usability, overall experience and as I said, functionality throughout the product and supporting the user towards their goals if they're doing a good job of it.


I think the biggest thing that I like to point out with UX writing especially just kicking it off, is that it's way more than just a nice to have or a vibe. It's something that can make or break the user experience and really have a massive impact on your product and how successful users are with it.

Yes. A lot of the examples that you guys dropped into that UX writing board up there and a lot of the products that are often highlighted as good UX writing do have a vibe. They do incorporate humor, friendliness, helpfulness support, things that feel more human and personalized to you. So that's definitely a part of it.


But I also want you to expand your thinking about UX writing beyond that into something that's a really powerful tool in. Functionality and in creating a positive user experience or making or breaking a user experience. And I put this example here from Slack. I made a little video that had something like this last week. But just as an example, there's this top message, send message and trigger channel notifications and or redesigned tweaks when I did below it that says, by using channel, before you send your message, you're about to notify 19 people in seven time zones. Are you sure? We get some copy here or choices to edit the message to send it now.

Some tips for shortcuts and a little advice on where you can control this warning in the future. And I like this example here because it highlights in a small form the power and the functionality of UX writing as a design tool where this is, nice little notification with our rooster and kind of on-brand slack language.


But we can see compared to this one down here, when you go back and look at the top one, you realize that it leaves out some important details that could lead to a pretty bad experience. For example, notifying your 19 coworkers in seven different time zones when you didn't actually mean to. So a little snippet, but I think a good one to get us in the zone of. Thinking about UX writing as a functional tool in addition to just good vibes and a voice or enjoyable tone that people like to interact with. Some other things to call out. I don't know why my gift's not working here, but you guys all know what it looks like. You don't have to be a talented or cr let's say creative genius or copywriting guru to be a great UX writer UX writing and doing it effectively and using writing and language to create a better experience and communicate more effectively with users is really a lot like any other aspect of the design process.


It involves understanding their needs, behavior, the scenarios that they're in. Testing, iterating, improving as we're gonna do in a minute, and being in tune with their experience, the different phases throughout it and how that relates to the way that you communicate with them. So this is a question that I've got a lot, especially when I've posted more beginner oriented UX writing workshops where I felt people, and people have written me emails about this, they felt conscious about Hey, I've never, I'm not good at writing marketing copy. I'm not good at writing a catchy headline. So if anyone came into this workshop today, maybe feeling some hesitation around that I hope you don't by the end of it, and I hope you get to see that it's really more so a process to follow and to. Implement into your day-to-day work and something like, being a copy copywriting, marketing whiz. Mainly what I want you guys to see today, improving UX writing is one of the most efficient and impactful ways to improve your product. Improving your product in and the user experience or your business goals is hard. It's, research takes time. You need buy-in. You might be trying to craft long studies.


They're, it's complex to get those findings and synthesize them into actionable insights. And then you have the whole other side of building new features. The timelines that go into that, the resources, it's tough, right? It's easy, it's simple in ways to understand your users and their goals and build stuff that supports those. But in reality, especially when it comes to new features and. Improving your product that is time consuming. Costly requires a lot of prioritization. UX writing I think of as like low hanging fruit. It's something that can have a huge impact on your product. As you'll see, it's something that you can get insights into and do research on fairly quickly and efficiently, especially with some of the tools that we're gonna look at. And in terms of implementing it, a lot of times it's just changing text, right? Or close to that. I think of UX writing as, yeah, low hanging fruit or a really huge opportunity to make fast, but high impact improvements to your product. That in many cases could be even more impactful than like a new flashy feature or something that takes months to research and build.


So hopefully you see it that way after our workshop today. Let me see. Me. Just you, Dan must be in the office. Let's see. Dan freeze for anyone else. Okay, cool. Sorry, I should have that open. Massive improvement. Cool. Sound good? Everybody put it in the chat. You guys can gimme a thumbs up and we're gonna get into our project here in our two, two many lessons that we're gonna work through together. Lemme make sure everyone's good. I'm coming through clearly. Hopefully you can see my screen. Nice. Awesome. All right, so let's move down to our scenario. As I mentioned we're gonna, we're gonna get hands on here today with kind of a demo project that I created and some ux writing examples that we're gonna work through, test look at some results through together.

So this is what we're taking on for our mini projects. Today. We're taking on the role of the UX writing team, let's say for home list, a platform for finding and hiring home improvement pros. So think of this like Angie Thumbtack, I think is pretty similar to this. So we're gonna use this we're gonna glaze over some of the details of the actual product but we're gonna use it as our baseline and our role to work through some of these UX writing challenges and make some improvements in a few scenarios.


So we're gonna cover three scenarios and how to test them, work together on improving them. I think we're gonna do two and save the last one for homework so we can take some questions. But everything, as I mentioned, I wanna focus on, when I was putting these examples together, I wanted to focus on things that are quick, effective and impactful. Getting away from the long, drawn out complex research studies that are hard to connect to an end goal or improvement, and get right into some of this, as I said, low hanging fruit. Things that you can test quickly, implement quickly, and things that can make a big impact on the user experience and your product.


All right, so we're gonna start with a tree test, which I'll get into in just a second. And we're specifically gonna focus that around UX writing, for example. We're gonna see how confidently and se seamlessly users can find what they're looking for. Then we're gonna get into a five second test where I'll introduce this scenario. We'll look at some test results, and we'll do some work, little light design work to improve it, and measure the improvement that we made. As I said, preference test. I have some stuff saved for that, but I think we'll probably do that one for homework so we can spend a little more time on feedback. But we'll see how we do on these. Alright, so let's get into our first one. So now we're coming down to this tree test section down here. Everyone with me once again, feel free to just follow along with the screen share. But I'll let you know when we're gonna get into putting some stuff in this fig gym.


All right, so we are working on home list. We're taking the taking on the role of a big, let's see how many people are here. 77 person UX riding team for this one. We should have some good ideas here. And I'm gonna give you some scenarios that we're gonna work through together. The first one being a scenario that would be a great fit for a tree test. So here's the specific scenario that we're working on. Here's our dashboard, my mockup dashboard of homeless. And as you can see, without reading through everything, or even like digesting what's in this dashboard, it's getting busy, right? There's a lot going on here. And we're gonna say that, we're experiencing a common problem, especially as a product expands and new features are added, which is that things get busy, navigation gets cluttered, and all of those new, or a lot of those new features and spaces, pages, functionality, just get stuffed somewhere under some kind of generic menu in some weird, settings page somewhere far away.


And, in the early stages of that, everything still looks pretty cohesive, still pretty easy to navigate. But as it starts to grow, it can. It can actually add up to, I tried to make this as cluttered as possible, but something like this where just first glance, you can, might be able to tell that it's probably pretty complicated to navigate and there's a lot of stuff to look through in it. So we're gonna work on a really simple change a simple copy change to improve navigation and make it easier for users to find what they're looking for. In order to do that, we are going to use a tree test and we're gonna use a tree test in the Lyssna, look at some results, and then share some examples of an improved version. Now, a tree test is a way to assess, refine information architecture, basically your navigation structure or the paths or hierarchy that a user would go through to.


Get to something. So a tree test in, in how it's mainly used is to adjust or test, validate your information architecture, the pages, higher level pages and titles and how those drill down into some more specific categories. And we're not gonna focus on that as much today. We're gonna use a tree test in slightly different and really more simple way to just make some changes to copy and labels and try to improve on how easy it is to find something in the platform. So tree test overall is gonna be a great test, whether you're evaluating information architecture, hierarchy, or ux, writing the labels and titles of these categories to understand how easy and. And or efficient it is for users to find what they're looking for. And that's exactly what we're gonna do here. So the example we have set up, let me come down here. This tree test here, which I'll pull up in a second, is for a user of home list, somebody who is using home list, they have maybe multiple home improvement renovation projects, contractors that they're hiring through home list. And they have that big dashboard that we just looked at to manage all of the different jobs, projects, and stuff that comes along with it.


The test that I set up here, the tree test is imagine that you wanna reschedule a consultation for one of your upcoming home improvement jobs. Where would you, I should say, expect to be able to do this? So let me share this link with everyone here. If you haven't clicked on it already, I'll put it in the chat.But I'm gonna have you guys just run through this tree test real quick. So let me share this in the chat and I will give everyone a couple minutes to go through it. Let me share, I'm gonna share this whole window actually. There we go. Cool. So go ahead and click that link in the chat and pull it up. Let me know if anyone has any trouble accessing it. But you should be able to open that and participate in the street test just like any other, participant a research participant here. So lemme give everyone two minutes to do that. I'm not gonna give any instructions on it or any guidance on it. I'll let you figure that out for yourself. And when you're done, you can just gimme a thumbs up on the message I just put in the chat. So take your time there and when you're done, we'll look at some of the results and break down what we can learn from this tree test.


And I'm not gonna fill it out because I have already, so we're not gonna double up on my responses.

All right. Oh, we got a lot of responses for this one. Nice. Okay, so let me share these. Let me check on how we're doing with completion. We got 26 people completed it. Nice. Gimme a thumbs up when you're done with that one. I'll give everyone another minute here. Do a quick refresh and we'll take a look through the results together.

All right, so let's, before we go into the results, let's take a look at what we just did, the tree test that you just ran through. This one is giving a little context about homeless and what you're gonna be looking at, and then we're getting our prompt. Imagine you wanted to reschedule a consultation for one of your upcoming home improvement jobs. Where would you expect to be able to do this? As you see, or as you just did, you can click through some of these navigation titles or hierarchical categories. And when you think you found the place that you would do this task, I'd find it here and. Pretty much concludes the test and submits your response so you can see, even if you've never done a tree test before or participated in one, that it can be really useful for a couple reasons.

Number one, breaking down the hierarchy or information architecture. So a tree test is something might commonly do after a card sort, and maybe for this very cluttered navigation. This example we're working through here, something like that would be needed, right? Maybe we're not gonna be able to fix everything by just changing some of the labels or wording on these categories, but we can use it to do that as well.


If we have maybe a hunch as a product designer or researcher that things are getting a little confusing. If we're seeing that people are writing support tickets to try to figure out how to reschedule and consultation that they have, we might run a test just like that. Super simple to set up and see, actually put it to the test. Could people find what they were looking for and how easy or difficult was it? So let's look at the results here. I put the link to this in the chat. Lemme do that again just to make sure everyone's got it. And you'll be able to see the exact same results that I'm sharing with you right here. Okay, so we have our backend of Lyssna right here, and we have first our instruction that I provided, and then we have our tree test and our results. That typo is killing me up there, that where would you expect to do this? And then we have our results here. Lemme refresh it one more time. So basically what we're looking at here is the number of responses, the success rate, and the directness. So this is the original cluttered. Site navigation for home list.

So the place indicated by this check mark or the page where you would be able to reschedule a consultation would be under manage events. So when I created this study, I marked that as correct. And also another way to get to it marking it as correct through your projects. So what we're seeing up here at a high level is the success rate.


35% of people who participated in this, you guys plus some about 20, 25 people I did before were able to get to the, and actually to the right place to pinpoint where you would theoretically reschedule that consultation. Then we're also seeing directness. So success rates more were people able to find what they were looking for. Directness is more about how easy. Was it to get there? Did they have to backtrack or did they immediately know, I'm gonna be able to reschedule my consultation for my, kitchen remodeling in this section and that's 18% over here. So we don't have a benchmark for this, but we could try to improve it and test it against what we have here.

Overall, I would say we're seeing some signals, again, we don't have anything to compare it to that are showing us that this is not the most intuitive label or navigation structure. Yes. A lot of you guys just found this. And 35% of people were able to. Make the right guess of where they would be able to do this.


But we're also seeing a lot of paths that go all over the place. A lot of backtracking and a lot of different selections. Even if it was only for a few people, a wide variety of places where people would expect to be, pages, where people would expect to be able to reschedule a consultation. So I would say from this without making too, pulling too much out of it, lots of room for improvement on this homeless navigation structure and some of the labels. So let's go. This is what I just walked through here. Can you, this, these were the results before. So you guys did a better job than the 20 participants who had a 19% success rate. But again, I'd say still pretty much the same takeaways, room for improvement in success rate and directness for sure, making it users feel more confident and it more seamless or intuitive to find the thing that they're looking for, in this case, how to reschedule an appointment.


All right, so how would you improve it? I'm gonna give everyone two minutes here to get into this fig jam and jot down some post-its and leave 'em on the side over here. If you're not in the fig jam, you can totally just put these in the chat. What I listed out here is the navigation structure and labels that you just looked at. Knowing that these didn't test very well, we didn't get a lot of people, majority of people didn't get to the correct spot didn't find what they were looking for or would've been in the wrong place had they been using it. And we had a lot of indirect paths, a lot of backtracking back and forth and checking out the different categories to see could it be in here? Could it be in there? So even those who did find it probably did a little digging based on the data we have. Here's your challenge. What would you change to make it easier, more intuitive for this specific task of helping users reschedule a consultation? We know that we, it's currently under. Events, manage events. Those are the correct answers marked here. Or you could access it through active projects, your kitchen project, kitchen remodeling, let's say events, and manage events. There. We got some thoughts going on post-it. So I'm gonna let you guys rock for, let's see, two minutes, drop some thoughts in there.


And again, we're not changing the hierarchy, structure, flow, anything like that. If you have some notes on that you would suggest or you would think might improve it, feel free to drop 'em in. But I want you to think more specifically just about writing, just changing a couple words. That could be a path to easier navigation or a better more intuitive navigation experience, especially to find your appointments and. Reschedule that consultation. All right, so take a minute and a half, let you guys rock. Feel free to get messy with the Post-it notes wherever you can find space for them. And we'll take a look at a few and I'll show you my, my, my version and some of the results from it. So yeah, don't peak at one.


Yeah. Tell me if I'm pronouncing your name incorrectly, but Yes. How would you validate the changes? Exactly. Yeah. Rerun the tree test. That's exactly what we are gonna do. And what I'm gonna show you right after this, so yes. This is our baseline here. We're getting, I'd say, a strong enough signal that there's room for improvement here, maybe with some quick UX writing changes. But we would put that to the test with some updates and another another tree test. Yep, you got it.

All right. Nice. This is what I like to see everyone keep dropping 'em in there. But I'm just gonna go through a couple of these. So we have, let's see some themes here. What are you guys thinking? Active projects, scheduled consultations from Dan. We have Isadora you sentence case in navigation to relax and tone it down.


Bold a different style and umbrella folders for better scanability. Okay, I was about to say Isador. I wanna see your examples for this one. Rename events to appointments or consultations. Schedule or make an appointment. Manage or reschedule an appointment, even see calendar. Love this. Great. Let me give you a, let's give you one, the chaka nice answers to Zorra. Given a kind of structure for it and some examples. Let's see what everyone else had. Appointments timelines can also be confused with appointments or schedules. Yes, we, that was another thing I was thinking of. Timelines. I threw that in there as a monkey wrench. Events scheduled. So some of you keeping this title of events, but then changing some of the wording, Artemis said. Scheduled events consultations, upcoming consultations instead of project schedule. Maybe you can say manage schedule to imply that you can change, control the timeline. Nice. So I'm seeing I'm seeing some themes here, some good ones.


Number one, making some changes to the labels on events and. We have some ideas of appointments what were the other ones? Consultations, meetings, I think I saw. And then some other ideas, or additionally some ideas to differentiate some of the other navigation items. The similar ones like timeline schedule, things that could be probably easily and were easily confused that we saw in the tree test. Awesome. So main thing I wanna highlight here, we have no idea if these are, if this is the right answer, right? But if we're looking at this navigation, we're seeing that people are struggling to, or. Inefficiently or frustrating to find the thing that they're looking for, in this case to reschedule a consultation.


We probably have some ideas on what can improve that and these are things that we can quickly test out, which I'll show you in a second. So I like these ideas. Lemme see if there's anything I'd like totally didn't think of that you guys came up with ongoing managed project rename events to schedule, you could have categories within it. Yes. So I know I kept you guys to the scope of like just changing the text, but I like all the notes. And good job putting those in here for not just changing the labels but some of the other you. Bigger overhauls we can make on this navigation with information architecture. Great. So let me show you what I did. It is not it's not that groundbreaking, but it's pretty much in line with what you guys had up here. So the TLDR of my UX writing upgrade on this was to change, to totally take out the word events and call that appointments and in other areas I took out, manage and kind of change that to schedule or reschedule. Again, this is based on, and the way I actually did this based on my best guess some competitive analysis that I did. No hard research, but just looking at ways to improve something that's clearly not a great experience and great navigation experience and being able to test it out quickly. So a lot of you guys had same ideas, me, probably some better ones. But this is what I went with literally just changing the labels of these, not even getting to the structure hierarchy information architecture, just changing them into something that I thought might be more intuitive and easy for someone to find.


And these are the results that I got back on this one. So reschedule or cancel appointment. We see we had 20 responses to this. We had a 75% success rate and 55% directness. And in comparison before you guys did, this study, this is what I had with my 21 participants. It was, let's bring it down here. A pretty big improvement on this. On our initial, we had, let's go left to right here. Original 21 responses, 19% success rate, 75% success rate, and a 55% directness. So look, is this a totally groundbreaking game changing update to homeless? Probably not, but we can see. It moved the needle for sure, even in a relatively small sample size and more. So what I wanna highlight is this is quick to come up with a potential improvement to test it out with a tree test like this and then retest it. And more importantly, to implement those changes. To change the label of something in a navigation is a way lower lift than, something larger like a new feature creation or a new tool that you're building. So it's one small example, but I wanted to you guys to see this and get some experience with really the lowest possible lift that can, when added up, have a big impact on an important aspect, especially of a dashboard which is making it easy and intuitive for users to find the things that they're looking for.


And while I can't say this completely conclusive research over I would say that. My solution and any of the solutions that you guys put up here in the post-its would probably be an improvement. We'd probably see some lift there and that'd be progress with some really quick testing and research.

Awesome. All right, so let's go over to our next one. We're gonna go right up here to our home list updates and email notifications. So follow me up there and lemme just check the chat see if there's any questions here. Okay. So how many participants would you typically recommend for this type of study? So there's that is the constant question with any of these, I would say that. It depends, obviously, and I know that's not the answer that everyone wants. If you are going to do a massive overhaul on your navigation, totally break things down and build them up again. If you're working on a feature that is going to, make or break your product, let's say you're gonna wanna do more than 20 responses on a tree test.


But the other side of that is that with a lot of studies, especially something like this, you will reach a point of diminishing returns on that research. You might even if it's not, let's say statistically sound or you have a huge sample size there's gonna be a point where you're starting to see themes that make you feel confident enough to. Change events to appointments in this case. So my advice for something like this, and especially with list net and getting started with it, or running a test like this, is to do 20 get 20 responses. For something like this, it takes minutes to recruit 20 people from the panel in most cases and go from there.


In some cases, depending on the decision, that might be enough for you to go in one direction or another if it's not like a super high stakes design decision. But in most cases it'll probably give you an idea for a follow up study, maybe some different wording or some. Ideas to improve it. And some ways that you could test out or improve the way you're testing it out with a larger sample size.

That's a huge generalization that I'm making there. But my main point is starting small with the, it all depends on how confident you wanna be with the the data that you're getting back and the statistical significance of it. But starting with 20 people in something like this, that's how I would go about it.


See if it moves the needle at all, and then consider if I want to validate that with more participants or maybe even continue to iterate and try to improve that and test it again. All right, so let me let's go down to our next one here. Homeless updates and email notifications is the last one we're gonna work on today, but this is our next scenario that I think will be a little bit more fun than the last one.

So users of home list, someone who's using it to manage and hire for home improvement projects. They get emails about updates, new appointments and activities on their jobs or from their contractors. The current email, like the one you're seeing here, feels friendly and celebratory, but they don't make the next steps clear. So this email that you're looking at your project is one step closer to kickoff. You've got an updated document in one of your active homeless projects. Log to review, respond and keep up the momentum towards a completed project. Ready to take a look, see what's new. I went pretty vague with this one.


Friendly, upbeat. Might be mistaken for good UX writing in a lot of cases 'cause it's. Positive, it's human, it's encouraging, but the reality is that it's not helping users or the contractors towards their goals. If someone gets this email and doesn't really, and skims it and doesn't really understand the actual meaning of it, which is that a contract's been updated and you need to approve it to start your job, and they just read, delete that email or breeze past it it can be really friendly, but that's gonna delay the project.


That's gonna leave maybe frustration or a need for a follow-up from the contractor. And it's gonna miss an opportunity to really give them the real experience, positive experience, not just a. Pleasant email of having a project that moves forward quickly, seamlessly, that they're in communication with and that they're updated on at each stage. So this is a great use case for a five second test, which is what we're gonna look at here. Attention spans are declining for sure, and a five second test is a great way to make sure that you convey your message quickly. Five second tests. What they look like is, we'll do one in a second, but you're basically presenting a design to the participant and you're giving them, could be five seconds for this one when I did seven seconds to look at it, try to remember as much as they can, and then asking them one or a few follow up questions after that.


This is a great study for. Something like this email where you wanna make sure that the messaging is clear, even in a, brief couple moments that someone's looking at it, that they understand, hey, it's time to, approve this contract, or your job won't continue. Or it won't be, you won't be able to start the project that you're working on. It's great for headlines. It's great for a features page if you're highlighting the benefits of something and want to see if people can digest that and recall it in a quick snapshot. Lots of different use cases for a five seconds test, but I wanted to focus on one that was a little bit more functional and a little bit more impactful here. Because if people don't get what's happening here and don't get the implication or don't improve or approve their contract, that's gonna have a real negative effect on their experience, the job, and probably with the contractor as well. So here is the email. And let me share the five second test with everyone in the chat.

It's gonna skew our results a little bit, but luckily I have screenshots for all of them. So I'm gonna put this in the chat and you can participate in a seven second test. This is not a five second test, so go ahead and click on that one. I'll give everyone a couple minutes to walk through it. You can gimme a thumbs up when you're done,


and we'll check out some of the responses and try to improve it with some UX writing. I know we're almost at time, by the way, everybody, we'll go a little bit over, but I've super quick wrap up at the end, give you a couple minutes to work on this. So if you're down to, hang out for an extra couple minutes, stick around. If not, it'll all be in the recording.All right that's gonna, like I said, skew our results a little bit since I just talked through the example and you guys are already working on an improvement. But I wanted to share what that study looks like to give you an idea what it would look like for participants and what it would look like if you were seeing it fresh.Really good study again, in line with everything else we've talked about. Simple, fast to create, fast to distribute and recruit for on Lyssna. And just like in this case, something that could give you a some really impactful results with changing the text. All right, so here I'll show you my results from this that I got before you guys did it, which were not good.


Now I got all this qualitative information of people to recall what it was about to ask them what they would do next. And to get a sense of the how urgent or time sensitive they felt it was. Again, one of the main issues with this original one that you just went through and as we saw in a lot of the feedback is that people couldn't really grasp it quickly and can, most cases didn't see that it's something they need to take action on or something that could delay their project very friendly, but not super clear about those next steps.And not very effective at moving the job along and relaying the main thing, which is, Hey, check out these updates to the contract, approve them so we can get started on your kitchen remodel. So as you guys have already started how would you improve it? We're getting results from the study that you just did, that it's hard to recall. People aren't really, they know it's an update on a project, but they don't really know the next steps. They might not know in a quick seven second snapshot the purpose of it, the importance, let's say, of it. And we get this kind of fluffy, friendly language that misses the mark on an important part of the customer journey.

How would you improve that if we were to run this exact same study again with your updated version? What would you do to see people recalling it more accurately? Understanding what it's asking them to do, and also under being able to articulate the, effect of it or the impact of it after just seeing it for a few seconds.


So we'll take two minutes on that. I'll show you my example and then we'll do a super quick wrap up. Get you guys outta here to enjoy the rest of your day. Okay. While you guys are working on that Lou, I'm just looking at your question. I think it was about the tree test one. You could triangulate the data with an analytics platform that could be a signal that you, that's signaling you to a potential problem. So maybe if in your analytics or site browsing data, you're seeing that people are spending a long time trying to find that reschedule appointment. If you're seeing that people are taking a wonky path to rescheduling an appointment those could be signals for you to a. See that, hey, maybe there's a problem here. Maybe our navigation is getting too crowded and confusing. Maybe we should test that out. So whether you're, like connecting with that, if that's something that you're seeing as a trend, absolutely that could be one of the sources of, signaling that you might wanna test that out or that there's some confusion or inefficiency in people finding what they're looking for in your dashboard.


All right, so lemme check out what you guys got for this. I will say this was a sneakily tough. Example, when I was doing this, I was like, oh, I'll rewrite this and it will be so clear so much better than the original. And then I, I thought about what seven seconds looks like and I started doing what all you guys are doing. Backspace, move that around, put it on the side. Like how do we really concisely communicate this in the right tone, but also getting the message across as quickly as possible. I'm seeing some good stuff here though. Let's see. We got current. Scott, your project needs attention. Contract's been updated in your account. Your, whoever, if you moved the thing, just hit undo and I'll bring it back. Sorry. That's the risk of all of us working in the same file. Luckily I can figure it out. Contract's been updated in your account. Login to review, approve new documents, keep the momentum going. You have one new update for a project. Log into review and keep up the momentum. Your account needs attention in order to ensure your project stays on schedule. Nice. Your contract needs your review. Log in and approve updates if you have questions regarding now. I'm seeing some good updates to the copy there. And also, there we go. Looking good, Amy.

Also some good updates to the button copy, which I didn't highlight, but is part of what we can make some changes on. Jenna, I like this looking super pro. Take action now. Review, now review contract review documents. Good. Not much space to work in, but I'm seeing some good improvements or potential improvements here.


Directions to go in. All right, let me show you what I came up with. Again, not totally groundbreaking here, but this is what I got. Please review and approve your updated proposal. This, I was gonna take this out, but I left it in just to show you guys my work in progress here, where I had a little bit more context. My overall thought process was that first email was so like general and fluffy, like a project in your homeless account. I was thinking let's get the point across to the call to action clear choices but also include some stuff that's going to be like signal to them, Hey, this is about your kitchen run, kitchen remodel project. These are the changes in the proposal. So slightly different from what some of you guys had, but overall same idea of front and center. Review and approve your updated proposal, a call to action view and approve proposal. I actually don't really like this 'cause it might signal to someone that they would accidentally approve it just by clicking that.

So I'd probably rework that, but. Similar idea here. All right, now I have not looked at the results for this one. So let's do that together. First. Let's see the original or we could compare it. This is all qualitative data that I was getting back. But I ran the exact same study here with the updated email or notification. And I'll share the link to the original one. But there is, I can see here now that we got more responses in this, that there is much better comprehension of what the email's about.

Put this link in the chat. Let's see how we did here. If you were to take action on receiving this email, what would you do? Not sure. First, take a look at the kitchen, approve the work right away. Click the blue link, click the button provided, re read it and determine whether the service or not. Click the button. Tap the button, if there's any.


So this one I would say I'm doing a really quick synthesis on some of these, but I would say like the action after this, if I were to go back and retest this, I'd probably reword this question. These were similar to a lot of answers in the first one, which was like, click the button. And what I was really looking for is if people knew the next step of like approving the contract.So that could be something just based on this test with 20 people. That either is a product of the wording here. Clicking the button is actually, super logical answer to this. Or maybe the it not coming through of the actual, what I was looking for is what's the next task you would have to do?We have some quantitative stuff here, time sensitive. Do you think the update is this pretty similar, little bit of an improvement to the original? And let's see, sensitive because it's about the kitchen, if not done, problems may occur. Work can't start without the approval. Not clear with workbook.Didn't have time to realize what this was about. Got the sense that the work is held up, but the communi communication was not stressing anything urgent. So maybe I went a little too light on it. I would say the in terms of a quick synthesis here, this was an improvement from some of the first responses of the fluffier email that I sent or the messaging.But I'm actually happy this was not like a slam dunk improvement because you can see that while it was a little bit more clear and we got more people who were being able to reiterate what it was about and like what the actions were there's still some stuff to improve. I think this one stands out to me.


I got the sense the work is held up, but the communication was not stressing anything urgent. When I wrote this version of it, I was trying to keep it still friendly po keep the same tone. And if we were to continue working on this, maybe a further iteration would be something that is a little bit more urgent, extremely straightforward, blunt, approve your proposal to begin your project.

Action required action needed. Some of the stuff that I saw in your examples could be another direction to go in that either way though, we've got a slight improvement here. We've got some directions to go forward with. We've got some real data and responses from users. We've updated it without any code or, imaginary, like major feature improvements, we're changing text pretty much. And this example could be something that has a huge impact on the user experience. If we did a great job of continuing to refine, test this, really lock in that seven second test and seeing the comprehension go way up and people really understanding it and what's happening, that could lead to a smoother hiring process of contractors.Smoother job, project process, quicker payouts, less headache, frustration for clients and contractors. A lot of things that are gonna flow down from it. All from some really light testing and very light. Product changes in this case copy that we just had to work through and continue to iterate here.


I'm seeing down the line and now actually curious about running another test, if any, if anyone wa put a post-it note next to yours or if you wanna come back and work on it maybe I'll run a couple studies with some of your examples here and share the results with you guys so you can check 'em out. 'cause I think some of these are better than what I put together and I'd be curious to share the comparisons and see if any of these did a better job of stressing the the impact of approving your changes in your proposal. Alright. All right. Awesome work everybody. Let's wrap up from here since you have spent more time with me than you bargain. For thanks for joining everyone. I like to end with some key takeaways. As I said, you'll guys will get the recording after this. You'll get all of the. Access to this fig gem. I'm gonna share some other resources and some stuff for preference testing, and I'm gonna come back and check this out to see maybe run some other studies or iterations on it.So put those in this file, put a post-it next to them to test, and I'll come back and check it out. Follow up with you guys with some results. But key takeaways, even though we went through a lot in a little amount of time today things that I hope that you leave with at a minimum from our workshop, UX writing.


Hopefully if you didn't see it before our workshop today, you do now that it's more than just creating a vibe or a. Friendly tone or communication style that can be an important part of it and can be a very valuable way to implement UX writing. But it can also make a really big impact on how users experience your product.Just in the examples we looked through today, it can change how people find things that they're looking for. It can create a more intuitive experience rather than a frustrating digging experience. And in the one that we just looked at, it can actually be a major link in the chain that could make or break how smooth a kitchen remodeling project goes. Next takeaway, great copy UX copy isn't magic or creative genius. It's about understanding users and their scenarios, goals, behaviors, and how they communicate. Just what we did here. Digging through some of those responses to the email. I don't know right off the bat what is going to get. Perfect score, perfect retention. In that seven second test I have some ideas. As you saw, I tested them out and while they moved the needle a little bit, they didn't, like I said, it wasn't a slam dunk. So I'm going back to the process just like anything else in product design, not about coming up with something, amazingly creative right off the bat but more so to stick to that process of learning, iterating, putting it out there and listening to some of the stuff we look through today makes it a lot easier to do that.

Sticking to that process. And finally improving UX writing is one of the most efficient, impactful ways to improve your product. Keep going back to that idea of low hanging fruit.


If any product that anyone's working on here, there are probably a whole backlog of things that you want to improve, things that you could make smoother, things that you have a hunch are frustrating or have room for improvement, I would bet a few of those have some link or some factor of UX writing that could be improved if improved and tested, could improve some of the bigger goals and experiences in there.So think about those in your day-to-day work, outside of the big features and upgrades and, design refreshes. What are there opportunities to test and change some of the little stuff, the copy that could actually make a big difference. If you had key takeaways, drop them in here on a post-it. And I'll be happy to check those out. I'll come back to that in a sec. thanks for joining. I hope you feel like better, more confident designer, UX writer than you were an hour ago.


And I'd say beyond this mostly what I hope is that you guys will find some opportunities, whatever your role is, to put this stuff into practice because there's really a lot of opportunity for improvement. And UX writing is something that can be overlooked in how impactful it is. if you have any questions on this, feel free to reach out to me and hopefully I will see you in another workshop soon. All right, everybody. See you.

Try for free today

Join over 320,000+ marketers, designers, researchers, and product leaders who use Lyssna to make data-driven decisions.

No credit card required

4.5/5 rating
Rating logos