Planning for Content

Karen McGrane gave a terrific presentation on Content Strategy, and what happens when we re-design a site, and decide to go live with the existing content. Anyone interested in providing their users with a good experience with their content should absolutely watch this presentation.

Here are some of my favorite takeaways from Karen’s talk:

  • “We tell ourselves we don’t need good content, we just need good templates.”
  • “We don’t plan time to create and edit content…”
    “Emphasize the real goal…better information for site visitors.”
  • “Do usability testing with content providers…(not just end users).”
  • “Challenge the schedule: content before design!”
  • “Don’t just persuade: start planning, writing, and editing.”
  • “People don’t go to your site to look at your templates. They go for the content.”

When you think about it, we all produce content: on Twitter, our blogs, podcasts, and other social media updates.  I would be interested to discuss how important it is to produce a good content experience personally and professionally. This reminds me of the old saying, “If you don’t have anything nice to say, don’t say anything at all.”

What are your thoughts on planning for  content? How do you plan for content on the sites, blogs, micro-blogs, podcasts, etc. that you are producing?

Usability Testing Content

For the past three years, I’ve been running usability tests on software applications. Most of the tests have been to measure and iterate on designs and interactions.  However, lately many of my projects my team has taken on have been related to *testing content*.  I realized that I needed a refresher on how to test content, and wanted to share with you what I’ve been reviewing. Highlighted below are some of the methods identified in the UX community to help evaluate whether the content on your Web sites is useful for your customers and prospects.  Not surprisingly, testing content is actually very similar to testing design/interactions.

Content Testing Methods:

Iterative Testing. Kevin O’Connor and Colleen Jones’s 2010 IA Summit talk: “Testing Content: Early, Often, & Well” is a great resource on testing content (here is the audio). Not surprisingly, she talked about how important it is to test content iteratively, just like we test designs and interactions.  She will often start with a baseline test of the content that is on the live site, then follow that up with concept testing, and then do a validation test.  What was interesting was how she focused the *protocol* on three key content questions:  Can users find and read the content they need? Do they understand the content? Can and will they *act* on the content?

5 Second Tests. Christine Perfetti wrote an excellent article: “5-Second Tests: Measuring Your Site’s Content Pages.”  Using this method, you’d basically show participants a web page for 5 seconds, take it away, and then ask them for their initial impressions.  Christine says you can ask them to describe back to you what they saw.  She says users make important judgements in the first moments they visit a page.  This method helps to uncover those judgements.  Also, it can measure whether the calls to action on the page are apparent enough.  She describes a case study with the American Red Cross, where 5 Second Tests helped them iterate on the design of their donation page, to make sure users knew what all the donation options were (i.e., donating airline miles, stock, clothes, etc.).

Inherent Value Tests. Christine Perfetti and Jared Spool talk about this method in a couple of articles, and in a podcast.  They say you’d want to run an Inherent Value Test when your team needs to know how well a Web site communicates the inherent value the designers have put into it, and whether new customers understand the true value of the service.  How it works:  recruit two user groups, in the first phase, you recruit existing users, and interview them about what they like about the product (what they find valuable).  This will help to identify features loyal customers miss.

Eye Tracking, Gaze Plotting, and Web Analytics. I talked with a our Technical Writer, Maureen Lau, who had recently attended the Nielsen Norman Group‘s course on “Writing for the Web.”  I learned from her that the Nielsen Norman Group tests a lot of content with Eye Tracking, Gaze Plotting, and Google Web Optimizer.  Eye Tracking tests how long they look at a particular area (the more red, the more they looked at it).  Gaze Plotting, tests where their eyes jump to.  She said you go through a similar process with content as you do with interactions (paper prototyping, iterating, trying to understand users’ needs, etc.).  She said Eye Tracking and Gaze Plotting are great to see where people look, and what catches their eye, however you need to interview people at the same time, to see if they are actually comprehending what they have looked at. They will use the Google Web Optimizer to roll out an AB test, and see which content “performs” better.  She told me about how readers typically read in an F-shaped pattern.  Finally, she said we want to create tasks around the content. Since users often search for keywords, they suggested getting a better sense of what SEO keywords we use, and testing to see if they look for those key words, where they’d expect to look for it, etc.

Testing Content Concepts. Colleen Jones wrote an excellent article called “Testing Content Concepts” that walks through the specific protocol, probes, and questions to ask participants about when testing content.  Colleen says a “Content Concept” is a mockup or draft of your content.  She says if your run a usability test on your content, and your content is not working well, you should fix the problems and test again until it does. Colleen recommends testing in three levels of fidelity:  content only, content in a wireframe, content in polished design.  What I found most interesting in her article was her recommendation to focus observations on how usability participants work with the content. I also liked her recommendation of measuring how successful people are at reading, understanding, and remembering key messages in the content. Colleen discusses the biggest challenge in testing content:  measuring how the content has influenced the participant to take action. She says “don’t press too hard, and thus, end up with misleading rationalizations.” One idea Colleen has that could work well for us, is to conduct a closing questionnaire  that asks whether participants would now make a decision that differs from their typical decision, and to rate how well the content informed their decision.

I’ve never been so convinced of how critical it is to test not only how to navigate to content and how to find content, but to test the content itself.  It is the content itself that drives influence and calls readers to action.

If you have any comments, questions, or alternative methods to test content, please leave a comment below!

Asserting yourself – one no at a time

Learning how to say “no” is not easy.  Dealing with what comes after the no, the disappointment, disapproval, and rejection from those you said no to, can sometimes seem unbearable. As a User Experience Researcher, I think we are constantly told that we are worth ‘less than’ our more technical counterparts. We are told we are a ‘cost’ to the organization, and that we can’t be picky about the work given to us.  If we say no to staying over the weekend to complete a project, we fear that we will hurt our professional relationships that we have worked so long to build, and jeopardize our job security.

I started reading The Power of a Positive No by William Ury, and it has dramatically changed the way I view my work as a UX Researcher. The following are a series a lessons from the book, and how I think these sessions in positive assertiveness apply to a UX Researcher.

1. “I need to tell them no in a way that is clear, honest, and respectful, and then let them react however they react.” William Ury, The Power of a Positive No

UX Researchers often take on too many projects, and say yes to helping too many people. We don’t know how to be upfront and honest about our heavy workload, because we know that it will cause a negative reaction to the person we are speaking with. Also, we worry and can’t bear to say no to a project, or say no to helping someone because we are trained to “go with the flow” as facilitators. We are great at accommodating participants, and doing whatever it takes to make them happy. However, we need to learn to stick up for ourselves – the right way, and that we cannot control how others will react. All we can do is do our best to be honest, clear, and respectful, and this means we are doing the best we can.

2. “Give respect not because of who they are but because of who you are.” William Ury, The Power of a Positive No

Giving respect is the best way to have stakeholders and co-workers accept your “no.”  When you show stakeholders and co-workers you respect where they are coming from, and understand the pain they are going through that would cause them to bring their request to you, it is much easier for them to see that you are not rejecting them personally when you say “no.” It is critical to put yourself into other people’s shoes, and do whatever it takes to understand what the motivations are behind their request, and show them that you understand where they are coming from. It might be painful or difficult to show respect to stakeholders or co-workers who disrespect you. However, the reason you need to show this respect, as the quote above suggests, is simple:  give respect not because of who they are, but because of who you areUX Researchers have good interests at heart. They work as advocates to improve the human experience of using Web sites, software, apps, and other technologies. This is very important to keep in mind when asserting yourself – be empathetic with your co-workers, and their needs, and it will take you far.

3. “You have done the essential prepatory work. You are like an athlete who has trained hard. Now during the race it is time to reap the rewards of that hard work.” William Ury, The Power of a Positive No

Before I get to how this quote applies to UX Researchers, I need to discuss an anaolgy brought up in The Power of a Positive No. UX Researchers can learn a lot to learn from trees, in terms of how to stand strong.  William Ury talks about how trees have deep roots in the ground that keep their trunks standing strong.  He says, our “no” is the trunk of the tree.  Our “yes” is in what we are rooted in, and in what we produce.  Our trunks however must stand strong, because if they break, what we produce dies.

UX Researchers need to do their essential preparatory work:  deepening their roots in their “yes.” They need to spend time growing in their knowledge and belief in advocating for users, building empathy for users, making actionable insights, and inspiring development teams with user empathy.  Spending time “on the balcony,” as William Ury calls it, discovering our deep core values and interests, enables us to have that strong trunk that grows out of them.  The deeper our roots, the harder it is for someone to uproot us. Even if we are chopped down, if our roots are strong, they will always grow back.  The goal of course would be to have blossoming branches of UX Research, providing useful customer feedback, validation, and get the voice of the customer to be lived and breathed into the very products we ship.

