Monday, April 18, 2016

The 3 Most Effective (And Overlooked) Content Curation Strategies

Want to learn the most effective curation tactics and best practices – the ones to make sure your efforts produce real results? Here are three tactics to ensure that your curation efforts are noticed, appreciated, and rewarded. Continue reading

The post The 3 Most Effective (And Overlooked) Content Curation Strategies appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1W2CY96
via IFTTT

What Is the Difference Between Content and Content Marketing?

Stop creating content. Start creating a content brand. Discover why just because content is everywhere, it isn’t enough. Learn why content marketing success really requires owning the destination for all your audience-building content. Continue reading

The post What Is the Difference Between Content and Content Marketing? appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/20MVbbA
via IFTTT

A Nutshell Guide to Proper Keyword Research

The importance of keyword research remains steady, but the methods have evolved as search engines grow more intelligent and users change the way they search. Here’s a brief, functional guide to keyword research in today’s environment. Continue reading

The post A Nutshell Guide to Proper Keyword Research appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1r9l0qi
via IFTTT

Thursday, April 14, 2016

19 Free Website Design Tools

There are plenty of free tools and resources to help with your website design, whether you’re just looking for a little flare or you want ...

from Practical Ecommerce http://ift.tt/1WlnBZM
via IFTTT

How To Take Charge Of A UX Kickoff Meeting

UIE Article: Every UX Leader Needs A Unique UX Strategy Playbook

In this week’s article I talk about building a dynamic strategy playbook. Here’s an excerpt from the article: I explained how Saying ‘no’ was an advanced approach for dealing with product teams that waited too long. The basic idea is to tell them you’ll only work with them if they bring your team in early […]

from UIE Brain Sparks http://ift.tt/1S7dG4Q
via IFTTT

Tuesday, April 12, 2016

The Steady UX Diet Versus the Magical UX Pill

By Dashiel Neimark Published: April 11, 2016 “Is the team in a panic and scrambling for a magic UX pill? Or does a consistent intake of UX nutrients support the team’s process?” No, this headline isn’t a joke about the increasing popularity of the term Lean UX. Rather, I am talking about the choices that organizations make in deciding how to adopt User Experience as a practice and improve the experience they are attempting to create. Do they apply User Experience through intermittent, quick fixes to rectify gaps in an experience? Or do they foster UX practices from beginning to end, throughout a development cycle? Is the team in a panic and scrambling for a magic UX pill? Or does a consistent intake of UX nutrients support the team’s process? The UX Diet The UX diet is all about preventative measures. One easy way to identify a team that has a steady UX diet is to see at what point they inject UX into their overall development process. If they involve user researchers and experience designers during a project’s discovery phase, that’s a positive sign. Involving User Experience in the generation of requirements rather than just the amendment of those requirements typically results in reducing the need for such amendments. In contrast, if a team hires a UX professional for a last-call, polish-it-off sort of engagement, the UX diet is likely absent. The driving force behind the UX diet is ensuring more precise, consistent validation of the direction a team is taking. It requires a long-term outlook.

from UXmatters http://ift.tt/1YoVDuM
via IFTTT

What the Past Five Years Have Taught Me About UX Design, Part 1

By Bob Hotard Published: April 11, 2016 “We are fast approaching 2020, the year corporations are holding up as the finish line for the promised land of a digital revolution. What trends are signposts toward the future as we approach 2020?” The decade is half over—so it’s as good a time as any to reflect on what’s important in UX design. We are fast approaching 2020, the year corporations are holding up as the finish line for the promised land of a digital revolution. What trends are signposts toward the future as we approach 2020? After reflecting on my experiences, working as a designer of corporate Web sites over the past five years, I’ve decided to write a series of articles about trends I think will still be relevant in 2020. Plenty of trends have hit since 2010: Responsive Web Design (RWD), Big Data, and wearable technology to name just a few. Five years ago, the focus was on adapting Web designs to iPhones and Android smartphones. Since then, we’ve learned to design for tablets, HD wide-screen monitors, and now, the miniature screens of wearables such as Apple Watch, which was introduced in 2015. Technology and device trends will come and go, but simple, clean, well-tested, Web user interfaces, provide the best user experience across platforms.

