Author archives: Kelley McDonald, Senior UX Architect


Content First Design: 3 Reasons Why Lorem Ipsum Isn't Enough

By Kelley McDonald, Senior UX Architect on Jun. 10, 2016 View Comments

The web has always been about content. Sure, people visit websites and use apps to complete specific tasks or interact with others, but it's ultimately the content that facilitates those events.

And while elements like maps, infographics, and videos are considered content, the written word, “real” copy, comprises the great majority of what's actually consumed and exchanged online. Copy is the infrastructure on which digital content and user experience (UX) is built—the glue that holds it all together.

Read More

Native App vs. Mobile Web? The Debate Almost Seemed Over, Until it Wasn’t

By Kelley McDonald, Senior UX Architect on Jun. 2, 2015 View Comments

A few years ago, there was a lot of lively debate about whether organizations were better off developing native mobile apps or browser-based mobile web apps. The relative merits of each were described and compared in-depth, and the underlying assumption was that organizations ultimately needed to choose one or the other (in fact, one of Celerity’s most popular events and its follow-up blog post was focused on just such a decision-making process).

Now, there’s a general sense in the digital community that the mobile web has come out on top.

Read More

Why UX's Time Has Come

By Kelley McDonald, Senior UX Architect on Jan. 31, 2015 View Comments

As a seasoned UX designer, I’ve worked with clients in many different types of organizations to envision new products and services or evolve their existing web properties. The most undeniably successful projects—and therefore the best user experiences—to which I’ve contributed were those that allowed for feedback from both client stakeholders and end users early and often in the process.

Too many times, clients and project teams with whom I’ve worked assumed that they didn’t have the time or money to include formal usability testing, so the whole idea of gathering feedback from end users was abandoned. Likewise, many projects only enabled stakeholders to provide feedback on designs once or twice in the process, and usually only after these designs were fully formed. The result in those situations was an overreliance on one person—me—to solve all design problems and control all facets of the solution. While this has certainly been great for my ego, it has not always been great for the user experience.

Read More