Seven Tips for Presenting Usability Issues to Stakeholders

In a previous life, I was a Library and Information Science masters student, and part-time reference desk librarian. I worked in the Biomedical library, connecting medical students and professionals to journals, articles, research, studies, books, knowledge…I attended medical library conferences and studied how to help medical professionals with “evidence-based practice.” As a
result, I became adept at helping people find evidence to base their practice on in medical research literature. That skill has certainly served me well as a user experience researcher as I work closely with designers and stakeholders, and now unsurprisingly, finding and delivering evidence to inform design decisions is my absolute favorite part of this wonderful job.

I’m in the thick of user research on my current project, and along the way I’ve been reminding myself of all sorts of best practices I learned from the brilliant Joan Kaplowitz, an Information Literacy Librarian.  Using her advice, I do everything I can to make sure the people consuming the information I present, are getting what they need and informing the design questions they have.

My hope is what works well for me, using Joan’s principles, will help you too when you have to communicate your results to a team of stakeholders.

1. Engage your stakeholders

“Active learning is better than passive reception for retention and transfer of learning.” Joan Kaplowitz

In my experience, the best way to engage stakeholders, and have them actively learn usability issues is to involve them in the research.  Having them come to observe usability test sessions and contribute their observations to an affinity diagram is a very effective way for them to retain the feedback they hear, and see trends across users.  One strategy I learned from attending the Nilesen Norman Group Usability Bootcamp in 2007 was from Kara Pernice: have your observers take notes on post-its (quotes, observations, one issue per post-it), and then change color post-its for different participants. Then you can start to group issues together with stakeholders, and see usability trends across users (colors). Your diagram of groups then can turn into your report, transcribing your wall of insights into a presentation slide deck or any other format.

2. Keep it lightweight

“Less is more. It is better to teach a few things well than to overwhelm learners with so much information that they become frustrated, anxious, and unable to retain anything from the instruction.” Joan Kaplowitz

The best way to describe this principle as it applies to reporting usability findings was best articulated by Todd Wilkens from Adaptive Path: “The effectiveness of your research report is inversely proportional to the thickness of it’s binding.”  You will be so much more effective in making change happen, and getting people to take action on your findings, if you don’t overwhelm them with new information. Your goal is to inspire your stakeholders to address the usability issues, and have designers solve the usability problems.  Then, validate those changes were successful with another round of testing!

3. Get them talking

“The instructor’s voice should be the one heard least during teaching.” Joan Kaplowitz

The best presentations I’ve ever given have been because I met with stakeholders ahead of time to get a sense of what they learned from watching usability sessions. Get designers to tell you what they learned, because it doesn’t matter so much what is in your head, as it does what is in theirs. Before giving your final presentation to the larger group of stakeholders, talk with your key stakeholders, and have them tell you what they learned, observed, and took away from the sessions.  Review the takeaways you intend to present, and invite them to add to it. Your final presentation will be far more effective at inspiring change to happen.

4. Grab them in the first 5 minutes

“You win or lose your audience in the first five minutes. Talk to your learners as they enter the room. Provide them with something to do and/or think about as people are arriving. Engage them from the start.” Joan Kaplowitz

Sometimes the beginning of the findings presentation is the most challenging, because all your great insights are coming later in your slide deck.  However, the beginning of a presentation ALWAYS sets the stage for the message you are giving. Get to the presentation room early, and build rapport with each person who comes through the door.  Great them with a hello, and say their name (people love to hear their own name).  The goal before the presentation starts is to get “audience members” on your side, because in my experience, these are the folks that that are most likely to help fend of hecklers in your defense! Also, you want a strong introduction.  You definitely don’t want to stumble through your first 2 minutes of speaking.  Here is a basic introduction that I use often – but the more creative you can be the better!

“Great, let’s go ahead and get started. Today we are going to talk about_____________. We have about 45 minutes for the discussion, and I’ll leave some time at the end for questions, but if you have any questions along the way, please feel free to ask. First I want to ask… who had a chance to observe the sessions?  Great, well if there is anything you would like to add that you remember observing, please feel free…”

5. Demonstrate each key issue

