How the semantics of UX change all the time.
“If anything, the T in T-shape isn’t a deep dive into a specific UX sub discipline, and its not to stay within the confines of either research or design. The skill you most want to T shape is the ability transfer the principles of good design across these factors. This is why the broad UX lens is perfectly positioned to engage the ambiguity that comes with design. After all, why put a cap on your abilities? We all have a ceiling but don’t put one there yourself.”
Max Taylor ~ Medium ★ courtesy of @thebrainlady
From UI to UX to (…)
“The user experience of most web-based applications begins well below the interface, all the way down to fields in a database. Examining how systems and users experience time prove this point dramatically. Think about how messy time can be—time zones, leap years, recurring events. As the creators of educational technology, our team learned the hard way about failing to consider the UX implications of time—not just about how time works in technology, but also how our users experienced it in our UI. What follows are some of the technical issues that UX designers should consider about time, along with takeaways and specific methods that can be used to keep the user experience of time at the top-of-mind during product development.”
Michael McLeod a.k.a. @mcleodm3 ~ UXPA magazine ★
Putting a square in a circle?
“Agile and user experience have been partnered successfully since the Agile Manifesto was first authored in 2001 and have had a history of working well together in many situations. However, user experience research (UXR) has been largely unaccounted for in this work. The Agile Manifesto encourages us to revisit our processes and to iterate on ways to better describe how we work together with our teams. That is the goal of this article: to share our progress toward improving how we work by documenting an iteration of a model for you to try.”
Carol J. Smith a.k.a. @carologic, Thyra Rauch, and Hannah Moyers a.k.a. @h_moyers ~ UXPA magazine ★
Design remains team work. Even in guilds, tribes, and other social labels.
“In our busy Agile development environment, our UX team was under-resourced and frequently a bottleneck. We had won the fight for buy-in: People wanted us, but there were not enough of us to go around. So, we were seen as more of an “injustice league” than the band of heroes we wanted to be. Facing the challenge head-on, we successfully leveraged the guild model to scale UX within our mid-sized development organization. We deputized UI developers and QA resources to lighten our design load and to spread good design throughout the land.”
Jennifer Bullard @jbullard and Carol Bergantino @cbergantino20 ~ UXPA magazine ★