from UXmatters http://ift.tt/1UUTJnw
via IFTTT

Articulating Design Decisions

By Tom Greever Published: April 11, 2016 This is a sample chapter from the book Articulating Design Decisions, by Tom Greever, which O’Reilly Media published in October 2015. UXmatters is republishing this chapter with Tom Greever’s permission. Copyright © 2015 Tom Greever. All rights reserved. Chapter 4: Reducing Cognitive Load “Before anything else, preparation is the key to success.” —Alexander Graham Bell When it comes to usability, getting users to successfully complete a task is all about their available brain space: their cognitive load. The more clutter, options, or roadblocks we put in front of them, the more we fill their head and make it difficult for them to complete a task. The same is true when it comes to the task of meeting with stakeholders. Our goal should be to remove as much of the clutter, options, and roadblocks as possible so that our stakeholders’ brains are freed to focus on the primary task of the meeting: getting approval for our designs. If they are distracted by an incoherent outline, grumpy coworkers, or a derailed conversation that has nothing to do with the project, it will be much more difficult for us to complete that task. Our goal is not to just have a meeting, but to make the meeting productive, valuable, and successful.

from UXmatters http://ift.tt/1YoVCad
via IFTTT

Moving to a UX-Critical Culture

By Baruch Sachs Published: April 11, 2016 “Now, more than ever before, I find myself fighting a different kind of fight, to ensure that teams allocate the proper time to User Experience for us to be effective.” With all the amazing changes that have been happening in the business world over the past few years, thrusting User Experience into the limelight, one would think that UX professionals have arrived. That we’d be able to devote enough time, money, and resources to ensuring the user experience is just right—because, you know, it’s important. For decades, we’ve been fighting to ensure that User Experience gets considered during product development. Now, more than ever before, I find myself fighting a different kind of fight, to ensure that teams allocate the proper time to User Experience for us to be effective. When stakeholders say they want something to pop, wow, or sizzle—or use some other silly word to describe User Experience—they’re actually trivializing the work that is necessary to make User Experience happen in a meaningful way. When people refer to UX professionals as magicians, those who are not part of the design or User Experience world begin to think that what we do is easy. But creating an amazing User Experience is really hard work, so we need to start reminding folks—gently, of course; don’t be a blow-hard about it—that what we do is not magic. It requires time and—God, forbid—actual planning to do the job properly.

from UXmatters http://ift.tt/1UUTJnG
via IFTTT

UIE Article – Focusing On What Our Users Shouldn’t Focus On

In this week’s article I talk about authentication as a microinteraction. Here’s an excerpt from the article: Authentication is a necessary evil in today’s world of trust, privacy, and security. It is designed to be selectively usable. A good authentication system needs to be unusable for unwanted intruders. However, it needs to be extremely usable […]

from UIE Brain Sparks http://ift.tt/1MCi1KW
via IFTTT

UIE Article: Misconceptions about Collaboration

In this week’s article Dan Brown talks about how misconceptions can hinder the collaborative process. Here’s an excerpt from the article: Throw smart people together. Suffice it to say that working with smart people is satisfying and challenging. But collaboration isn’t just about smarts. It’s about providing a framework for working together. Just as important as […]

from UIE Brain Sparks http://ift.tt/231EZEN
via IFTTT

Privacy Guidelines For Designing Personalization

Diverse And Engaging Instances Of Interactive Infographic Design

A Simple Web Developer’s Guide To Color

Improve User Experience With Real-Time Features

Better Interface Design: Logins, Menus, Toggles And Other Fancy Modules

A Great Analyst's Best Friends: Skepticism & Wisdom!