This advice I learned on the ground floor at the UCLA Biomedical Library reference desk.  Students, nurses, patients, etc. would come to the desk asking how to use the library databases.  The most effective way for them to learn how to use the databases wasn’t just telling them, but actually demonstrating it to them. In fact, it was best if you could hand the keyboard to them, and have them drive themselves.  In an usability findings presenation, you really want to re-create the issues that participants had during the session.  Stakeholders tend to be quite visual, and greatly benefit if you show them what you mean.  Take full screen shots, and simulate the experience of using the technology using basic animations such as fading in.  This seems to be the best way to re-tell the story, and have your findings really sink in with stakeholders.

6. Keep track of your effectiveness

“Always include a way to assess your outcomes. Otherwise you will have no idea if your learners have attained them.” Joan Kaplowitz

In the world of UX Research, the best way to assess your outcomes is to keep track of which issues are on the plan to getting fixed, and which ones have not been fixed. You can keep track of these in an Excel spreadsheet on your own, but the best is to have your issues make it to the product roadmap.  You want to see your usability issues turn into “user stories” if you are working with Agile teams, or possibly the roadmap, bug fixes, or “change requests” if you are working in a waterfall environment. However your organization keeps track of changes that need to be made to the system, do what you can to make sure usability issues are represented there.

7. Take a multi-format approach

“Use handouts, web pages, and pre and post activities to extend your contact time with your learners. Offer ways for learners to keep the conversation going after instruction is completed — through email, blogs etc.” Joan Kaplowitz

A PowerPoint presentation is a great way to walk through usability findings.  However, you don’t want to only deliver a slide deck. In addition to your presentation, you will want to give a “hand out” to your key stakeholders, the people who need a “check list” of things to address.  Don’t rely on them taking their own notes during the presentation, give them a list that they can easily make notes to.  You don’t need to pass this out to everyone, just to your 1 or 2 key stakeholders. Also, I’ve seen a follow up email work really well, with a link to your presentation, to the recording of the discussion, and a couple bullets that summarize the key takeaways.  Inviting users to continue the conversation using wiki pages is a great way to keep them engaged, and continue with next steps.

So there you have it. This is my very best advice on how to present usability findings so that it inspires your stakeholders to take action. Many of the information literacy principles listed here apply to basing design decisions on evidence.   How do you communicate your usability issues?

Six Great Articles To Improve Your Writing

Do you want to become more comfortable blogging? Crafting a strategy to post interesting posts frequently can be a challenge.  Here are 6 articles from expert bloggers who discuss how to generate useful posts, how to get over the need to be perfect, and how to get your ideas out there as often as you can.

1.  “How to write 3 blog posts in one day” by Chris Brogan (writes 4000 words per day!).  Chris encourages readers to get over the need for everything to be perfect in order to write, but to instead find pockets of time to write. You can do this if you keep a notebook in your back pocket, take photos of interesting things, use Evernote to capture your thoughts, etc. He advises that you get into the habit of seeing everything with curious eyes, and show the world what you are seeing. He also says not to be afraid to write clunkers, and write imperfectly…

2. “How to write a great blogpost in 15 minutes” by Nerma Moore
Nerma recommends developing an organizational format for each of your articles (so you don’t have to think about this each time). She says to keep a bank of headlines (questions, quotes, short story title spoofs, stats). She of course says to time yourself, and strive to write short, comprehensible sentences – then, step away from the computer. She says to “think progression, not perfection.”

3. “5 simple ways to open your blog post with a bang” by Brian Clark.
Brian outlines 5 ways to start your blog posts. The most interesting ideas were to share an anecdote that will make people laugh, and use words like “Imagine” or “Picture this” or “Do you remember when…” I think I could also have fun with using analogies, metaphors, or similes, as he suggested, especially if I can conclude the article with a tie back to the beginning. Fantastic read!

4. “The reason you are stuck”
by Seth Godin.
“You must find something SO IMPORTANT that it is worth enraging your prehistoric fears, SO IMPORTANT that you can’t sleep until it ships, SO IMPORTANT that yes, you are willing to go through all the hoops Leo lays out for you in order to ship. Either that, or you could be mediocre instead.”

