cURL error 22: The requested URL returned error: 404 Not Found
Or try one of the following: Afterdawn, Ajaxian, Andy Budd, Ask a Ninja, BBC News, BBC China, Brent Simmons, CNN, Digg, Flickr, Google News, Harvard Law, iTunes, Japanese Language, Newspond, OK/Cancel, OS News, Phil Ringnalda, reddit, Romanian Language, Ryan Parman, Technorati, Engadget, Web 2.0 Show, XKCD, Yahoo! News, Zeldman
Using your status as a speaker to promote others 11 Aug 2020, 11:39 am
Being invited to speak at an event confers some benefits. For newer speakers, the most obvious benefit of speaking is to advance your career. Speaking at an event confers a certain amount of legitimacy and status. The fact that you’re on stage and other people are listening to you implies that you’re somebody who deserves to be listened to; that your ideas hold value that the other people in the audience will benefit from them. This is a great thing to have in your back pocket at interviews, and is sure to impress the person doing the interviewing.
Speaking at a conference also helps raise the status of the company you work for, which is why so many companies are keen to encourage their staff to speak. If you say smart things, the audience will naturally ascribe those thoughts to both you and the company you work for. They’ll think “company X hires really smart people” or “I like the way folks from company X think”. This leads to tonnes of ancillary benefits for the company like finding new customers, attracting new talent, and generally raising the brand even further.
If you come from a recognisable brand, this works the other way around as well. While folks may not have heard of you, they may have heard of the company you represent. This will create a bit of a halo effect around you as a speaker, and confer some of the company’s brand value on to you. “I like the work company X does, this person is from company X, so I’ll probably like them and their work too”. In truth, this is often the way new speakers break into the speaking circuit—by using the value of their employers brand.
New speakers (as well as more experienced ones) also get to benefit from the connections they make—especially with other speakers. They may also get exposed to new job offers from employers in the audience who were impressed with their spiel.
But it’s not all about the person speaking. The very best speakers will usually have something important they want to say.; Something they feel really strongly about, and wish to share with their peers in order to make their lives better. Maybe they’ve just come up with a clever technique that makes folks’ lives easier and want to share it with as many people as possible? Maybe they’ve seen people making the same mistakes over and over again that are easily avoidable if they just do this one small trick? Or maybe they’ve been the brunt of some sort of challenge or injustice and are looking to highlight these problems and drive a deeper systemic change. Whatever their motivations, having a platform is a powerful thing, and something not to be squandered.
As a result of the Black Lives Matter movement, a lot of experienced speakers are looking for ways to do more with their privilege; to use the power, connections and opportunities they’ve been given to raise others up. One simple way to do this is to pepper your talks with references and quotes by peers from under-represented groups. I’ve seen this done a number of times and it can be super effective.
But the more obvious solution is to step aside and recommend speakers from under-represented groups who could take your place. This is an altruistic thing to do. To offer up your place to somebody else who you know would value it more than you.
This approach works, but maybe not as often as it should. Unless the people we recommend get picked, we haven’t made any significant change; we’ve just made ourselves feel good. Fortunately there are a few small, simple things we can do to improve our hit rate here.
The first thing to do is to understand why the conference organiser has reached out to you in the first place. Was it because of a specialism you hold, a talk you’ve done in the past, or a project you worked on; or was it simply down to the company you work for and the position you hold?
Many conference organisers—especially smaller ones—don’t really care about the content you have to offer. They’re simply looking for a speaker from a well known brand to help them sell tickets. In this case it’s really easy to suggest an alternate speaker. You simply say something along the lines of “Unfortunately I’m not available but my colleague X would love to speak”. If you’re lucky, that’s all you need to do.
However these pesky conference organisers probably want to make sure that the person you’re recommending is actually a good speaker, and not just a report who mentioned wanting to do more public speaking in their last evaluation. It’s usually a good idea to send a link to a recent talk from that person, rather than just a list of names. If it comes with a personal recommendation, even better. Something like “I’m afraid I’m not available but I saw X do an amazing talk at Y recently. I think they’d be perfect for your event, so would you like an intro?”
Sometimes conference organisers aren’t just looking for any old speaker—amazing I know. Sometimes they’re looking for somebody with a specific angle to talk about a specific topic. In these instances, it’s helpful to understand what role the organisers wanted you to fill, and recommend a speaker you know can do similar. “I’m afraid that I can’t make this event, but I saw X give a really good talk on the same subject as me at Y recently, and I was really impressed. In fact I was thinking of using some of their ideas in my next talk. Want me to make an intro?”
From a conference organisers perspective, this is probably the perfect recommendation. You’ve had personal recommendations from somebody you trust. They’ve seen the person speak, can vouch for them, and have shared a link to see for yourself. They’ve even said that they’ve been so inspired by that person that they’re going to use some of their ideas in future talks themselves. This person is somebody I definitely want to speak to.
This is great, but what if the people you want to recommend aren’t as established as you? Maybe they haven’t even spoken before. You have an inkling that they’ll be good, but you don’t really know.
If you have somebody on your team who wants to speak at a conference, before giving up your seat and thrusting them into the limelight—or under the bus—it may be worth investing a little more time in their development. Consider spending some time in your one-to-ones to pull out the topics they’d like to speak about. I can’t tell you the number of times I’ve had folks tell me they’d like to speak at one of our events, but then have no clue what they’d speak about (TOP TIP: “Oh, whatever you want me to speak about” isn’t a good answer). Once they’ve got some ideas starting to develop, help them write a talk description, help them put together an outline, help them write a first draft and give them feedback. Find opportunities inside the company for them to speak first, and try and record their sessions if you can. Many a great talk started life as an internal brown-bag session, got honed at community meet-ups, and only then found its place on a conference stage.
You see, developing one of your team as a new speaker is more than just throwing out their names in an email. It’s about investing in that person and helping to transfer some of the skills that have made you such a good speaker over to them.
Another great way to develop new speakers is to suggest that you do a joint talk. The conference still gets to have you on the bill for all the reasons they reached out in the first place, but now they get a second amazing speaker as well. You get to confer some of your legiticancy on them, and they’re going to learn a tonne about being a great speaker from you in the process. This effectively takes ALL—or at least most—of the risk away from the conference organiser, while you use your platform to raise somebody else up. It’s a win-win for everybody involved.
This works especially well if the conference is looking for you to talk about a specific project. Sure you may have overseen the project—and claimed much of the kudos from that Medium article you wrote about it a few months ago—but you know that your team put the hard work in. So suggesting a joint talk where you frame the project, and then have your colleague jump into the details, can work really nicely. In fact I know several well established speakers who started their speaking careers in this way. Very soon they’d eclipsed the person that got them on stage in the first place, and had developed their own stand-alone speaking career.
It’s often harder if the people you’re recommending don’t work for you. It’s worth thinking about why exactly you’re recommending them. Maybe you haven’t seen them speak, but you read a really smart article they wrote a few months ago. Or maybe you’re aware of the work they did on a specific project. Any background you can give about why you’re suggesting them as a potential alternative is better than a list of unqualified names. If you’re unable to confer a sense of equivalence to the conference organiser—that you’re confident that the person you’re recommending would do an equally good job as you—the chance of that person being selected is fairly slim. So the more evidence you can supply to underpin your recommendations the better.
Being invited to speak at a conference is a privilege. Let’s use that privilege to benefit others.
Transitioning to Design Management is Hard, Risky and Requires a Lot of Luck 4 Jun 2020, 11:09 am
There are three common paths into Design Management. Either you start at the bottom and work your way up, you take on a stretch project that elevates you above your peers, or you hit a glass ceiling and are forced to jump ship.
I know a lot of people who have followed the first path. They joined an early stage start-up as its first designer, and four years later are running a team of 40 people as Vice President.
It’s easy to see how this happens. As Designer number one, you’re responsible for hiring designers number two, three and four. For the first 18 months or so you’ve moved from being a regular designer to a lead designer. You understand the design system, and know why certain decisions were made, and everybody comes to you for advice.
When it’s time to hire your fifth, sixth and seventh designer, you’re the one who ends up writing the job spec, doing the interviews, and onboarding the new hires to the team. Once folks start, they report to you, and when they want a pay increase, it’s you they come to first. You probably don’t have the title of manager yet, but you’re effectively doing the job of one.
A lot of career advancement comes that way. You accidentally find yourself doing a particular job, and the title, salary and job description follows 6 months later. Eventually you’re doing so much people management that you move out of production, hire a couple of leads who eventually become managers themselves, and now you’re a Head, Director or VP of Design.
This is a wonderful career trajectory and looks amazing on a CV. However it’s a super hard career trajectory to plan, as a lot of it revolves around joining the right company at the right time. This doesn’t diminish the hard work and effort you put in. It’s just a hard route for others to follow with any certainty.
The next approach is more common inside larger, more stable teams. As a designer you’ll see some sort of opportunity, improvement or trend that you’d like to explore. These tend to be internal focussed opportunities like the creation of a Design System, or the formation of a Design Ops team.
Using your natural sales and leadership abilities, you’ll secure some time and budget. If you’re lucky, the project will be a success, and you’ll end up being put in charge of this new initiative. The powers that be will see this drive, and other leadership roles will soon follow.
This is a great way to prove yourself as a leader, but it comes at some risk. Convincing your company to do something new is always a challenge, and if you fail you’ll lose the trust of your superiors and your status in the organisation. As such, this can be especially hard to do for people from more diverse backgrounds, who don’t feel as secure in their role or their ability to leave and walk into another job with ease.
Unfortunately these opportunities are few and far between, so there’s an element of being in the right place at the right time. There’s also a big element of office politics going on here.
As leaders, it’s our job to find these stretch assignments for our teams, but there’s a good deal of evidence that these sorts of assignments aren’t evenly distributed. That promotion worthy stretch assignments get given to white men more than women—who are often given maintenance assignments—or people of colour. As such it’s important for design leaders to make sure that these opportunities are distributed evenly and judged fairly.
The third most common route into management is through promotion. You’re a great Designer or Design Lead, who continuously goes above and beyond the call of duty. Your design work is stellar and your peers consistently approach you for advice. You know how to navigate projects through your organizations successfully, and your stakeholders appreciate your diligence and hard work. The only problem is, there are no leadership roles available.
While most people assume that they’ll eventually be promoted into a leadership role, this happens a lot less frequently than you’d think. Unless the company you’re working at is growing quickly, you’re effectively waiting for your boss to leave; and while individual contributors seem to move roles fairly frequently, managers stay much longer. As such, the only option is to jump ship.
If you’re lucky, you’ll land your first leadership role at a company with a long history of Design Leadership, a group of peers to learn from, and a governance structure in place. However that often isn’t the case for new managers. Instead they’ll often find themselves being hired by companies with little background in design, as a Player Coach.
On the surface, the Player Coach role sounds ideal. You get to learn new management skills, while continuing to do the design work you know and love. The problem is that management very quickly becomes a full time job, especially when you discover that you don’t have basic things like standard job descriptions, team charters, or progression frameworks in place. You spend so much time working on these fundamentals that your design work and people management skills begin to slip. Very quickly you find yourself stuck in the new manager death spiral, and start wondering whether you did the right thing. Maybe life would be easier if you went back to being an IC.
I’ve seen this cycle repeat itself more times that I care to say. Fortunately this feeling will pass. You’re not a bad manager. You just found yourself in an impossible situation, so it’s time to move on. The best thing you can do is use this experience to land a design management role at a much larger company with an experienced design leader, a supportive group of peers, and all the necessary governance and infrastructure in place.
As you can see, none of these routes into Design Management are especially easy, and a lot of them require being in the right place at the right time. However It’s important to be aware of these common tropes, so you can take advantage of them when they present themselves, or know when to step away when they don’t.
Ghosting Candidates, Marathon Interviews and Zero Feedback: The Modern Recruitment Experience 6 Mar 2019, 12:05 pm
The digital sector is a talent led industry, and as much as I dislike the idea of the 10X developer, the difference a great hire can make to your business is huge. So I’m always amazed when I hear about the shady, sloppy or downright atrocious recruitment practices we inflict on prospective candidates.
There was a time, not so long ago, when you could expect a polite acknowledgement of a job application, an explanation of the process and steps involved, and feedback if you weren’t successful. These days, ghosting candidates seems to be the norm. Hiring managers will claim that they are inundated with responses, so it’s just not possible to acknowledge every application, or inform people when they have been unsuccessful. They’ll also claim that overly aggressive legal requirements and an increasingly litigious environment means it’s no longer possible to provide candidates with feedback. Personally I don’t buy either of these arguments.
The volume of job applications has always been high, and if talking to hiring managers is anything to go by, the challenge they face is having too few qualified candidates rater than too many. While it used to be the case that applicants would apply for jobs via email, a large part of the process has now been automated. So the use of hiring tools with their set processes and templated responses, makes it harder to hide behind the excuse of volume.
I can sort of understand why, if you’ve received over a hundred applications for a specific role, it may not be practical to respond to everyone individually. However if somebody has taken the time to come in for an interview, I think you owe it to them to let them know why they failed to make the cut on this occasion. It’s not only polite—and generally the right thing to do as a human being—but failing to respond with the appropriate level of care and attention can have negative results.
The feedback I’ve heard about interview practices isn’t much better. Overly long, marathon interviews where the candidates are left feeling broken and exhausted by the end. No offers for tea or coffee, no breaks, just a revolving door of stakeholders peppering them with a seemingly random barrage of question. The lack of any coherent narrative makes these team interviews especially torturous. Randomly jumping from topic to topic with no logical segues, or being forced to answer almost identical questions posed by people who weren’t in the room to hear the answer you gave 20 minutes earlier. This unrelenting style of interviewing feels at best like a popularity contest and at worst like a form of interrogation, intended to break the will of an unsuspecting candidate.
In a time where team diversity is an increasingly important consideration, overly combative interview processes that favour certain personality traits like aggression, ego and resilience, seem like an especially bad way to go. While some hiring managers may be impressed by one candidates ability to bullshit their way through a series of essentially random questions, it’s not an especially good indicator of future success.
This brings us nicely around to the issue of interview tasks. Now I’m actually in favour of tasks in certain situations, particularly when you’re hiring junior roles where people have talent, but lack a broad portfolio of work to show. It can also help level the playing field between agency designers with lots of exciting bands in their portfolio, and people who have been in-house for a long time working on a single product. However I also admit that in most cases, tasks are planned and delivered poorly, and can have a negative toll on the recipients.
One big problem with tasks is when they focus on a real problem the company is facing, and end up feeling little more than spec work. Here is a poorly stated problem, and the person who comes up with the answer we like the most wins. Another common problem are tasks that are set a week in advance, and given fairly tight deadlines. Some people will be able to fit this work around their existing work and family commitments, while others won’t. As such, I tend to prefer whiteboard tasks that take place during the interview process itself. Even then, these things are often dropped on candidates without any notice, a process which borders on abusive in my book.
As product people and technologists, we’re meant to have empathy and understand the human condition, yet little if any thought goes into the candidate experience. I guess this wouldn’t matter so much if you had hundreds of qualified candidates knocking down the door, but this often isn’t the case.
It’s easy for hiring managers to forget that candidates are assessing you as much as you’re assessing them. Often more so. I’d argue we’re in a supply driven economy at the moment, where the best applicants will be choosing between 4 or 5 employers. In this situation, it’s your job to sell candidates on your company, and no glossy vision deck or lists of aspirational values will subvert a painful and broken interview process.
It’s also worth remembering that the digital industry is highly networked and super tight. If an applicant puts a tonne of work into an application, undertakes a remote task, and comes in for an interview, only to be ghosted by the company, you better believe they’re going to tell their friends. The old marketing adage goes that a happy customer will tell one of their friends, while an unhappy customer will tell ten. The same is true of the recruitment process.
I know a surprisingly large number of influential people who feel aggrieved towards certain, well known companies, because of the way they were treated during their recruitment process. They’ve told their friends over coffee, shared their experience in closed networks, and put dozens of people off of applying in the future. This isn’t where you want your brand to be.
Even if the experience wasn’t so bad as to be noteworthy, a lot of candidates will feel so bruised and battered by the experience they they’ll be put off from applying again. This is a huge loss as, just because the candidate wasn’t right for you now, doesn’t mean they won’t be right for you in the future.
Not wanting to blow our own trumpet, but at Clearleft we regularly have repeat applicants. Why? Because we try and make the process as humane as possible and give good feedback. We explain what we liked about the candidates–and what they needed to work on–while making it clear that we really valued their time and would gladly consider them for future openings.
So rather than ghosting or hazing candidates, and leaving a bad taste in their mouths, we need to try and create the best recruitment experience possible. So even if the candidates aren’t successful, they leave thinking that you’d be a great company to work with, will recommend you to their friends, and jump at the chance we a future job opportunity comes along. This isn’t just a case of playing the long game—It’s the fair and decent thing to do.
Personas aren't bad, and you're not a bad designer if you use them 20 Feb 2019, 5:19 pm
With disturbing regularity, my Twitter stream seems to explode with posts demonising commonly used, yet seemingly harmless design tools. These posts take great pains to document all the ways these tools have failed people in the past (while downplaying or ignoring situation where they may have helped). Reading one of these threads you’d be forgiven for thinking these tools were actively harmful; some sort of public health nuisance this brave whistleblower was uncovering for the first time. Although they generally read more like the hysteria surrounding MMR vaccines to me, rather than any reasoned or measured debate. Instead they’re full of personal anecdotes and half truths, wrapped up in a thin veneer of scientific speak. One such debate I witnessed recently revolved around Personas.
Now the love/hate debate around personas is nothing new; in fact it’s been rumbling on for some time. I personally have no great love for personas—that would be a little like loving a hammer or a chisel—but I have no great hate for them either. Personas are tools like any others, with their own relative strengths and weaknesses. So while every few months a new tool comes along claiming the previous one is now dead–in this case Jobs to be Done—I’m much more interested in developing a rich toolbox of tools to draw upon, than engaging in a Battle Royal style deathmatch. That is to say, I’m not on team persona, team JTBD, or any other team that may be having its moment in the sun. Instead I’m on team human.
Whenever the vilification of persona’s pops up its ugly head, it always goes something like this. “Personas are bad because they’re usually made up and therefore have no empirical backing”, “Personas are bad because they try and segment people and people are too unique to be segmented”, “Segmenting people is bad on principal and tantamount to discrimination”, “Personas are just a bunch of demographics and are therefor completely useless”, “Even if personas aren’t just a bunch of demographics, they are so badly used that we should just stop using them”.
While all these arguments annoy the hell out of me, the last one is the worst. The idea that because something is badly used, we should ditch it, is a blatant call for ignorance. Personally I think if something is poorly or wrongly used, it’s our responsibility as experts, craftspeople and educators, to help people understand how a particular tool or technique works, rather than just throwing it–and the people using them—away like yesterdays garbage.
So let me address some of these other common misconceptions about personas. The first and most pernicious is the idea that personas are just a bunch of—often made up—demographics featuring a persons age, gender, job, hair colour and little else. Now if this was the main content of personas I could understand the frustration. However that’s just not the case.
I think this misconception comes from the world of marketing, where marketing personas generally are more focussed on demographics. That’s because marketing personas are generally used to try and capture, understand and categorise fairly broad ranges of preferences, and then understand where people holding those preferences spend their media browsing time, to better focus marketing spend. That’s all well and good for our friends over in marketing, but this sort of approach provides very little value when it comes to Interaction Design.
Instead, the use of demographics in personas is really there to add a bit of background detail, to make these pen portraits a little more realistic and memorable. This is because the true value of personas is a communication tool. As a way of synthesising a large amount of rich and complex data, generated through observations, interviews and surveys, into something that can travel around an organisation, and be consumed by people who weren’t necessarily involved in the conversation, or even have regulate access to customers. In these situations it’s helpful if the persona is recognisable as person, with a name, a background story and a set of attitudes and beliefs.
The question then is, if personas are a communication tool, what are they communicating? Well in general, the most useful part of any persona is the User Scenario; the area on the page that describe the sort of problems these users are facing, the behaviours they exhibit, and if you want to use that particular language, the jobs they want to get done.
I think this is one of the reasons why a lot of people claim that Job Stories and JTBD do away with the need for Personas, and I think in some situations that may be true. If you’re working in a fast moving engineering focussed start-up, servicing an incredibly wide demographic with a similar set of needs, and everybody in the company is very user centric and in touch with those needs, you can probably do away with the touchy-feely fluff and focus on the core jobs; it’s just a lot of unnecessary distraction.
However if you’re working in a traditional organisation serving a smaller range of fairly distinct behaviours, and you need to get your stakeholders out of the mindset that all customers think and behave the same, or worse, all customers think and behave the way the executive team do, personas may be of some use.
In some way you could argue that personas and a useful step on the journey towards JTBD, but if you’re already there, they probably hold little additional value. Personally I like the ability to reference John, Mary, Prisha, or Joaquin as a placeholder for a set of behaviours, rather that sifting through half a dozen job stories to explain what set of problems we’re solving for today. It’s efficient and and travels well, even if there is a certain loss of fidelity.
The best personas generally are based on research data. You’ve surveyed hundreds or thousands of customers, you’ve interviewed dozens more, you’ve crunched the data and found certain patterns. Maybe you’re a travel company and have noticed that parents and children tend to travel shorthaul for a week or two, over the school holidays? Maybe the data has surfaced another cluster of younger travellers who prefer cheap city breaks, anytime other than the school holidays. Maybe you discovered a third cluster of people who travel for business and generally (but not always) fly business class, use the lounge and prefer to be back home for the weekend. This is a fairly trivial example, but I hope you get my drift.
Knowing this information may allow different product teams to tailor different experiences for different clusters of behaviour. This obviously beats treating every customer as the same, but isn’t as good as building up a rich and individual picture of behaviour by acquiring tonnes of data about the user, and feeding it into a sophisticated CRM system. Many tech firms have these capabilities, which is another reason why they probably look down on personas and those who use them. However you’d be amazed how few traditional businesses are able to significantly alter the merchandising offering, let along the whole user journey, based on detailed data capture.
Now it’s worth pointing out that nobody is saying that you can’t be both a business traveller, a city breaker, and somebody who is looking for a fly-and-flop holiday with their family. Similarly while the Personas my suggest that city breakers tend to be younger than people traveling with families, the actual data shows considerable overlap. In fact you may find a cluster of retirees who take their grandchildren on holidays on their own, and also like city breaks.
Fortunately personas aren’t rigid definitions, but rather porous archetypes, so people will move between the two. Something this will happen over years. Other times it will happen in a single session. The key to any successful model is realising that it’s only a model, and therefore has limited scope. Sometimes it’s useful to think about light in terms of a wave, other times in terms or a partial. A good craftsperson understands the strengths and weaknesses of each model and uses it appropriately, while a poor craftsperson generally blames their tools.
Which comes on to my last point, the inevitable cargo-culting of any and all design tools. As a quick recap, cargo cults emerged amongst Pacific Islanders who tried adopting the object and rituals of western colonial power, without realising how things really worked. So they would build wood and reed airplanes, control towers and airport terminals, in the hope that American GIs would return with their cargo, without realising the intricacies of world politics, aviation, and international trade. They basically just copied what they saw other people doing in the hope it’d work.
I see this all the time in our industry. You read an article about personas and throw up some badly researched, demographic heavy documents. You then use them to prover the validity of your pet feature to a bunch of skeptical engineers and business people, and wonder why it failed. It couldn’t have been you, it must have been the tool, so you go to Twitter or Medium and vent your anger at the uselessness of Personas.
It’s frustrating to see people behaving this way, and if it was just themselves they were hurting, I wouldn’t mind as much. However when these things below up, the outrage and misinformation tends to travel much further than a reasoned argument about the pros and cons of a certain tool or technique ever could. The resulting blast radius is huge, and a lot of innocent people often get caught up in the ensuing chaos. After all, if you were a relatively newly minted designer and somebody you trust with 20k followers on Medium, tells you that the thing you were taught as school is no longer useful, and all the smart people are now using something else, what are you going to do? Well, you’re probably going to ditch one tool in favour of the other, and may go around telling others to do the same. This is how MMR scares and market panics start.
Fortunately we’re not dealing with anything nearly as serious here, and at least you’ll end up with a tool in your tool box. However as the saying goes, if all you have is a hammer, everything looks like a nail. Even if you spend most of your time hammering nails into blocks of wood for a living, I think it’s worth understanding what a screw looks like, and when to use it, rather than trying to hammer a screw into a block of wood once or twice and then claiming that screws are rubbish.
As a professional we all benefit from having a variety of tools at our disposal, instead of falling for the hype around silver bullets and one size fits all solutions. We’d also benefit from a bit more critical thinking in our industry. Arguments that go along the lines of “This thing hasn’t worked for me, so it cannot work for anybody” are super reactionary. They stifle intellectual curiosity, rather than encouraging people to expand their horizons and learn new things.
If you’ve discovered a new tool that works for you, by all means share what you think is great about it. Similarly if you’ve found legitimate weaknesses in existing tools, please share that information so we can all learn and grow. However we live in incredibly polarising times, and debate through opposition is super easy. Just remember that it isn’t always necessary to raise one thing up by knocking something else down. That it’s a large world out there and we benefit more for variety and choice than a limited set of (largely manufactured) binary opinions.
On Food (and my 50by50 challenge) 11 Jan 2019, 12:45 pm
I’ve always been somebody who has favoured experiences over objects. The buzz you get from buying a nice watch or a fancy pair of shoes fades pretty quickly, even if the utility remains. However the memories you form from that city break to New York or that diving holiday in the Maldives last a lifetime, or at least until you memory starts to fail. Research into the field of hedonic psychology backs this up. There’s a general belief that you get more bang for your hedonic buck when buying experiences over material positions—just one of the many things our Millennial friends have got sussed.
For me, one of the best ways of capturing a strong memory is having a great meal at a top-notch restaurant with a small group of friends. There’s something amazing about the art of hospitality—of making people feel warm, welcome and comfortable. From a UX perspective, I find so many parallels in the art of hosting and the art of creating digital experiences; the sense of occasion, the focus on small details, the dedication to craft.
Of course, these meals can be pricey, so I realise what a fortunate position I find myself in. That being said, I’m often surprised nice restaurants don’t charge more; especially in comparison to some of the expensive, but un-noteworthy meals I’ve had in the past. In my experience a top end restaurant serving an eight or twelve course tasking menu will cost about twice as much as my favourite local bistro offering a starter, a main course and a desert. So for the cost of two nice but largely unmemorable meals, you get to have a three to five hour gastronomic experience that will stay with you forever. Good value hey?
Over a post conference dinner with a couple of friends last year, we bonded over our mutual love of food. Whenever we found ourselves in a new city, we’d try and hunt down an interesting restaurant to dine at, and one of the easiest ways to do this was by picking a restaurant with a Michelin Star. Now there’s a lot to be said about the Michelin star system, both for and against. Not every good restaurant has a star, and I’ve been to several “starred” restaurants which over promised and under-delivered. However if you don’t know the culinary scene in a particular city, it’s generally a safe bet.
A few years earlier I’d discovered another restaurant rating list called The Worlds 50 Best Restaurants. Rather than restaurants being reviewed by professional reviewers with a strict set of criteria, this list was compiled by industry experts; chefs, restauranteurs, food writers and critics. I’d eaten at a couple of the restaurants on this list already, and had been super impressed. I told my friends about this crazy idea I had of trying to eat at 50 of the best restaurants in the world by the age of 50. Much to my surprise and delight, they thought this was a great idea, so we’ve ended up egging each other on to undertake this task.
Over the past 12 months I’ve eaten at 7 restaurants on the top 50 list; The Clove Club, Restaurant Tim Raue, Odette, Attica, Alinea, Le Bernardin and Eleven Madison Park. The year before I’d also eaten at The Ledbury, Septime and Lyle’s, brining MY grand total to 10. I’ve two more restaurants booked for early next year, and have a couple more I’m lining up once reservations open.
One of the things I’ve enjoyed most about this undertaking so far, it’s it’s ability to bring folks together around food. Normally when I travel to cities for work, I’ll reach out to groups of people I know in that city to arrange brunch, dinner or drinks. However if you live in a city like New York, you’re always getting folks passing through, so it can be difficult making enough time. Especially if you have life to get on with. If, on the other hand, you’re into food and somebody says that they’ve just secured a hard to get table at a restaurant you’ve been anting to try for years, people find a way to make that happen.
I generally book a table for 4-6 people, put the word out, and see who fancies joining me. As a result the dinners are usually a mix of super interesting folks, some of whom know each other already, and some of whom don’t but really should. As such, it’s fun playing matchmaker, and seeing new friendships form.
While many of the restaurants are in easy to reach cities like London, Paris and Barcelona, a few are in more exotic or off-beat (for me anyway) locations like Shanghai, Mexico City and Lima. So another big draw is having an excuse to go and visit these places. There are also a few places like Moderna in Italy or San Sebastian in Spain which I hadn’t considered visiting before, but now I am.
As the lists changes each year, I’m not going to be able to eat at every restaurant on the list in my 50th year. However by the age of 50 I hope to have eaten at 50 amazing restaurants that were on the list the year in ate in them. Oh, and if you were interested, I’ve 4 years left to accomplish this task, so it’s doable, albeit tricky.
That’s where I need your help dear readers. If you’re a friend, happen to live in one of these cities and would like an excuse to have a nice meal, drop me a line and let’s get our dates synced up. If I don’t know you, but you’d like to take me out for a meal at one of the restaurants on this list in return for some free mentoring or advice, consider me interested; and if you’re a conference organiser arranging an event in one of these cities, we should definitely chat.
On Travel 2 Jan 2019, 12:51 pm
I grew up in a pretty standard working class family. My father was a glazier while my mother looked after me and my two brothers. We lived in a nice, 3 bedroom council house, on a friendly estate. My parents worked hard to give me access to things they didn’t have as children. That meant a home full of books, weekend trips to museums, and regular holidays.
Summers were spent in the U.K. Mostly in the West Country, but occasionally we’d venture further afield; to Wales, The Lake District, and the Yorkshire Dales. I relished our family trips and felt super lucky, as few of my Friends had seen as much of the country as me.
I had one friend who’d been on holiday outside the UK. He’d had a two week trip to California and I loved hearing his stories from the land of CHiPs and Beverly Hills Cop. The huge meals, the gigantic freeways; it all sounded so exotic. However his dad had an office job and they owned their own house, so overseas travel clearly wasn’t on the horizon for me. Yet one can dream, and dream I did.
Being a child in the 80s, I grew up on a diet of James Bond and Indiana Jones. Watching these heroic figures hop from exotic country to exotic country with seeming ease. I dreamed that one day I’d be able to visit places like Hong Kong or Shanghai, but how was a kid from a council estate going to make that happen? I reasoned that the only way somebody like me would get to travel was if I ferried other people there, so I set out to become an airline pilot.
I went to Manchester University to Study Aeronautical Engineering but quickly realised that being a pilot wasn’t for me. At the time, the majority of airline pilots were ex RAF, and doing 20 years military service didn’t really appeal. British Airways took on a small number of graduate trainees, but competition was stiff, and they seemed to favour applicants from specific backgrounds. The only other option was to pay your way through training, and that wouldn’t have been possible for somebody from my background.
Fortunately I was starting to go off the idea anyway. There’s an old adage that being an airline pilot was ninety nine percent bordom, punctuated by one percent sheer terror. I also had a friend whose dad was an airline pilot and she talked openly about his drinking problems and tendency to have affairs with the cabin crew—something of an occupational hazard I later found out. Neither of these things sounded like a lot of fun.
Around the same time I met a couple of people who’d been on a gap year before University. Being one of only a handful of kids at my schools to go on to University, I hadn’t realised this was something you could even do. Hearing their stories about trips along the Mekong River and full moon parties in Thailand sparked my sense of adventure. So once University was over, I saved up some money doing low paid jobs, and went off travelling.
Looking back it’s amazing how much your environment and the people around you fix your perception of what’s possible.
That first 6-months travelling around South East Asia really opened my eyes to the wonders of the world, and the possibilities that existed. I loved experiencing different cultures and seeing how others lived. I also met people from a variety of backgrounds, opening my eyes to a range of career options I never thought possible. I was hooked.
6 months turned into a year, then two, then three. I learnt to dive in the Indian Andaman Islands, did my Dive Master on Koh Tao, and became a Dive Instructor in Phuket. I led dive expeditions on the remote islands of Indonesia, ran a dive school on Koh Phi Phi, and did a stint as a dive guide on the Great Barrier Reef. This helped fill my coffers, working the high seasons and then using the money to travel the rest of the year. It was on one such trip to Singapore that I discovered Web Design was a thing.
Arriving at the hostel late one evening, there were only two other people still awake. A British guy and a French dude in lycra who I later learned had just cycled to Singapore from Paris. We got chatting over beer and the British guy said that he was a Web Designer. At the time I didn’t know you could actually create web pages, let alone make a living from it. The British guy explained that it was super easy. All you needed to do was learn this thing called HTML and you could make tonnes of money in London. This was in the hight of the first dot on bubble, allowing my newfound friend to work for 6-months and travel the rest.
As somebody who’d always had an affinity for computers—I was the first person in my school with a ZX81 and would regularly spend my lunchtimes playing snake on the BBC
micro while everybody else played footie outside. So I set about learning web design from sites like Ask Dr Web, using cracked copies of Dreamweaver and Photoshop from coverdisks of tech magazines. The rest, you could say, is history.
Somehow I’ve managed to build a career that involves a fair amount of travel. Last year I visited Singapore, Wellington, Tokyo, Hong Kong, Melbourne, Chicago, Berlin, Amsterdam, Norway, Stockholm and New York for work. I’ve also visited Rome, LA, Palm Springs, Vegas, and The Maldives for pleasure. All in all I’ve had a spectacular year or travel!
This year is also shaping up to be a fun year. I have work trips to Copenhagen, Seattle, Seoul and Japan arranged for the spring. I have a couple of potential speaking engagements in India and South Africa which I’m waiting to confirm, and am tentatively planning a holiday to Ibiza, a road tip in the US, and a long weekend in Marrakesh in the second half of the year.
While I’m not a millennial, I think I have millennial sensibilities—possibly a product of growing up on the Web. For instance I’ve never been a huge fan of acquiring stuff. My movies are through Netflix, my music through Spotify and my transport (when not walking or using public transport) is through City Car Club. As such, the bulk of my disposable income is spent on renting services and buying memories, be they food, travel or live entertainment. So yes, I’m somebody who would rather have a nice brunch of avocado on toast on the weekend, then save up for a 65 inch OLED flat panel TV or statement car (I should add that this isn’t to dismiss anybody who does want to spend their money on physical possessions, it’s just not how I’m wired).
I feel incredibly privileged by all the travel I’m able to do, and can’t imagine what 12 year old me would think of the life I’ve somehow made for myself. However I’d like to think it’s everything he dreamed it would be, and more.
Breaking into the speaker circuit 6 Aug 2018, 11:19 pm
As somebody who both organises and speaks at events, I’ve got a good insight into the workings of the conference circuit. This is probably why I regularly get emails from people looking for advice on breaking into the speaking circuit. So rather than repeating the same advice via email, I thought I’d write a quick article I could point people to.
First off, breaking into the speaker circuit can feel intimidating. If you look at the line up of most international conferences, they’re packed with veterans speakers from well known brands. It’s easy to feel that the speaker circuit is already locked down and there’s no way to break in. However it’s worth noting that every veteran speaker was in your shoes at some stage. In truth, audiences get bored of the same old faces pretty quickly, so conference organisers feel a huge pressure to find new speakers from diverse backgrounds. As such, conference speaking is surprisingly egalitarian, and talent rises to the top surprisingly quickly.
Conference speaking can be a lot of fun, but before you start dedicating too much time and effort becoming a speaker, it’s worth thinking about your motivations. There are a lot of reasons why people choose to speak at events, and there’s no right or wrong answer. However the most common motivations I see include:
- Having a unique specialism you want to share.
- Giving something back to the community.
- Having an excuse to learn a new skill.
- Frustration by the status quo.
- Not being able to afford to attend conferences unless you speak.
- Building up your personal brand.
- Increasing your perceived employability and finding work.
- Promoting your company or consultancy services.
- Travelling the world.
While all the above reasons are perfectly valid, focussing on the intrinsic benefits of public speaking like a desire to help people, share knowledge and to push the industry forward, will lead to a longer and more fulfilling speaking career. Conversely, if you focus on extrinsic reasons like building a person brand or landing that next job, you’re more likely to stop once those goals have been met. Either way, public speaking is incredibly rewarding, so let’s look at where to start.
I regularly get emails from people wanting to speak at one of my events. When I ask where they’ve spoken before and what they speak about, the answers are often the same; they’ve not actually spoken anywhere before, and don’t have anything specific they want to talk about (worse is when they ask you what you want them to speak about, when you have no idea what they’re actually good at). This is a relatively new phenomenon, and it seems that speaking has gone from being a means to an end, into an end in itself.
So my first piece of advice would be to think deeply about the topics you want to talk about. If you have a particular skill, passion or experience you want to share, that’s great. However there’s a misconception amongst a lot of people that you need to be an expert to speak. While knowing your topic is important, you don’t necessarily need to be the most experienced person in the Universe on your chosen subject.
There’s a strange irony that the most experienced people in a particular topic are often the worst communicators, while those relatively new to a field can be great at explaining things, because they’ve recently gone through the process of synthesising the information themselves. As such, great storytelling usually trump superior domain knowledge.
There’s no point being a great storyteller if you don’t have a good story to tell, so its worth thinking about the particular point of view you bring to the topic. Do you have recent experience in the subject matter? A project that went well of badly? A technique you’ve developed, or a perspective that’s slightly different from the norm. It doesn’t matter if you’re talking about something that’s been spoken about before, as long as you’re bringing a new and interesting perspective to the conversation.
Its also worth mentioning that just because your topic have been done by other people, doesn’t mean that everybody knows the subject inside out already. There’s a tonne of new people entering our industry every day, so there’s always a market for seemingly obvious stuff. In fact, I have no problem finding people to talk about cutting edge techniques at my conferences, but I really struggle finding people to talk about foundational skills. So don’t think you have to have something unique before you start talking about it.
Another common mistake new speakers make is coming up with a new talk for every event. Public speaking is a learnt skill, so the more you do it the better you get. That means that the first time you do a talk will probably be the worst time, and as you do it more and more, you’ll get better and better. You’ll learn which parts of the talk work well, and which bits need tweaking. You’ll see where people laugh, and where they don’t, and use the feedback k to improve things the next time you speak. As such I generally find I have to do a talk three or four times before I’m happy with it.
A lot of professional speakers will have 3 talks on the go at any one time. They’ll have a talk that they’re just debuting, a talk that they’ve been doing for a while and really happy with, and a talk that was super popular a few years back, but they are slowly running down. The new talk will be reserved for smaller conferences or conferences looking for fresh material, the main talk will be for the big events looking for a surefire hit, and the older talk will usually be the one you’ll do for free at local events.
As I mentioned earlier, I’m seeing a lot of new speakers expecting to start right at the top, with the big international conferences. I’m not sure if there’s an x-factor type level of expectation here, but most of the good speakers I know started building their reputation and learning their craft by talking at small local meet-ups. After a few years they’d start speaking a local and sometimes national conferences, and only start being invited to speak at bigger international conferences after a good few years on the circuit.
This is similar to bands and comedians, who spend years learning their craft in local bars and comedy clubs, before getting the big TV spots and stadium gigs. As such, my advice would be to start small, get in loads of practice, and work up to the bigger conferences and events over time.
Public speaking can be a nerve-racking experience, and even the most experience speakers feel stressed before going on stage, In fact I have a few friends who are literally nervous wrecks in the run up to their talks, wondering why they put themselves through the stress, and swearing that they’ll never speak again. Yet the moment thay step on stage something changes, and as an audience member you’d never know the stress they were going through back stage.
A small amount of nerves are arguably a good thing, and can act as a performance enhancer. However there are lots of “tricks” that can help you combat the inevitable stress of public speaking; exercise in the morning before your talk, listening to music backstage to get in the zone, or just being quiet and peaceful before your session, in order to blank out any fear and self doubt. Whatever techniques you use, things do generally get better with time and experience.
My top tip for getting over nerves isn’t anything especially revolutionary. I just try to memorise the first few minutes of my talk, so when I get on stage I can do it confidently and eloquently. It usually takes a few minutes for the nerves to subside, and for you to hit your stride. So nailing the first few minutes, usually helps.
The other little secret is the best speakers often get coaching. Public speaking is a performance, and generally get’s better through active improvement. So training and coaching can help you structure more engaging talks, develop a good stage presence, increase your vocal range, and generally improve your delivery and confidence. So no matter what level speaker you are, whether beginner or expert, consider getting some external help.
When you’re ready to move from smaller local events to larger conferences, organisers are looking for three things, generally in this order.
- Confident speakers who are able to tell a great story.
- A really interesting topic that fits with the current zeitgeist.
- Well known speakers or speakers from well known brands, that will help sell tickets.
Mostly, conference organisers are looking for people who can demonstrate expertise, so if you are reaching out to organisers to suggest your services, you need to understand their conference, the audiences it attracts, and the topics that will be of interest to them. If you’ve been to the conference before, let them know. If you haven’t been, maybe you should consider buying a ticket this year, and then suggesting yourself as a speaker next year. It’s always more flattering as a conference organisers when the person genuinely knows the event, rather than bulk emailing a list of conferences they got off lanyard. Even worse is when the person’s assistant or PR firm reaches out, as it demonstrates that person is to busy or self important to bother reaching out directly. This anonymous shotgun attitude always gets a black mark in my book.
If you’re already an experienced speaker with a good reputation, organisers will mostly know who are are, and what you talk about. If not, you’re going to need to give them a couple of possible talk ideas, along with a video or two of you speaking. If you don’t have videos of you speaking, it’s going to make your lives a lot more difficult as the organisers want to minimise risk and be sure that you’re going to do a great job. So consider recording a version of the talk when doing a run-through for colleagues or friends. Failing that, offer to drop by the event organisers office to run the talk by them in person. Organisers get dozens of unsolicited talk requests, so you need to make their jobs as easy as possible, by demonstrating how good you are and the value you can bring to their event.
When preparing talks, I usually allocate 1-2 hours of preparation for every minute of the talk. So a 45 minute talk would take me 90 hours (roughly two weeks) to pull together. The more you do it the quicker you’ll get. A lot of novices don’t realise the time it takes to put together a great talk, and will skimp on prep. In fact I see a lot of novice speaker (and embarrassingly some experienced speakers) bragging at speaker dinners about how little effort they’ve put in the talk. Even worse is when they get up on stage and say to the audience that they were finishing their slides off the night before.
While we’re all busy people, this unpreparedness is unprofessional and disingenuous to both audiences and event producers alike. So make sure you put enough time into the preparation of your talk, and run through it at least 3 or 4 times before you present to a paying audience.
Lastly, if you are a novice speaker, asking for a fee can be tricky. It’s amazing how many conferences don’t pay their speakers, or even cover expenses. In fact some conferences still expect speakers to pay for a ticket. While it’s tempting to speak for free, in exchange for the “exposure” you’ll get, this makes it harder for other speakers. Especially ones who are having to take time off work to speak at the event, or dip into their own pockets to cover things like childcare. So when you’re approached to to speak at a conference, it’s always a good idea to ask what package they can offer, and not necessarily take “no fee” as the first answer.
Of course you then have to decide what your fee should be. Whatever it is, you’ll be lucky if the fee covers your time out of the office, let alone the time it took for you to put the talk together. One way to look at it is to assume you’ll probably give the talk a half a dozen times, and spread the cost over a a number of events based on a rough day rate. Another way to look at it is to pick a fee that a low multiple of the average ticket price. At the end of the day there’s no perfect way to set and negotiate fees. It’s something that comes with time, practice and a certain level of experience.
I hope this article has given you a few ideas for whether public speaking is right for you, and if it is, how to go about breaking into the speaking circuit. In my experience, conference speaking is a highly rewarding thing to do, and its fun being part of a smart, supportive and diverse community of speakers. So I wish you all the best on your future speaking career, and hope to see you on stage at a conference soon.
Reoccuring billing, and forgetfulness as a dark pattern 1 May 2018, 11:16 am
Five years ago my company was pitching for a newspaper project, so I decided to sign up for a bunch of newspaper subscriptions, including the Times. I was really impressed with the thought and consideration that had gone into both their Web offering and iPad app, so used it constantly for about a month. Once the pitch had finished, I stopped using the service, and my attention drifted elsewhere.
Today, I received a threatening email from the Times saying that my last payment hadn’t gone through and if I didn’t do something about it, they were ominously going to “take action”. I immediately felt a knot in my stomach. Had I accidentally been paying for the subscription all this time? How could I have not known? I felt stupid, I felt gullible, I felt angry and betrayed.
It would be easy to blame me for my own stupidity, and a do take a good deal of responsibility. After all, shouldn’t I be checking my bank statements each month for erroneous payments? I’m sure a lot of people do this with their personal accounts, but I genuinely struggle to find the time. It’s even harder with company accounts. With so many transactions are going though each month, it’s easy to miss small anomalies. Especially when the person managing the accounts isn’t the person making the payments. When this happens, associations easily get divorced.
For the majority of online services I use, this isn’t a problem. I’ll sign up with an email address and be sent a handy invoice or billing reminder each time money is taken. This lets me know that I’m still a subscriber, and reminds me to use the service and get the value I’m paying for.
This wasn’t the case with my Times subscription. They kept dutifully taking money from my account once a month, without informing me this was happening. Understanding that memory is fallible, it’s inevitable that people will eventually forget some of the subscriptions they’ve signed up for, and without these billing reminders, people like myself will find themselves accidentally paying for services long after they’ve stopped being useful.
It’s entirely possible that this was simply an oversight from the Times, and there was no malicious intent. However it’s interesting to think that of the two possible approaches—remind or don’t remind—the former massively favours the customer as it prevents them from forgetting subscriptions, while the latter hugely favours the company as they constantly get to extract money from people who have accidentally forgotten their subscription, and would otherwise cancel. So you can’t help but wonder whether an ambitious product manager made a deliberate decision to avoid subscription reminders, in an attempt to maximise revenue.
Even if this was a genuine oversight, and not a deliberate dark pattern, I cannot be the first person to have forgotten they were paying for a service they weren’t using. Especially with the increasingly ageing population of Times readers. As such, I suspect the customer service team must get a handful of such calls each week, if not each day.
Oh, did I mentioned that the only way to unsubscribe was by phone, despite being able to sign up online. This is another well known dark pattern. Making it super easy to subscribe to something, but relatively hard to unsubscribe. As such. I’m sure a good portion of people phoning up to unsubscribe get fed up waiting 15 to 20 minutes for an answer, decided they’d phone back another time, then dutifully forgot again.
Being a known problem, this would be a relatively simple thing to fix. For instance, you could send customers a gentle reminder on the anniversary of their subscription. That way, if customers were to forget, this would give them an opportunity to re-enguage with your service, or cancel if they no longer wanted to use you.
A more sophisticated approach would be to notice that people hadn’t logged in after a set time, like 3 months, and put peoples accounts on hold. This is a really nice approach as it shows a duty of care to your customers, while still keeping the option open that they’ll re-enguage.
Of course this all depends on having the will to make these improvements, especially if the result could mean a drop in income. So for many companies it’s just more convenient—and more profitable—to ignore these edge cases and keep taking money from people you know no longer use your service. To that end, it feels like the fallibility of human memory is a dark pattern many companies are using for their own benefit.
Norwegian A.I. Retreat 1 Oct 2017, 11:23 pm
Last week I took a group of friends and colleagues over to the Norwegian Fjords for a 3 day retreat. We’d all been working hard the past year, and were feeling pretty burnt out. So everybody jumped at the chance to breath in the clean Nordic air, marvel and the beautiful surroundings, and get a sense of inspiration and perspective.
We’d booked the wonderful Juvet Hotel, a place I’ve wanted to stay ever since seeing it used as the location for Ex Machina. We needed an area of focus for the retreat, and considering the location, Artificial Intelligence seemed like the obvious choice.
Once the preserve of Science Fiction, A.I. is starting to weave its way into our lives. At the moment there’s a lot of hype and speculation; over active marketing teams trying to convince us that adding the letters “A” and “I” to a product instantaneously make it better. While that isn’t always the case, it’s helping lots of start-ups attract more investment and increase their valuation.
At the same time there is also a lot of fear, uncertainty and doubt being generated by the media. Rarely a day goes by without some news story proclaiming an end of days scenario, only for that same publication to dismiss the fears as irrational a week later. It seems that if A.I is good for one thing, it’s boosting circulation.
With opinions fluctuating between utopia and dystopia, I was struggling to get an accurate view of the field. As such, one goal of the retreat was to gain a more realistic understanding of A.I. away from the media hyperbole. We did this by starting the retreat with a simple domain mapping exercise, to ensure that we all had a shared vocabulary and understood the general direction of travel.
My other hope was to bring more diversity of thought to the conversation, and break away from the usual circle of computer scientists and technocrats. Rather than domain experts, we were a group of interested parties, comprised of people from the arts, humanities, academia and design. We weren’t necessarily the people inventing this brave new world, but we would be the type of people called upon to make it palatable to the general public through story telling and design.
At the outset of most technological revolutions, the focus is understandably on the benefits it can bring. For industrial advances, these benefits are often in the form of reduced costs, increased productivity, and increased shareholder value. It’s only later that the social effects become clear.
As a group of user-centered designers and humanist technologists, it became evident that our interest lay in the effects A.I. would have on people and society as a whole, rather than the more immediate and obvious benefits to productivity and commerce. Over the course of around a dozen unconference style conversations, from brainstorming dystopian futures to discussing robot ethics, a pattern of concerns started to emerge. We’ve tried to capture the outputs of these discussions as a series of open questions, which we hope to share soon.
One big topic of discussion was the fear that A.I. and robotics may bring about large scale under-employment. Past technological revolutions have sparked similar fears, and humanity has always been able to adapt. Engines surpassed human power, production line technology automated mundane and repetitive tasks, and computers allowed people to outsource data storage and processing. Each time this has happened, we’ve be able to find new and meaningful work to replace the lost jobs, driving productivity ever forward. However could A.I. be difference? If we can finally outsource human cognition to the machine, is there anywhere left to go?
A related problem is the nature of the work we’ll end up doing as a result. A.I. has the ability to remove mundane tasks and let us focus on the fun and creative parts of our work. It also has the ability to create a generation of workers who’s sole job is to babysit machines, only stepping in when some sort of exception is thrown up. While this may be efficient, it’s not a great route to job satisfaction. As a result A.I. could very well eat into the middle of the jobs market, pushing some people up the skills ladder, and others down.
Another big problem was the realisation that as systems become more and more sophisticated, they become more difficult to understand. It’s no longer just a case of viewing source and checking the code, but also understanding the training data. If the training data is biased, because society can be biased, the results may be skewed and difficult to detect. This could result in new jobs like A.I. trainers and data bias consultants to ensure that new A.I.s are being fair with their decisions.
We briefly talked about robot skeuomorphism; how a lot of household robots are currently designed to look vaguely humanoid. This has certain benefits, such as signalling the robots capabilities to their users. If the robot has eyes, you presume it can see, if it has ears you presume it can hear, and if it has legs you assume it can walk. A lot of robots also seem to demonstrate rather childlike capabilities like big eyes and short stature, partly to communicate a level of simplicity and demonstrate that they aren’t a threat. At the moment the form is largely a consequence of engineers trying to create robots that can do similar tasks to humans by duplicating their movements. However over time I believe that robots will move away from the humanoid form and develop shapes which are better designed and more suited to their particular tasks.
We also touched on the area of ethics and morals. For instance should A.I.s be forced to adopt a human moral code, and if so, what would that actually be? If we did manage to create some form of super intelligence, would we have to grant them human-like rights, or could we still consider them a utility like a car or a toaster. If they were treated like utilities, wound’t that raise some rather uncomfortable questions?
On a slightly more mundane, but possibly more near-term scenario, should we encourage people to be polite towards A.I.s in the same way we are polite to people? Obviously the current crop of A.I.s wouldn’t really care if we say please or thank you. However by ignoring these common social behaviours, we may be baking in problems for the future. One of the attendees mentioned how they accidentally started talking to their partner like they were talking to their Alexa, while several parents noted their kids had started to behave in similar ways. Imagine a future where robots pets and helpers were common. Could we imagine a scenario where mistreating a robot pet change the way we treated actual animals? If so, would we eventually have to consider legislation to prevent robot abuse?
Obviously a lot of these questions are just thought experiments, and are a long way off at the moment. However I truly believe that when I’m old enough to need some form of home care, there’s a good chance I’ll be looked after in part by a robot. So many of these challenges may will be here In our lifetimes, and a few may arrive sooner than we think.
Of course the trip wasn’t just pondering theoretical questions. I was as much a holiday as anything else. So as well as lots of stimulating conversations over good food and slightly overpriced beer, we had plenty of time to enjoy our surroundings. This included a lovely forrest walk along King Olav’s Way, a hike up a mountain to visit a Glacier, and even a chance to see the Northern Lights. These shared experiences helped us bond as a group, while the beautiful scenery helped put things in perspective and provide the space to think.
Considering the short amount of time we had at our disposal, It’s amazing how much ground we managed to cover and how productive we felt by the end. We had started the retreat with the 20 of us sitting around discussing what we’d hoped to get out of the next two days. We finished on a similar note, explaining what we’d all taken away. Everybody had a different story to tell, but we all left with new connections, deeper friendships, a better understanding of the emerging field of A.I. and a newfound love of the Norwegian Fjords. So much so, that we’ve already booked next years trip. I for one can’t wait.
Twitter and the end of kindness 13 Sep 2017, 12:36 pm
When you see somebody with spinach in their teeth, the kind thing to do is to tell them privately. If you tell them to their face, in front of a group of friends and strangers, you get the same end result; the spinach gets removed. However in doing so you bring attention to the problem, and shame the participant in the process. So what could have been an act of kindness, quickly turns into an act of cruelty and public humiliation.
There was a time, not so long ago, when you would contact a company directly if you had a problem with a product or service. Maybe the product got lost in the post or wasn’t as advertised, maybe the hotel room wasn’t as expected, or the food didn’t come up to scratch. In these situations you’d tell the waiter or manager, drop the company an email, or call customer support.
These days, when you see a problem, the first reaction is often to reach for Twitter and share your frustration with the world. With large companies this often comes from experience. We’ve all had conversations with banks, utility companies and airlines, which have gone nowhere, so we end up venting our frustration online.
While it’s easy for companies to brush private conversations under the carpet, it’s much more difficult to do in public, so we’ve quickly learned that if we take our criticisms to Twitter, there’s a better chance they will get dealt with.
I’ve had this experience myself. After several frustrated phone conversations with my airline of choice, I took my complaints to Twitter. They immediately responded, took ownership of the problem and sorted it out straight away. I’m now on some kind of airline social media watchlist (the good kind), re-enforcing the fact that if I complain on Twitter my problem will get solved faster than phoning customer services.
In order to avoid a public relations disaster, complaining on social media encourages the best customer service from a company. This is something the large companies could have avoided, by delivering consistantly great customer service through traditional channels. As this hasn’t happened, publicly shaming companies has become the go to way to ensure a good customer service.
If this stopped with large companies, or companies who you’ve experienced an irreconcilable service failure with, I wouldn’t mind. However this behaviour has become the standard behaviour with everybody now, from big companies to small companies, from celebrities to friends. Rather than contacting people directly, we’ve started using public shaming as a tool to correct behaviour.
I see it regularly on Twitter. A friend or follower tweets you to highlight some small problem. Maybe there’s a broken page on your website, a typo on your recent medium post, or you accidentally referenced the wrong user in a recent tweet.
It would be super easy to email or DM the person, but instead you post to their public timeline. Most of the time you mean well, and are simply trying to help. However by posting publicly you draw other peoples attention to the problem, forcing people to act out of shame and embarrassment rather than gratitude.
People usually post to the public timeline because it represents the least amount of effort to do a good thing. You don’t have to switch panes in your Twitter app, go hunting for their email address, or ask if they’d mind following you so you can direct message them. You can get it off your mind as quickly as possible and move on.
However sometimes it feels like there’s an ulterior motive. That there’s a small amount of joy to be had from spotting the person you’re following has done something wrong, and flagging it up in public. That you get the public perception of doing a good deed (which is always nice) while making a small but pointed statement that they’re not perfect in front of their friends. It’s as though you’ve spotted the spinach in their teeth, but decided that the kindest thing to do was to point it out loudly in a crowd, in front of a thousand of their closets friends.
Personally I’d prefer to know rather than not know, so I’m definitely not suggesting people stop pointing out these small errors and transgressions. However I think we should think twice before posting these things publicly, and if time allows, reach out to your friend or follower directly first. That way you’ll avoid accidentally embarrassing them, or making them feel that they have to act from a sense of public pressure.
More importantly it’s the kind and polite thing to do. It’s also going to make that person think more warmly of you, as you’ve done them a favour without seeking any recognition, while maintaining their dignity and public reputation at the same time.
It’s only a small behaviour nudge, but from now on I’m going to do my best to approach people directly first, whether it’s large companies, small businesses, website owners, followers or friends, when I notice something is amiss. I urge you to do the same.
The Golden Age of UX may be over, but not for the reasons stated 5 Aug 2017, 2:52 pm
Last week an article entitled The Golden Age of UX is Over popped onto my RADAR, after causing a bit of a stir amongst the design community. If I was being generous I’d say it was a genius title, designed to spark debate amongst UX designers. If I was being slightly less generous, I’d say it was a devilishly brilliant piece of click-bait, designed to drive traffic to an agency site. Either way I had a feeling the article would annoy me, so spent the next couple of days actively ignoring it. However temptation finally got the better of me and I ended up taking the bait.
On the whole I agree with the sentiment of the title that the “Golden Age of UX” probably is over. I say that as somebody who has been working in the space since the early naughties, set up one of the first UX practices in the UK, and curates the longest running UX conference in Europe.
The field of UX started life as a small but emergent community of practice, on the fringes of conferences like SXSW and the IA Summit. It grew through the blogs of early pioneers, and through the work of consultancies like Adaptive Path and Clearleft. The community accreted around new conferences like UX Week and UX London, which, in their early years, attracted almost the entirety of the UX communities in their respective locations.
I would argue that the quality of innovation, the quality of discourse and the quality of change in the UX space peaked somewhere between 2008 and 2012. This for me could arguably be described as the golden age of UX.
As with any gold rush, news of the find spreads quickly, and as more people rush in to make their fortunes, resources get depleted. By the middle of teens, UX hyperinflation started to occur. Every freelancer and every agency added UX to their titles, without really understanding what the term meant. “UX Designer” featured in lists of the most in-demand new professions and recruiters rushed to fill the gap, with often disastrous effects. While the number of people who self identified as UX designers carried on climbing, a deep and detailed understanding of what UX actually was started to ebb away.
The meaning of UX got muddied. Was it the same as UI? Was it another name for interaction design? Where did strategy, research and IA fit in? UX vs UI memes started to form on Twitter, arguments erupted about the existence of unicorns, and seemingly nobody could agree on anything anymore.
For years I fought to maintain a clear definition of UX, one that linked back to the community of practice from which it sprang. However the tidal wave of misunderstanding and misrepresentation became too big to fight, so I eventually gave up trying. UX had become so watered down and misunderstood that popular perception no-longer represented the community I knew. I became resigned to the fact that meaning changes based on usage, and if the majority of people see UX as this lightweight blending of prototyping and UI, devoid of any deep research, awareness of business needs, or commercial imperative, so be it.
It was this latter sentiment that annoyed me about the “Golden Age” article. Criticising a discipline based on cargo-cult thinking. In-truth, UX has always taken account of business needs and market forces, while Lean start-up was little more than a reformation of user centred design for a business audience. As a result, the article was less about the golden age being over, and more the dawning realisation that they may have confused a badly drawn map with the territory.
It’s also worth noting that most people tend to associate a “golden age” with their formative years, whether it’s movies, musics, or the discovery of a new career. So it’s possible that the golden age may be over for some, but for others it’s just beginning.
Design Leadership Slack Team 30 Jul 2017, 9:30 am
I recently started a Slack Team for Design Leaders. We currently have over 450 members; mostly Heads, Directors and VPs of Design from prominent tech companies and large traditional organisations. We’ve been very careful building the community. As a result the signal to noise ratio is remarkably high. Recent conversations have included:
- Discussions around recruitment and whether design tasks are a good idea.
- Various design leaders sharing their career progression ladders.
- An ongoing debate around the perfect team structure.
- Whether managing Millennials required a different set of skills (the general conclusion being they don’t).
- The challenges of managing fast growing teams.
- Tactics for your first 90 days in role.
The criteria for joining is fairly straightforward.
- You’re a senior design leader of an in-house team.
- You’re either the most senior design representative in your company, or a member of the design leadership team (at larger orgs).
- You’ve moved away from delivery and aren’t a “player-coach.”
- You’re a genuinely nice person who wants to contribute to the evolving filed of knowledge we’re creating.
If this sounds like you, drop me an email and I’ll hook you up.
Once you’ve joined, please feel free to lurk for a while and get a feel for the place. When you’re ready to jump in, please introduce yourself to the group, letting folks know a little about your background, the company you work for, the team you look after, and the leadership challenges that are interesting you at the moment.
We expect members of the Slack channel to respect each others privacy. If you do wish to disclose anything discussed here, please use Chatham House Rule and refrain from identifying individuals or their companies.
Members of this group are generally kind, considerate, constructive and helpful. Heated discussions may occur, but they should always be done with respect and a desire to advance the conversation. If you witness any disrespectful behaviour, please inform myself or one of the admins. We aim to resolve any conflicts peacefully and in a positive manner. However on the rare occasion this isn’t possible, we may ask individuals to leave.
The Real Value of Original Research 17 May 2017, 1:24 pm
User-centred designers typically start a new project with a research phase. This allows them to understand the product or service through the eyes of their customers, explore the limits of the problem space, and come up with recommendations that feel at least partially informed. All useful things from a design perspective.
Sometimes organisations baulk at the idea of doing research, causing the design team to launch into their typical spiel about the value of their approach. In my experience, these objections are rarely about the value of research itself, but more around whether original research is necessary on this occasion.
All organisations of a certain size carry out research as a matter of course. They probably have a marketing department segmenting customers, understanding customer sentiment, and testing new propositions through surveys and focus groups. They also have an analytics team tracking user behaviour, testing the effectiveness of campaigns, and pinpointing areas for improvement. In preparation for this project, the product managers and BAs almost certainly did their own research to help build the business case. They probably have more information than they know what to do with.
Most organisations feel they have a pretty good handle on what’s going on inside their company; they just need you to fix it. They claim there’s no need to do more research. Instead, they will provide you with access to their analytics package, the results of the user testing report they commissioned nine months ago, and copies of their marketing personas. This, combined with a briefing meeting should be enough to get your team up to speed.
On the surface this makes sense. After all, why pay for original research if you already have the answers you need? Better to save the money and spend it coming up with a solution, especially when resources are scarce.
This attitude is completely understandable, but it hides an unusual and counterintuitive truth about the value of design research. Design research is rarely about the acquisition of new knowledge and information. Instead, the real value of design research comes from the process of gathering and analysing the results. It’s this analysis phase where the data gets processed, information gets turned into knowledge, and understanding becomes tacit.
Existing research will have been gathered to answer general business questions, so it won’t necessarily provide the insights the design team need. Instead, design research is done with a specific product or service improvement in mind; it adds nuance to the problem at hand, and allows the designer to weigh up different options and understand how the various solutions may play out.
Knowledge gained from original research is far more impactful than that gathered elsewhere. Remembering the conversation you had with a frustrated customer becomes part of the narrative, and the resulting insight becomes internalised. This is a very different experience from reading a data point in somebody else’s report, which can easily be downplayed or forgotten.
In psychology this phenomenon is known as embodied cognition—the idea that you think through problems using your whole self, rather than just your mind. This means you learn more by experiencing something in person, than you do by reading about it in a book or report.
For most designers, original research isn’t about gathering facts and data. Instead, it’s the process they use to understand the task at hand. Like warming up before the big race, research allows you to engage body and mind, get the creative muscles working, and be flexible and limber enough to tackle the challenge ahead. It isn’t something you can effectively outsource to your coach or team captain. It’s a vital part of the pre-race process.
This was originally posted on UXMas.
First Direct Trains Customers to be Phishing Victims 2 Mar 2017, 11:55 am
Banking security is a big deal and has been all over the news of late. Most of the coverage focusses on digital security and how to avoid having your account hacked. A common culprit is the Phishing attack, where a hacker sends you an email claiming to be from a trusted source, and asking for personal information like your password, mother’s maiden name, date or place of birth. Most security savvy companies have got wise to this approach, so on every email they will state clearly that they will NEVER request personal information like this.
So I was amazed when I got a phone call, with no caller ID, from somebody claiming to be from my bank. The caller said that before he could speak to me he needed to take me through security and ask me a bunch of personal questions. If you know anything about security you know that Social Engineering on one of their easiest attack vectors. With Social Engineering somebody phones up claiming to be somebody official—your finance department, your IT team, your bank—and asks you to divulge personal information they can then use to compromise your account. This is essentially the real world—or at least phone world—version of a phishing attack, and is something and good security team should be concerned about.
As somebody who cares about personal security I was shocked, so immediately called the bank to highlight this glaring security risk. However rather than caring about security holes, I was told that this was bank policy and if you didn’t want to answer the questions you could always go online or call up.
This is a terrible response as it essentially legitimises and habitualness the fact that banks can phone their customers up without notice and expect people to hand over personal information to a stranger. Security savvy folks like me would decline, but not everybody is as wary as I am. If First Direct trains its customers to hand out personal information to strangers on the phone, this opens up a massive security hole. Any fraudster can now identify First Direct customers (for instance folks who have interacted with the first Direct Twitter account recently), find their contact details online, then phone them up to extract personal security information, and then use that information to break into their account.
This feels like a crazy thing for banks to be doing. What’s more, it seems strange that banks should be conscious about this type of security weakness through digital channels, while actively encouraging it through their phone banking services. There are of course various ways banks could solve this problem, like making automated calls asking the customer to contact the bank using the number on their card. That way, the customer knows they are talking to the bank and can go through the usual security protocol. Instead, it seems that banks like First Direct are sacrificing good data security, for the sake of convenience, which should be a worry to all their customers.
Talk Tropes and Conference Cliches 30 Dec 2016, 4:53 pm
Over that last 12 years of attending, speaking and organising conferences, I’ve seen a lot of talks. Probably upwards of a thousand. I’ve seen talks that have inspired me, talks that have challenged me, and talks that left me welling up. During that time I’ve seen themes start to emerge; topics our industry find fascinating and love to revisit time and time again. Many of these topics I’ve used myself, and were I ever to write a “101 things I learnt at architecture school” style book for the interaction design industry, these tropes would feature heavily.
After spending two days binge watching talks in an attempt to find the last couple of speakers for a conference I’m organising, I was amazed how regularly these tropes appeared. I was also surprised how certain traits and behaviours kept repeating themselves across speakers. So I thought I’d jot them down, on the off chance people found them useful. Either as things you hadn’t heard of before and wanted to explore further, or topics and behaviours you wanted to avoid in a search for originality.
Top Talk Tropes
One of the earliest tropes I can remember is “paving the cow paths”; the idea of designing for observed behaviour rather than imposing strict architectures of control. This concept beautifully illustrates the fields of user centred design and lean startup. It’s also one of the pervading philosophies behind the web; that there is intelligence in the system, and it will find its way around any blockage. In the retail world, “cow paths” are also known as “desire lines”, and are used to maximise product exposure. In past talks I’ve used this example to explain why milk is always placed at the back of the store, and how casinos in Vegas are designed.
If desire lines can be seen as a highly optimised user journey, the “peak-end rule” is a similar short-cut our brains make for judging how we experience said journey. Research from the field of hedonic psychology has shown that we tend to judge an experienced based on two things; the intensity of the peak condition—positive or negative—and the end state. This is one reason why the most memorable customer experiences are often the result of something bad happening. We remember the intensity of the bad experience, plus the happiness caused by a positive outcome, and the differential between the two frames our perspective. That’s not to say that we should deliberately try to manufacture negative experiences. However it does suggest that people will judge experiences more favourably that have peaks and troughs of emotion, but ultimately end well, rather than an experience that was consistently good, but not noteworthy.
A related cognitive bias is the idea of “change blindness” as illustrated perfectly but the classic basketball video. Viewers are asked to count the number of times the basketball changes hands. So fixated are they on this task, a good proportion of viewers fail to spot the 100 pound gorilla in the room, both literally and figuratively. This goes to show that even when we think something obvious is happening with our designs, many of the people using our products literally don’t notice the things we’re carefully designed.
One tool to help craft these peak experiences is “The Kano Model”. This model classifies features into three different types; basic needs, performance pay-offs, and delights. I usually describe the Kano model in talks by using the analogy of a hotel. A hotel room just wouldn’t function without a bed, a door, access to a bathroom, electricity and a few other must have items. Theses are your MVP feature set. However in order to compete in a crowded market, you can add performance pay-off features like a bigger TV or after broadband. Over time, these nice-to-have features eventually become basic needs, which is why most MVP aren’t very minimal. It’s the third type of feature in the Kano model that interests interaction designers and product managers the most. The small additions which have an unusually sizeable effect. This could be the warm cookie waiting for you at check-in, the free bottle of champagne in your room, or something as simple as a handwritten note from the cleaning staff, letting you know what the weather is going to be like tomorrow.
All these items can be mapped as peaks on some form of journey map. They can also form part of the classic “hero’s journey”, another common trope. If you’ve not heard of the hero’s journey before, it’s essentially the idea that many well known stories follow a common archetype. Somebody is given a challenge, they set off on a journey, aided by a wise confident. They overcome a series of increasingly difficult challenges, only to return back to the start a changed person. Stories like the Hobbit and Star Wars follow the heroes journey closely, which is one of the reasons they have endured so well. Narrative storytelling is all the range in the interaction design world at the moment, in large part thanks to the work of content strategists. We’ve actually used the hero’s journey framework in the case studies on our new site, making sure to cast the client as the hero, rather than ourselves.
The preceding tropes are good, but I think my favourite one has to be Stewart Brand’s “Shearing Layers” diagram from his book, How Buildings Learn. The original diagram was used to demonstrate the different speeds at which buildings grown and evolve, as well as the friction caused between layers moving at different speeds. I tend to use this as a megaphone for organisations structure and learning. Add to this the idea of pioneers, m settlers and town-planners, and you have a powerful tool for describing why different teams, disciplines and functions within organisations often struggle to work together.
There are dozens of other common tropes I could mention here, like Maslow’s Hierarchy of Needs, the classic three ringed Venn diagram with whatever the speaker does shown in the middle, or the classic illustration depicting lean start-up by showing a product move from skateboard, to bike, to scooter, then finally ending up as a car. I won’t bore you with my thoughts on that particular diagram here. Suffice to say there are a lot of common trends repeating themselves in the speaker circuit, and for good reason. However if you’re goal is to present something new and original, it may be worth picking something slightly more obscure.
Common Conference Cliches
As well as picking up and using a common set of tropes over the past 12 years, I’ve also adopted common traits and behaviours from other speakers. Behaviours like asking the audience about their backgrounds, or whether anybody has heard about the topic you’re about to discuss. It’s a way of building rapport with your audience, while making yourself feel comfortable on stage. However as audiences become more savvy, asking questions like “who here has heard about Lean” becomes increasingly meaningless, especially when their response is unlikely to change the direction of your talk. I’ve witnessed several awkward moments where a speaker asked an audience if they knew about a certain thing—when they clearly did—only for that speaker to launch into a 10 minute scripted description of what that thing was, making everybody feel like they hadn’t been listened too.
A similar faux pas is spending a sizeable portion of a talk introducing who you are and where you come from. A little context can be helpful, but I once witnessed a speaker give a 15 minute bio of pretty much every job they had had in their career. By the time they reached the meat of their talk, they had completely lost the audience—in some cases literally as around 50 people had walked out. The frustrating thing is the rest of the talk was amazing, or at least what I saw of it was, as the speaker ran out of time and had to cut the bulk of the talk short.
In this case I suspect the speaker simply felt nervous and wanted to justify why they had earned the right to be on stage to the audience. However from the audiences perspective the speaker had already earned their place on the stage and were expanding on information that was already in there conference programme. So rather than being interesting or helpful, it actually came across as self indulgent and disrespectful of the audience’s time. From that point on I decided never to introduce myself on stage, assuming that if people were interested they would read the schedule or check out my online profile. I’d urge folks to do the same, although if explaining your background is important, a great way to do it is part way in. I call this “The Hollywood opener” as you throw your audiences right into there middle of the action, and only introduce them to the main character once they’re hooked.
Making the audience feel uncomfortable is never a good idea, so having an understanding about the audience and their culture really helps. I’ve seen plenty of amazing speakers have great success with audience participation on their home turf, getting folks to stand up, stretch, introduce themselves to their neighbours, or discuss something that’s challenging them at work. I’ve seen those same speakers crash and burn in more conservative regions, where force social interaction makes people feel awkward. One particularly uncomfortable incident featured an exuberant North American speaker, a room full of stoic Europeans, and a compulsion to high-five everybody in the front row.
Ironically I’ve also seen audience participation go too well, with speakers allocating 30 seconds to something that should actually take 5 minutes of more. In that situation the audience is having such a good time chatting to their neighbours, having the speaker cut them off to get back to the talk can actually be quite jarring and a little insensitive.
One of the most challenging forms of audience participation has to be the Q&A at the end of a talk. I’ve seen some fantastic Q&A session that were actually more insightful and interesting than the talks that preceded them. However I’ve also witnessed my fair share of awkward sessions where a shy audience is cajoled into asking meaningless questions, just to break the silence and make the speaker feel liked and appreciated. More often than not these Q&A sessions suck the energy out of a carefully scripted talk; like a Director being forced to explain the plot-points of a move once the credits have rolled. They also get in the way of the audience members getting coffee, grabbing some food, making an important call or a much needed comfort break. So can also be a source of discomfort to some. As such I think it’s better to finish a little early than force an unwanted Q&A session.
This brings me to my biggest bugbear of late—not least because I’ve used this one plenty of times myself. It’s people making THAT joke about being “The only thing between you and food/beer”. It was funny the first couple of times I saw a speaker say that, and its’ always resulted in a titter of approval when I’ve used that line myself. However at a recent conference I saw two consecutive speakers make exactly the same joke, to clearly diminishing returns. As such I think THAT joke has now jumped the shark, so I’m going to do my best to stop using it.
It’s worth noting that there’s nothing wrong with any of these talk tropes and conferences cliches in and of themselves. They all have value if used appropriately. As such there is no judgement on anybody using them. After all I’ve used most of them myself. Instead I present them to you more as an observation from years of conference speaking, attending and organising, in the hope that both new and experienced speakers find them interesting. What you do with the information, if anything, is up to you. However I thought it was worth adding that caveat as you know how touchy people on the Internet can be.I’d hate for anybody to overreact or anything like that :)