Here's something important I've observed in my experience in working with data, and changing organizations with ideas: Great Analysts are always skeptical. Deeply so. This was always true, of course. But, it has become mission critical over the last few years as the depth, breadth, quantity and every other dimension you could apply to data […]

A Great Analyst's Best Friends: Skepticism & Wisdom! is a post from: Occam's Razor by Avinash Kaushik



from Occam's Razor by Avinash Kaushik http://ift.tt/25G09u8
via IFTTT

How to Measure Engagement the Right Way

What does engagement really mean? It’s not clicks, social shares, and time on page. Consider these three alternatives to vanity metrics to truly understand how your audience interacts with your content. Continue reading

The post How to Measure Engagement the Right Way appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1UWwBU5
via IFTTT

Content Marketing: Forget About the 5%

Before you add another tactic, pick a new target audience, or expand your reach, stop and ask yourself: Are we going after a shiny object and ignoring the core of what’s important to our content marketing strategy? Continue reading

The post Content Marketing: Forget About the 5% appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/22K4duA
via IFTTT

A Take on 3 Confusing Terms: Content Marketing, Content Strategy, Content Marketing Strategy

Do you know the differences among “content marketing,” “content strategy,” and “content marketing strategy”? Stop using the terms interchangeably. Let’s explain the differences and similarities, and share why you need to care. Continue reading

The post A Take on 3 Confusing Terms: Content Marketing, Content Strategy, Content Marketing Strategy appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1ZMKGVa
via IFTTT

How One Brand Uses Insanely Useful Content to Help Customers Make Better Decisions

Farmers must analyze reams of data to keep operations profitable. PotashCorp saw an opportunity to provide utility-based content – four web-based calculators – to not only inform farmers, but also influence critical decision-making. Continue reading

The post How One Brand Uses Insanely Useful Content to Help Customers Make Better Decisions appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1Rx1jCd
via IFTTT

How to Document Your Content Marketing Workflow

You can improve your content marketing effectiveness if you document your strategy. Now, it’s time to make sure you document your content workflow – provide a written structure to your processes and increase execution efficiency. Continue reading

The post How to Document Your Content Marketing Workflow appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/1oxLOhK
via IFTTT

Getting Started With Structured Content

Managing your content development and reuse on a case-by-case basis makes sense when you publish a few hundred assets a year. Scale it to thousands and the process gets seriously gummed up. Let structured content come to your rescue. Continue reading

The post Getting Started With Structured Content appeared first on Content Marketing Institute.



from Content Marketing Institute http://ift.tt/20a0h19
via IFTTT

The Cult of User Personae

On alternating Tuesdays, I get to be a young second-generation immigrant woman named Selene with great phone presence and multilingual skills. Or I could be a beefy mid-30s guy named Silas with a buzz cut and a flair for figures. Or any of a few others, or several of them in succession. Every second Tuesday...

from Boxes and Arrows http://ift.tt/1SiP7RP
via IFTTT

Design for Real Life: An interview with Sara Wachter-Boettcher

A note from the editors: A List Apart’s managing editor Mica McPheeters speaks with Sara Wachter-Boettcher about getting to the heart of users’ deepest needs.

Our users don’t live the tidy little lives we’ve concocted for our personas, with their limited set of problems. Life is messy and unpredictable; some days, terrible. When planning a project, it’s important not to let our excitement lull us into blithely ignoring life’s harsher realities.

Discomfort with others’ burdens has no place in good design. We sat down with coauthor and content strategist Sara Wachter-Boettcher (a past editor-in-chief of ALA), to discuss why she and Eric Meyer became vocal proponents of taking users’ stress cases seriously. Their new book, Design for Real Life, goes to the root of insensitive design decisions that fail to support the very users we’re meant to understand and respect.

First off, would you tell us a bit about how the book came to be? What was the tipping point that led you to take on this topic?

SWB: In early 2015, I started writing about the way forms demand users to reveal themselves—and all the ways that can be alienating and unempathetic. In that article, I talk about a couple personal experiences I had with forms: being asked to check a box about sexual assault, without knowing why or where that data would go, and being at the German consul’s office, filling out paperwork that required me documenting a sibling who had died as an infant.

