Skip to content

Cornell University

Cornell Drupal Camp
2016

Anthony D Paul

As Director of User Experience at idfive in Baltimore, Anthony D. Paul helps large organizations solve some of their most difficult problems — to define and create great digital experiences and software through usability research, sketching studios, IA concept models, and prototypes of all fidelities. He has concepted business-critical products for Yahoo, US Army, T. Rowe Price, and more—unearthing hairy workflow inefficiencies and audience engagement hurdles. Today, Anthony is helping idfive’s higher education clients remain relevant in a digital world where free and cheap training venues are diversifying competition. He is the co-author of an in-progress book on the future of higher education, wrapping up editing in late 2016.

Twitter: 
@anthonydpaul

Organizing Your First Website Usability Test

You’ve built a shiny, new Drupal site. You asked your grandma and your client if they like it and they both do. However, you’re lying awake at night wondering if you’re missing something—because you know you’re not the end user. You yearn for actionable feedback.

Bringing Order to a Content Hoarder

When timid users step up to your site and are spooked by the ghosts of content past, or those who dare to enter become lost in a maze of composted navigation, a dusting just won’t fix the years/decades of content rot. You know you need to pull everything out to figure out what you have, what to keep, and what to toss—but that can be a daunting and overwhelming endeavor.

Intro to User Journey Maps for Building Better Websites

You’ve asked the right questions and maybe you have some personas. There’s a heap of feature requests from your client and a whole lot of content to organize into a sitemap (IA) document and wireframes. However, something’s not sitting right and you wonder how the site fits into the bigger customer journey with the client’s brand, business, and products.

Lean Requirements Without Skimping on the Meat

In today’s website feature debates, you and your team hash out priorities based on budgets, timelines, and what one of the clients mentioned in passing, ignoring the larger context of the design problem. We focus on the current list of edits—and rallying for the user is lost in the shuffle. In this session, you’ll be introduced to a framework for approaching your Drupal project’s situational analysis from many perspectives, to create success goals that resonate with everyone on your team—including your client’s wallet-bearers.Attendees should walk away with: