Posts Tagged ‘Process’

We are pleased to present below all posts tagged with ‘Process’.

Designer Myopia: How To Stop Designing For Ourselves

Have you ever looked at a bizarre building design and wondered, “What were the architects thinking?” Or have you simply felt frustrated by a building that made you uncomfortable, or felt anger when a beautiful old building was razed and replaced with a contemporary eyesore?

Designer Myopia: How To Stop Designing For Ourselves

You might be forgiven for thinking “these architects must be blind!” New research shows that in a real sense, you might actually be right.

Read more...

The Messy Art Of UX Sketching

I hear a lot of people talking about the importance of sketching when designing or problem solving, yet it seems very few people actually sketch. As a UX professional, I sketch every day. I often take over entire walls in our office and cover them with sketches, mapping out everything from context scenarios to wire frames and presentations.

The Messy Art Of UX Sketching

Although it’s sometimes easier to start prototyping on a computer, it’s not the best way to visually problem solve. When you need to ideate web site layouts, mobile applications or story board work flows and context scenarios, sketching is much more efficient. It prevents you from getting caught up in the technology, and instead allows you to focus on the best possible solution. Giving you the freedom to take risks that you might not otherwise take.

Read more...

The Big Think: Breaking The Deliverables Habit

Right there in the center of my boilerplate for design proposals is a section that I glare at with more resentment each time I complete it. It’s called “Deliverables,” and it’s there because clients expect it: a list of things I’ll deliver for the amount of money that I specify further down in the document. Essentially, it distills a design project down to a goods-and-services agreement: you pay me a bunch of money and I’ll give you this collection of stuff. But that isn’t what I signed up for as a designer. Frankly, I don’t give a damn about deliverables. And neither should you.

Screenshot

Case in point: for months now, I’ve worked consistently with a particular client for whom I do almost no work on actual design artifacts (wireframes, prototypes, etc.). Rather, I hold frequent calls with the main designer and developer to go over what they’ve done with the product (i.e. poke holes in it) and what they should do next (i.e. help prioritize). Some days, they hand me wireframes; sometimes, a set of comps; other days, live pages. Whatever the artifact, our purpose is always to assess what we have now versus where we need to get to.

Read more...

How To Build An Agile UX Team: Integration

This is the final part in a three-part series on how to build and grow successful user experience teams in agile environments. It covers challenges related to organization, hiring and integration that plague UX teams in these situations. The perspective is that of a team leader, but the tactics described can be applied to multiple levels in an organization.

Agile team working together

For many designers, coming into an agile environment feels like settling in a new country. There are different dialects and new rituals. Furthermore, design is treated very differently than they are used to. It is, in fact, through ritual that a UX designer is able to integrate in their agile team. In addition, it is incumbent on the designer to open up the design process for collaboration and critique from other members of the team. Together, these tactics have the potential to yield a successful agile team.

Read more...

How To Build An Agile UX Team: Hiring

This is the second in a three-part series on how to build and grow successful user experience teams in agile environments. It covers challenges related to organization, hiring and integration that plague UX teams in these situations. The perspective is that of a team leader, but the tactics described can be applied to multiple levels in an organization.

A cross-functional scrum team sketching together

As you build and grow an agile UX team, hiring becomes a central point of impact for the team. Understanding what to look for in designers and how to assess their potential success (or failure) in your agile environment can be tricky. In addition, not all (and potentially none) of your legacy designers will integrate with the agile methodology. Here are a few ways to go about it.

Read more...

How To Build An Agile UX Team: The Culture

This is the first in a three-part series on how to build and grow successful user experience teams in agile environments. It covers challenges related to organization, hiring and integration that plague UX teams in these situations. The perspective is that of a team leader, but the tactics described can be applied to multiple levels in an organization.

Agile Culture

Building any kind of agile team is a lengthy and challenging process. Building a user experience team within an agile organization challenges not only traditional design practices but typical design team dynamics. In this first part, we’ll look at the type of culture that would support a strong UX component in the agile process and how to structure the organization so that designers are most effective and are able to thrive.

Read more...

The S.M.A.R.T. User Experience Strategy

I was a competitive road cyclist for four years. My bikes were good, but my race results were much less impressive. Instead of medals and trophies, all I had to show for it were shaved legs and a farmer’s tan. Regardless, on the road to becoming a competitive athlete, I followed a rigorous training plan with concrete goals. These goals were specific, measurable, attainable, realistic and timely. With this training plan, I was able to quantitatively and qualitatively assess my progress and adjust my routine to match.

S.M.A.R.T. User Experience

In the years since, I’ve hung up my racing jersey and replaced it with a designer’s hat. While wearing this hat, I (and many others) have been told to “create a good user experience.” We’ve heard this in creative briefs, project kick-off meetings and critiques. It may have been a bullet point in a PowerPoint presentation or uttered by someone trying to sell a client or company on the value of their services. But there’s a fundamental problem with stating that your goal is to “create a good user experience.”

Read more...

↑ Back to top