It’d be easy to call that the tipping point, but to be honest, I didn’t actually feel that way. In fact, I had started writing that article the day I came home from the German consul’s office. But I wasn’t sure there was anything there—or at least, anything more than an emotional anecdote. I set it down for six months. The idea kept sitting in the back of my mind, though, so finally, during some winter downtime, I finished it off and posted it, unsure whether anyone would really care.

Turns out they did. I got an endless stream of tweets, emails, and comments from people who told me how much the piece resonated with them. And I also started hearing other people’s stories—stories of ways that interfaces had triggered past trauma, or demanded someone to claim an identity that made them uncomfortable, or made assumptions that a user found alienating. Forms that couldn’t handle people who identified as biracial, product settings that assumed heterosexuality, pithy copy that failed if a user’s current emotional state was anything less than ideal. The examples went on and on.

One of the people who reached out to me was Eric, whose work I had of course also been reading. And that’s really when it clicked for me—when I realized that this topic had touched a nerve across all kinds of groups. It wasn’t fringe. All of us deal with difficult pasts or current crises. Each scenario might be an edge case on its own, but taken together, they’re universal—they’re about being human. And now we’re all dealing with them online. The more Eric and I talked and compared stories others had shared with us, the more certain we were that we had something.

We’ve been talking about user-centered design for decades. Shouldn’t this sort of “sensitivity blindness” have been dealt with by now?

SWB: I wish, but historically, teams simply have not been trained to imagine their users as different from themselves—not really, not in any sort of deep and empathetic way.

That’s not just an issue on the web, though—because it’s a lot bigger than “sensitivity.” It’s really about inclusion. For example, look at gender in product design: crash-test dummies are all sized to the “average male,” and as a result, car accidents are far more dangerous for women than men. Medical research subjects are nearly always men—despite the fact that women experience illnesses at different rates than men, and respond to treatment differently. Of course we’ve transferred these same biased practices to the web. In this context, it’s not surprising that, say, Apple’s Health app didn’t include a period tracker—one of the most normal bits of data in the world—for an entire year after launch.

Identity issues—gender, race, sexuality, etc.—are huge here, but they’re just one way this lack of inclusivity plays out. Eric’s experience with Facebook’s Year in Review tells that story quite well: Facebook long imagined itself as a place where happy people share their happy updates. After all, it’s a platform that until just the other day literally only offered you one reaction to a post: to like it. The problem was that Facebook’s design mission stayed narrow, even as the reasons its users interacted with the platform became more and more varied.

While the web didn’t create bias in the world, I do think it has the opportunity to start undoing it—and I am starting to see seeds of that sown around the web. Digital communication has made it so much easier for organizations to get close to their audiences—to see them, talk to them, and most importantly, listen to them. If our organizations can do that—look at their audiences as real, multifaceted, complex people, not just marketing segments—then I think we’ll start to see things truly change.

Why do you think it’s hard for designers to keep real people in mind? Is it that we tend to be excited and optimistic about new projects, so we forget about the ways things can go wrong?

SWB: Yeah, I think that is part of it—and I think the reason for that is largely because that’s what organizations have trained design teams to focus on. That is, when a business decides to spend money on a digital product, they do it with positive outcomes in mind. As a result, the team is trained on the positive: “how can we make this delight our users?” If that’s all you’re asking, though, it’s unlikely you’ll catch the scenarios where a product could be alienating or harmful, rather than delightful, because your brain will be focused on examples of the positive.

For example, if you try to write a tweet that’s too long, Twitter has this little bit of UI copy that says, “Your Tweet was over 140 characters. You’ll have to be more clever.” Now, let’s say I just tweeted about the amazing tacos I just ate for lunch. In that scenario, the copy is light and funny. But what if I was trying to figure out how to tell the world that a friend just died—or even something more everyday, but still negative, like that I’d been rejected from a job? All of a sudden, that interface feels rather insulting. It’s alienating. Sure, it’s a small thing, but it’s hurtful and can even be degrading. And if you only ever test that feature with pithy sample tweets, it’s pretty likely you just wouldn’t notice.