5. “How to write an executive summary” by Eric Markowitz.
Eric starts out his article with a 2 sentence sub-headline, that summarizes why you should read the article – great technique! He also advises that the executive summary should tell readers what it is that you do, and why they should read the rest of your text, proposal, results, report, etc. He says your first sentence is the executive summary of the executive summary, and that you should tailor your summary to your audience (much like you tailor a resume to a job description). Your summary should strike a chord with your readers, and describe how you’re report is special/unique in a certain way. Finally, I really liked his idea to create an executive summary that matches the outline of your report, and to include a section called Why Now, to show the urgency of reading the report. Great ideas!

6. “Rethink your web presence” by Chris Brogan.
Chris says we need to think about what users want when they come to our Web site, Twitter page, LinkedIn page, Facebook page, etc. First, we need to spell out who we want to come to our sites. Next, we need to identify how they will know they belong there. After that, we need to show what we want them to do – and make this really obvious. Finally, we need to explain how they can stay in touch with us. Great tips!

What materials have you read about how to write better? Please feel free to share in the comments!



Bonus Articles:

“Elements of a Good LinkedIn Recommendation” by Chris Brogan

“How to write Better Linked In Recommendations” by Lisa B. Marshall

Do you need to be right all the time?

Have you ever tried to introduce a new idea, but had people tell you that it is a bad idea? Have you ever voiced a concern, or offered an alternative direction, and heard someone say to you:

“No, that won’t work…that’s not possible…that’s not relevant.”

It can be unsettling to face resistance, especially when the resistance happens in front of others. It can feel like a huge blow, and can be very hard to swallow the fact that people don’t see where you are coming from. It seems as though UX Professionals in particular feel tempted not to voice their opinion at all, when they have faced too much resistance. However, we can’t let these things get to us. We need to learn to let things roll off our backs, and move on. Here are five tips and advice that UX professionals can use to approach conflict:

1. Change your attitude. UX professionals think very highly of themselves, and have a tendency to position themselves as higher, or more important than others. When others resist their idea, it comes into conflict with how they view themselves – how could anyone not support my brilliant design decision? How could they not understand all this brilliant research I have done? Newsflash: you are not more important than anyone else. So, change your attitude, get over it, drop the ego, and move on.

2. Be humble and gentle. You may be very passionate about your idea, and you may want change to happen no matter what the cost. You might be tempted to talk about your years of experience and accomplishments, thinking that it makes you more credible, and that they should listen to you more. But this just makes you come off arrogant and conceited. It really does NOTHING for your cause. Also, be sensitive to the fact that maybe those you are talking to are not ready to fully embrace your idea. Give them the opportunity to solve the problem as well – treat them the way you want to be treated, and seek out their thinking and expertise on the issue. Be gentle and soft-mannered in your response back.

3. Do not introduce a new idea out of selfish ambition. Before talking with your team about a new idea, determine why you are introducing this new idea. Your team will be able to sniff out any selfish reason you are trying to get them to adopt your thinking, especially if you are looking to get more recognition. Think instead about what would be best for the team, and for your fellow teammates. Generate new ideas and opinions that make them shine, advance, give them more flexibility, or help them become a more balanced employee.

4. Don’t consider perfection as something you can grasp. Accept the fact that you will fail, and make mistakes, and that others will make mistakes too. You can’t possibly be perfect at everything, and mistakes will come, no matter how hard you try to prevent them. Keep a notepad with you at all times – when you make a mistake, write it down, and what you will do differently next time. Then move on. Also, don’t expect others to be perfect either – they are human, just like you.

5. Be patient. Your idea may be a good one, or you may have a legitimate concern. However it might just not be the right time to introduce your idea. You can always come back to it later, if you feel you are still concerned. But just be patient for your team to get to a point where they are ready to try your new idea.

You don’t have to be right all the time, and you don’t have to stress when others don’t see things from your point of view. Life goes on, and if you treat each other right, you might just get more accomplished than you thought you could have otherwise.

“The happiest of people make the most of what comes their way.” ~Unknown

Sometimes User Experience Research can be stressful. It can be difficult to manage competing priorities between clients and projects, and it is nearly impossible to please everyone. No matter how hard you try, you can’t be “perfect.” How then, can we make sure that we are delivering value to the organizations we serve?

Make the most of your mistakes. I’m learning more and more, that instead of perfecting a project to flawlessness, it is more important to make the most of the hours I’m given, and embrace any mistakes that come my way. Doing your very best, and giving it your all, suddenly isn’t about putting in all the hours you can, but making the most of your mistakes.

