James and I went to Ipswich last week for work. But this wasn’t part of an ongoing project—this was a short intense one-week feasibility study.
When designing for performance means killing some darlings, making hard decisions and realising that it’s not about the design, it’s about the user.
Culture change. It’s a phrase that’s thrown around with reckless abandon these days. Seems like no matter where you turn everyone is looking for a culture reboot.
Typography - it’s at the heart of the web experience but with so many different options available it’s sometimes hard to know where to start when designing. Font stacking, embedding or web fonts? And what’s more important, brand or user experience? And what does this all mean for the designer who just wants to try and make type look great across as many devices as possible without losing their mind?
This week we hosted the Agile SwapShop meet up at Clearleft, and had around 20 people come along to the session. With such a large group of people, and the emphasis being on discussion rather than presentations, it was important to find a method to allow everyone to get involved and provide a useful structure for the conversation. We decided to try out the Lean Coffee method.
A couple of weeks ago we held the second in a series of Roundtable events, where we invited UX leads, product owners and creative technologists from organisations like The Guardian, Auto Trader, RBS and Pearson who are at varying points of the journey of going responsive; to share experiences, troubleshoot, debate and share ideas.
Or why you should be asking “What’s the point?” Design for objectives not for goals.
Andy’s been playing Devil’s Advocate again, defending the much-maligned hamburger button. Weirdly though, I think I’ve seen more blog posts, tweets, and presentations defending this supposed underdog than I’ve seen knocking it.
It’s tempting to think of testing with screen-readers as being like testing with browsers. With browser testing, you’re checking to see how a particular piece of software deals with the code you’re throwing at it. A screen reader is a piece of software too, so it makes sense to approach it the same way, right?
The hamburger menu has gone from handy UI element to social pariah. In this article Andy Budd discusses why some of the criticism may be premature and ill-informed.
Here at the Clearleft towers we use DigitalOcean and our servers run Ubuntu 14.04 and Nginx 1.8.0.
The 20 Second Gut Test is a workshop which can help you discover an initial visual design direction. It helps you identify general design aesthetics and is a good technique to help you get started.
Moving towards consent based decision making builds an environment of trust, saves time and empowers teams.
We’ve started to use a very simple system of ‘Checking in’ for each of our meetings. By taking the plunge and doing it, we’ve discovered quite a few unexpected benefits.
This is second and final of the Hero’s Journey UX Workshop. This part of the workshop is about identifying opportunities to help each hero along their journey and designing value proposition that embody those opportunities.
‘So, how’s your week been?’ ‘Not bad. The project is going pretty well, the client seems happy.’ ‘Sounds like it’s going well. Do I hear a but in there?’