What Eric and I are really advocating for, then, is for design teams to build a deep breath into their process—to say, every time they make a decision, “who might be harmed by this? In which circumstances does this feature break down for a user? How can we strengthen our work to avoid that?” There’s even an activity we talk about in the book, the “premortem”—where, instead of sitting down after a project ends to discuss how it went, you sit down beforehand and imagine all the ways it could go wrong.

At one point, you and Eric mention that “compassion isn’t coddling.” In the example with Twitter’s snarky copy, someone might say, “you’re overreacting—it’s just a joke.” How would you respond to that?

SWB: I’ve definitely gotten plenty feedback from people who say that this is all “too sensitive” and that we’ll all be “walking on eggshells.” Their answer is that people should just have a thicker skin. Frankly, that’s BS—that mentality says, “I don’t want to have to think about another person’s feelings.”

Coddling someone means protecting them from the world—shielding them from difficult subjects. That’s not what we’re proposing at all. We’re saying, understand that your users are dealing with difficult subjects all the time, even when using your site or service. Being kind means being respectful of that fact, and avoiding making it worse. Think about the normal things you’d do in person—like if your friend were going through a divorce, you’d probably wait for them to open up to you, rather than ask prying questions, right? If you knew someone had just been traumatically assaulted at a specific bar, you’d probably not suggest meeting there for drinks. You’d be compassionate, and avoid making them feel even more uncomfortable or vulnerable.

Humans learn to be good at this in person, but because we don’t know when or if a user is going to be in a difficult emotional state, we seem to forget about this online. And that’s why niceness isn’t enough. Being nice is easy to reduce to being friendly and welcoming. But compassion is deeper: it’s recognizing that people have all kinds of needs and emotional reactions, and our job is to help them, rather than expect them to fit our narrow ideals.

If a team understands that, and wants to be compassionate, how much do they need to do to account for “edge cases”? Is there a cutoff point?

SWB: This is something we talk about a lot in the book. “Edge case” is a really easy way to write something off—to say, “this is not important enough to care about.” Calling something or someone an edge case pushes them to the margins, quite literally. Instead of treating people who don’t quite fit whatever you thought of as “average” as fringe, though, we think it’s a lot more helpful to think of these as “stress cases”: the challenges that test the strength of your design. Because if your work can hold up against people at their worst, then you can be more confident it will hold up for everyone else, too.

Just like in traditional products. Think about the brand Oxo, which makes ergonomic housewares. People love Oxo products. But they weren’t initially designed to suit the average user. They were initially designed with the founder’s wife, who had arthritis, in mind. But by making something that was better for people with more limited ranges of motion, Oxo ended up making something that was simply more comfortable to use for most people. We have the same opportunity in our interfaces.

Our message, though, is that it takes a bit of a reframe to get there: it’s not about “how many edge cases do I have to support?” but rather, “how well have I vetted my work against the stress of real life?”

But won’t that affect creativity, to constantly plan for limiting factors—many that we can’t anticipate?

SWB: You know, no one complains that designing a car to be safer during an accident limits the engineers’ creativity. So why should we say that about digital products? Of course thinking about users’ varied identities and emotional states creates limiting factors. But that’s what design is: it is a creative solution to a set of problems. We’re redefining which problems are worth solving.

Of course we can’t anticipate every single human issue that might arise. But I can’t imagine not trying to do better. After all, we’re designing for humans. Why wouldn’t we want to be as humane as possible? I don’t think we need to be perfect; humans never are. But our users deserve to have us try.

Pick up your copy of Design for Real Life from A Book Apart.



from A List Apart: The Full Feed http://ift.tt/1SjzWYy
via IFTTT