Address the root cause of your failures. Instead of putting in a ton of hours perfecting your work, embrace your failures, and instead spend more time finding new ways to solve the root problem for the failure (lack of resources, clarifying priorities, etc.).

Show your clients & employers that you can pace yourself, and won’t burn out. Clients and employers really want to make the most of our services, and are happiest when they can use our talents and skills to their fullest potential. They don’t want us to burn out, hit a wall, or crash. They want us to continue to produce high value to their organization.

The only choice I see, is to work hard during the hours we are given, make mistakes along the way, and learn from them. This does not mean we should slack off, and not do our best at work. It means learning to say no to distractions, and being highly efficient in our work.

What is User Research?

“User research is the process of understanding the impact of design on an audience.” – Mike Kuniavsky, Observing the User Experience

Sometimes I feel like we struggle to explain what User Research is all about. Too often we get caught up in the day to day implementation of User Research, and lose touch with how to explain what we do in plain language. Our job as User Researchers, is not to simply run usability tests, and communicate the results. If you tell your friends, colleagues, etc. that all you do us run usability tests, they will give you a blank stare. We don’t just run usability tests, we help dev teams understand the impact of their product, feature, system on its intended audience.

But I think a more powerful question is: what happens when you don’t think about the intended audience? What happens when you don’t conduct user research? Here are three consequences of not thinking about the intended audience, and how User Research can help:

* Your product could become ‘incomprehensible.’ Often times, products and systems are made, but people saying they can’t understand what the product is for, what to do with it, what problem it solves, let alone how to use it. User Research can identify this early, before launch, and can generate ideas to better communicate what the product does to the end user.

* Endless internal debates about scope, audience, purpose, and functionality. Many times, those working on a new Web design project feel like they can identify with the user. They will say things like, “I never like it when sites do this…” or “I always expect to see…” When project scope, audience, and purpose is defined by the those on the project, and not by those who will use the end product, debates sky rocket. However, when User Research is involved, you can find out what users think is most important for the project. After doing even a handful of interviews with users, suddenly your scope, purpose, functionality, etc. of the project can become much better defined. User Research makes everyone more aware of what is most important to the end user.

* Creating a solution that doesn’t solve any real problem. Solutions are sold because they relieve pain points for people. You need to conduct User Research to understand the problem, and the kinds of people who have this problem.

Bottom line: User Research is about identifying and defining problems, not creating solutions. It is about looking into problems, and spelling those problems out for the people who build the products – to those who have the power to solve the problems. Designers are inspired to solve problems, and user research inspires them.

Blogging through “Observing the User Experience”

I’ve decided that if I really want to learn and grow as a User Experience Researcher, I need to read and apply more best practices. I was really inspired by Julie and Julia, the story of a woman who blogged her way through Mastering the Art of French Cooking, as a way to commit to learning to cook.

In Observing the User Experience, Mike Kuniavsky from Adaptive Path writes why user research is good, and how it fits into product development. He also addresses various research techniques, and ways to communicate results. Much of what I think, worry, ponder over all day every day.

I look forward to reading and writing about the book, and how I apply it daily.

Stay tuned!

Build Your UX Stamina

“Success comes from knowing that you did your best to become the best that you are capable of becoming.” – John Wooden

As a UX professional, you will face many opponents – many people will want to fight you. They will play devil’s advocate, mistreat you, and question your work. They will resist your ideas and tell you tell you you can’t do what you want to do.

So much of the work a UX Professional does is subjective and artistic – there isn’t a right or wrong way to do what we do. However, people will fight you, grill you with questions and disapprove of your judgement.

This will exhaust you – unless you have the stamina to sustain you. How do you build the stamina needed to continue to stand up for what is right? For me, I need to build physical stamina. With strong physical stamina, I have the strength in my heart to:

* remain calm in the midst of conflict
* confront conflict at work and family
* stand up for myself
* call co-workers out when they do something wrong
* work through conflict with difficult people
* do the right thing, when others pressure me not to
* say “no” when someone tries to take advantage of me
* set and enforce boundaries with children and family

UX Professionals need strength in their heart to stand up for what is right. If you tend to get exhausted in the midst of conflict, confrontation, bullying, or pressure – try building your physical stamina. You might just find the strength to do the right thing.