Many, many years ago, Tim Berners-Lee wrote this page of answers to (genuinely) frequently asked questions he got from school kids working on reports. I absolutely love the clear straightforward language he uses to describe concepts like hypertext, packet switching, and HTTP.
Questions prompted by the Clearleft gathering in Norway to discuss AI.
A series of questions to ask on any design project:
- What are my lenses?
- Am I just confirming my assumptions, or am I challenging them?
- What details here are unfair? Unverified? Unused?
- Am I holding onto something that I need to let go of?
- What’s here that I designed for me? What’s here that I designed for other people?
- What would the world look like if my assumptions were wrong?
- Who might disagree with what I’m designing?
- Who might be impacted by what I’m designing?
- What do I believe?
- Who’s someone I’m nervous to talk to about this?
- Is my audience open to change?
- What am I challenging as I create this?
- How can I reframe a mistake in a way that helps me learn?
- How does my approach to this problem today compare to how I might have approached this one year ago?
- If I could learn one thing to help me on this project, what would that one thing be?
- Do I need to slow down?
As part of an ongoing series where we ask industry professionals what they use to get the job done, we speak to Jeremy, technical director at Clearleft.
I couldn’t resist the smartarse answer about my “dream setup.”
I’ve made one of them there “ask me anything” things so that you can ask me, well …anything.
I can forgive our answer machines if they sometimes get it wrong. It’s less easy to forgive the confidence with which the bad answer is presented, giving the impression that the answer is definitive. That’s a design problem.
Absolute gold dust from Mike!
I think that having regular 1:1s is really important, but I’m sure I’m not doing them as effectively as I could—the advice in here is going to be invaluable.
There are three types of employees in the world when it comes to disclosing issues:
- Those who will always tell you about problems.
- Those who will never tell you about problems.
- Those who will tell you about problems when asked in the right way.
I love my ones and am frustrated by my twos, but I feel like at least 9 out of 10 people are actually threes.
This is really good fun! And thanks to service workers, it works offline too.
The rounds are:
- Dead or Not Dead,
- Number 1 or Not Number 1, and
- Oscar or Not Oscar.
In which I attempt to answer some questions raised in the reading of Resilient Web Design.
A good range of answers for this year’s question, overlapping a bit with 2011’s What scientific concept would improve everybody’s cognitive toolkit?
Shamefully, I haven’t been doing one-to-ones with my front-end dev colleagues at Clearleft, but I’m planning to change that. This short list of starter questions from Lara will prove very useful indeed.
Eric asked me some questions and I was only too happy to give some answers.
Ignacio asked me some questions. I was happy to answer them.
Just when I think that I don’t get the point of Medium, along comes Dan to show me the light. This thought-provoking thinkpiece isn’t quite on the same level of his seminal groundbreaking kittens work, but I guarantee it will stay with you.
I really, really enjoyed this chat with Conor, especially the quick-fire round.
Note: I’m happy to report that between doing the interview and its publication, I managed to get the redesign of The Session out the door.
Trent and I answered a few questions for the Responsive Design Weekly newsletter.
Wondering whether that network-enabled device of yours is worthy of being considered part of the “internet of things?” Just answer these few short questions.
Markov-generated Quora questions …far more entertaining than actual Quora questions.
A beautifully presented site wherein Ben and Frank endeavour to answer your design-related questions.