Thinking

Step right up folks, and come right on in
This week's weeknotes: They're about to begin!

We are looking for a Lead UX Designer/Product Strategist

In a dramatic twist to last week, this week's weeknotes are early. Gasp. Shock. Awe.

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.

The weeknotes are little late this week (or is it last week?). It's been a busy time, with lots of heads-down immersion in client projects.

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?

By the toll of a billion deaths, man had earned his immunity, his right to survive among this planet's infinite organisms, and that right is ours against all challenges, for neither do men live or die in vain.

For our 100th weeknotes edition, I consulted the oracle (in the form of the Elle Horoscopes website) to find out what has been going down at Clearleft HQ this week.

How did the UN Climate Change Conference reach consensus on tackling the worlds most serious challenge without a backlog of user stories?

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.

Objectives and Key Results—or OKRs for short—are all the rage in Silicon Valley at the moment. So we've decided to start a 6-month experiment to see if they'd work for Clearleft.

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?