-
A study in Frustration

Screenshot from The Simpsons episode ‘Homer’s Enemy’ © 1997 Fox Broadcasting Company “Suffering is the rejection of reality” – Yuval Noah Harari
Thy right is to work only, but never to its fruits; let the fruit of action be not thy motive, nor let thy attachment be to inaction.” – Bhagavad Gita
Why are some people more easily frustrated than others?
It could be that they have especially dodgy wi-fi connections or bad traffic on their way to work.
It could be their disposition, conditioning or upbringing.
But maybe it’s because of their internal rules about the world. Beliefs about how things ought to be.
When these assumptions clash with reality, they get frustrated.
To see how these sorts of beliefs can backfire, let’s look at Frank Grimes, a hapless character from The Simpsons, the episode ‘Homer’s Enemy’.
Frank is this really square, serious, buttoned up guy “who’s earned everything the hard way.” He’s a ‘real life, normal person’ who’s just working hard and struggling through life.
The joke of this episode is to have Frank start working at the power plant alongside Homer. Obviously opposite of Frank, Homer is a slacker, constantly failing to do his job properly, yet managing to coast through life. Homer can’t help but irritate Frank, who eventually becomes his sworn enemy.
As Frank settles into his new job, you can tell he’s a model worker who doesn’t have time for messing about. After perfunctory introductions he dismisses Lenny and Karl, saying “I’m sure you all have a lot of work to do.” Homer irritates him immediately, by knocking over his perfectly ordered pencils. Frank believes a good worker has a nice clean desk and doesn’t waste time with chit-chat. This sort of belief might help him feel like he’s had a productive day at the office, but it doesn’t leave much time for personal connections.
Frank is appalled at Homer’s indifference and sloppy shortcuts. When alarms are ringing in Homer’s control room, Frank has to point it out. He starts to gossip, “I saw him asleep in a radiation suit” and “I’ve never seen him do any work”. Homer doesn’t fit into what Frank believes a Safety inspector should look like, and the result is resentment: “That’s the man who’s in charge of our safety?”
When Homer nearly drinks from a beaker of acid, Frank’s beliefs compel him to intervene. Thinking fast and doing the right thing saved Homer’s life. But along with those good morals is a big dose of righteousness. He can’t help but give him a lecture. “Don’t you realise how close you came to killing yourself?” In Frank’s world, people ought to be cautious and careful. He feels that he needs to step up, because no one else seems to care.
Frank’s resentment goes into top gear when he visits Homer’s home. He’s stunned to discover that Homer has been living in a ‘mansion’. Homer has everything that Frank wants, but doesn’t have. Deep down Frank believes that only those who ‘work hard every day’ deserve a ‘dream house, two cars’ and ‘beautiful wife’. The result is the unpleasant taste of bitterness and more resentment.
Frank only lasts an episode. He winds up electrocuting himself, yep, you guessed it, to prove a point. He couldn’t survive that particular clash with reality. Josh Weinstein, Simpsons producer, expressed regret for killing him off so early but admitted that “we took a certain sadistic glee in his downfall. He was such a righteous person, and that somehow made his demise more satisfying.”
Frank also inspired an interesting mix of reactions amongst fans too. Many related to his realistic struggle while others just wanted him gone. Everyone seemed to take away a slightly different lesson from the episode. Here are some comments from a YouTube clip:
- “The less you care about life the more you gain.”
- “Found it funny as a kid. Now it’s realistically painful. Like I totally understand Frank’s frustration now that I’m adulting”
- “Frank no doubt deserved a better life, but he blew his chance to try and make at least one friend.”
- “our modern day Job(from the Bible)”
- “Dumb lazy people = succeed Hard workers = failures”
- “people will always prefer the fun-loving over the miserable man.”
- “Life isn’t fair, Frank.”
I feel bad for Frank. He had a point, but his downfall came from clinging too tightly to it. His rigid beliefs about what a good person should look like, and what a good person deserves, only fueled his misery and suffering. He couldn’t find a balance between his particular internal code of perfection and the real dysfunction around him.
But someone like Frank needn’t abandon their integrity or work ethic. They shouldn’t have to switch off their brain like Homer or melt down into caustic cynicism. What would help is patience (the best remedy for anger) and abiding by your inner rules a little more lightly. Neither squeezing life with a death grip, or giving up on it, but simply allowing it to happen.
Read this post on Substack
-
Abstractified

November 19, 2024 @ 6:31pm – Hawthorn, Victoria, Australia What I like about Temple Grandin is she gets to the point.
In “Animals in Translation”, she doesn’t spend long digging into the science, research studies or history behind a fact. She’ll just say something like “in my experience dogs do not like Halloween costumes.”
And she’s probably right.
She likes to use heuristics like “the more Wolfie a dog looks, the more Wolfie it acts” and she’s not afraid of wading into un-researched areas either, “I expect we’ll find that dogs make humans into nicer people and better parents.”
As I read on, I was surprised not only how willing I was to give her the benefit of doubt, but also how refreshing her writing felt. Why was that?
I mean, I don’t even own a dog.
One reason her writing stands out might be because she’s autistic. Temple is highly functioning, but clearly looks at the world differently. One example of this is how she sees things most people don’t. In her work with livestock, she created a checklist of 18 ‘tiny details that scare farm animals’. For her, and to a 1200lb Angus, a ‘sparkling reflection on a puddle’ is really distracting, something even seasoned farmers weren’t noticing.
Secondly, she doesn’t signal. Usually in a popular science book like this, the author is subtly signalling all sorts of things like that they’re smart, woke, a New Yorker, a creative or that they’ve read a ton of books. Everyone does this to some degree. Publishing a book itself is usually about establishing some degree of credibility and authority. It’s actually so prevalent that it’s hard to notice, until you read a book like Animals that is completely devoid of it. It’s not that she doesn’t have an ego, or a point of view, she just doesn’t seem to care how she comes across. She is simply trying to communicate important things to know about animals. Yes, really. Even when she is considering something controversial like whether humans should eat meat or not, she’ll talk about the idea purely on its merits, something pretty much no one does.
Lastly, Grandin avoids the usual frameworks and buzzwords that are so common in pop science books. In fact, she views abstract thinking as a big blind spot for us ‘normal’ people.
“Unfortunately, when it comes to dealing with animals, all normal human beings are too absractified, even the people who are hands on. That’s because people aren’t just abstract in their thinking, they’re abstract in their seeing and hearing. Normal human beings are abstractified in their sensory perceptions as well as their thoughts. That’s why the workers at the facility where the cattle wouldn’t go inside a dark building couldn’t figure out what the problem was. They weren’t seeing the setup as it actually existed; they were seeing the abstract, generalized concept of the setup they had inside their heads. In their minds their facility was identical to every other facility in the industry, and on paper it was identical. But in real life it was different, and they couldn’t see it. I’m not just talking about management. The guys in the yard, who were there working with the animals, trying to get them to walk inside the building, couldn’t see it, either.”
Abstraction is hard to avoid, especially in knowledge work that involves complex, messy problems that span code, relationships, digital systems and physical environments.
Even so, I’d like to think of Temple barging into a meeting, covered in mud, sweeping all the post-its aside, clearing the diagrams off the whiteboard and saying ‘what the hell are you guys doing here?’
In 2023, I wrote Keeping in Touch, inspired by Temple’s first book, Thinking in Pictures
-
Designing with concepts

March 20, 2025 @ 7.32pm – Hawthorn, Victoria, Australia In his book The Essence of Software: Why Concepts Matter for Great Design, author Daniel Jackson says that all apps are made up of collections of “concepts” each a “self-contained unit of functionality.”
A concept isn’t exactly a design pattern, feature or job to be done. So, what is it?
“You’re already familiar with many concepts, and know how to interact with them. You know how to place a phone call or make a restaurant reservation, how to upvote a comment in a social media forum and how to organize files in a folder.”
So when you write an email in Gmail, or message a friend on WhatsApp, you’re not just scrolling screens and tapping buttons, you’re relying on these invisible “concepts” like Inbox and Conversations.
Concepts are everywhere, characterizing every piece of software.
Another concept you’re probably familiar with is a comment. You might find comments on a NYT Cooking recipe, a line in a Google Doc or a video on Meta. A comment lets users to respond to something specific. Like a comment, but a bit more specific, an upvote on Reddit lets users to show they support a post, making it more visible to other members.
If you’re responsible for designing software, you’re likely already dealing with lots of concepts that were “invented by someone at some time, for some purpose… (and have) undergone extensive development and refinement over time.”
Well designed concepts means better usability
‘So what?’ you’re thinking. I’m a designer, I’m focused on real problems like usability, not abstract concepts.
Well, what makes software difficult to use? Sometimes it’s because features are missing or hard to find but usually (it only takes one user testing session to learn this), it’s because “the user has a mental model that is incorrect—that is, incompatible with the mental model of the designer and implementer of the software.”
Or in other words, the user experiences bad design.
We can design better software when we understand how our users think about the software – their mental models. And likewise, “An app whose concepts are familiar and well designed is likely to be easy to use, so long as its concepts are represented faithfully in the user interface and programmed correctly. In contrast, an app whose concepts are complex or clunky is unlikely to work well, no matter how fancy the presentation or clever the algorithms.
‘Style’ – A closer look at a word processing concept
I first learned about concepts from Daniel Jackson years ago. The thinking resonated with me, but as a product designer I struggled to put it to use. Since concepts ‘have no visible form, they’re rather abstract’, it’s easy to overlook and dismiss them.
One simple way to work with concepts is to compare how they’ve been expressed in similar apps. Take word processing for example. It turns out Microsoft Word & Apple Notes share lots of the same concepts like paragraph, format and style.
In Notes, an app created by Apple to help “jot down quick thoughts”, clicking a button in the toolbar opens a menu with 9 preset styles.

Notes: Click anywhere in the text you want to format, click “Aa”, then choose a style. In Word, there’s also a similar Style menu in the Toolbar, but instead of 9, there’s 16 preset styles. When you resize the window, more styles become accessible in a visual ‘Style Gallery’. Fancy. There’s also a side panel so you can see all the styles while you type as well as heavy duty style management in settings.

Word: Select the text you want to format, and then click the style you want in the Styles gallery.Style is a foundational concept, which is why it appears in both apps and works in pretty similar ways. But small differences point to different product decisions, target users, and even company values.
Designing with concepts
Aside from discovering concepts in apps you use, here are a few ways to bring concepts into the actual design process.
- The less the better: Aim to use the smallest set of concepts users need to get the job done. Simple doesn’t necessarily mean less functionality or more white space. It’s true that some of the best designed apps are simple, but they are simple because they use a small number of elegant concepts – or paraphrasing Gall’s law, “evolved from a simple system that worked.”
- Don’t overload: If you’re thinking of introducing a new concept into your product, always make sure it has a clear “purpose”. Don’t overload a concept to make it try and solve lots of different problems at once. In Word, buttons for formatting text appear near to the Style panel (because that’s where one might expect them to be) but they aren’t all mixed up in same menu.
- Where are concepts failing? When you test a design with a user, consider if they are having trouble with a particular interface element or bit of content, or if there might be a broader issue with how concepts have been designed and implemented.
UI widgets don’t determine the success of a successful product, well designed concepts do. When we work with them directly, we can design systems that are more enjoyable, learnable and effective for the user.
Want to learn more? Daniel Jackson has created a lot of content on this subject:
- Short read: Software = Concepts (6 min read)
- Watch: What makes software innovations succeed? Maybe not what you think. (13:30)
- Long read: The Essence of Software: Why Concepts Matter for Great Design (336 pages)
Read this post on Substack
-
Taking meditation seriously

July 12, 2024 @ 12:22pm – Mission Dolores Basilica, CA As soon as one believes a doctrine of any sort, or assumes certitude, one stops thinking about that aspect of existence. – Robert Anton Wilson
Belief is a toxic and dangerous attitude toward reality. After all, if it’s there it doesn’t require your belief- and if it’s not there why should you believe in it? – Terrence McKenna
I recently finished my second 10-day silent Vipassana retreat.
As I said my goodbyes, I got into conversation with Vishal, the man I’d been sitting next to in the meditation hall every day. Since there’s no talking or eye-contact allowed, the other meditators (about 24 men and 24 women) are more like blurry shapes of energy than actual personalities. You can’t help but think about what they are like in the outside world, but we’re reminded that this is just another distraction.
Yet, with only occasionally glances at him in my peripheral, I’d noticed his quiet determination. Compared to others, he took every sitting as seriously as possible. Sometimes you can just tell.
When I said this to him, he smiled politely. “You take it seriously too.”
Two years prior, I had signed up and sat my first retreat quite spontaneously. I had no meditation practice or even theoretical knowledge to prepare me. But after a short ‘dark night of the soul’ on Day 3, where I was close to packing my bags, I was suddenly all-in. When the gong was struck at 4am, I didn’t flinch. I was often first in and last out of the hall. I started to deeply enjoy the simple, vegetarian meals. 10 days went by in a blur. On the final day, when ‘noble silence’ was lifted, others came up and congratulated me. “You were sitting like a statue.” “How did you do that?” I felt surprised and sheepish. I didn’t have an answer. I shrugged, “I guess I just took it seriously.”
I shared some of this with Vishal, who nodded. He was tall, and pious looking, with carefully groomed hair. It had been ten years since his last retreat, due to a busy family life, part of the reason he’d tried to make the most out of the last ten days.
“We’re serious because we’ve done this before.”
Due to his beliefs, karma and previous lives explained my disciplined almost reverent approach to meditation, something relatively unfamiliar to me and not connected to my parents or society I grew up in.
In 2023, encouraged by a Taiwanese co-worker, I booked ‘Tour de Taiwan’, and rode around the island in 9 days. Having never visited before, I felt strangely at home with the strange people and places we discovered. Why was that? As we made our way along roads that snaked over mountain passes and rice paddies, familiar faces crossed my mind.
There was Emily, a Creative Director at a tech startup. She was high energy, put on art shows in her spare time and was half Taiwanese. In 2014, after a summer of unsuccessful interviews, my US visitor visa had run out and I’d travelled to London. I was calling her from a loud Starbucks with dodgy wi-fi. But she hired me, and I ended up living in America for the next 6 years.
Four years after that call, another Taiwanese woman took a chance on hiring me, and so I moved from New York to San Francisco. She was also a Creative Director, a single mum, loud, un-filtered and Taiwanese.
At that job, the Taiwanese-American Head of Content, who moonlit as a spin class instructor, encouraged me to sign up for a triathlon, which would become an interest for me over the following years.
Finally, my girlfriend in New York. One weekend we took a trip to upstate New York where we stayed at her family’s house. She was born in the States but her parents were from Taiwan and seemed to be Buddhists by the look of some of the paintings and sculptures dotted around the house. On the way back to the city we stopped at a temple. “We’re not really that serious about it” she said as I gawked at a giant statue of Buddha.
Do these coincidences make me believe in reincarnation? The short answer is no. I like to remain open and flexible in my thinking, which is just not compatible with being certain about stuff like that. But I think it is worthwhile to consider and be grateful for our unique strengths, preferences and affinities – whether you know where they came from or not.
This was also posted on Substack
-
Writing rightly

February 12, 2022 @ 12:56PM – Freeport, Bahamas Last August I posted a note to Substack that outlined my criteria for publishing writing. It should be:
- Interesting (to me)
- Communicated as clearly as I can
- Useful to the reader
I mostly still agree with these but wanted to include my general ethical attitude/approach toward my writing. Here it is, in no particular order.
- I think what I’m writing about is valuable in some way. I wouldn’t share it otherwise.
- My intent therefore is to share that with the reader. That’s basically it. I don’t want to inflame emotions, get you to buy something, troll or make you feel bad.
- I’m not writing for a specific audience.
- Writing is both a means and an end for me.
- I only write what I’d also be comfortable saying, or defending if need be, in person.
- I’ll try to write as clearly as I can. I might use certain words or techniques but my intent is never to manipulate. This is obviously a balancing act, but I’d rather someone be bored and leave than to be tricked.
- I won’t lie or make things up.
- I’m mostly interested in things that you can point to or that seem intuitively right. I don’t make metaphysical claims.
- I want to write as truthfully as I can, but don’t expect exactitudes. That’s not the point of my writing. I might say something like: “we’d be better off drinking water instead of Fanta or whiskey.” One could pick apart that sentence endlessly, but you get what I’m trying to say. This is why I use a lot of words like ‘might’ or ‘probably’. I don’t ever want something I write to be misconstrued or misunderstood as an absolute claim.
- I have opinions but I won’t ever try to force them on you. I try not to write moralistically or judgmentally. For example, although I don’t think it’s a good idea to lie, I will never say that people who lie are evil or that you should never lie. If you want to read what I write, great! If you don’t, great!
- I write about topics I feel confident enough to explore and perhaps offer something valuable to the reader. That said, writing about something doesn’t ever mean I know what I’m talking about.
- Aside from minor tweaks, I don’t dramatically rewrite articles once they’ve been published. If I do seriously change my mind, I might remove the post.
- I occasionally use LLMs for writing support.
- I’m often thinking or relating to real people, places and things that happen in my life, but in almost all cases I won’t use names or details of real people.
- I’ll occasionally quote books or articles, and if I do I’ll make a footnote. But I’m not a good fact-checker. For example, if I quote Socrates or a Wikipedia article, I’m not doing deep research to make sure it’s correct. I go by intuition, and if I feel unsure about the source, I won’t quote it.
-
Are designers making design hard for themselves?

These days, whether it’s gen AI or the overall death of the industry, there’s no shortage of problems flying around for designers. And that’s what I expected to read about when I picked up this short book titled Why Design is Hard.
But instead, I was surprised to see the argument made that design is hard because of an internal problem, rather than an external one; that the profession of design has flaws in how we think about what we do.1
So why is design hard?
- Designers tend to think of design as a solo activity, when it’s clearly not
- Designers tend to think others should just trust their design decisions
- Designers tend to overvalue creativity over bottom-line value for the business
The authors suggest that this type of attitude lands designers (of all levels) in all sorts of trouble. Designers are then surprised when priorities change, offended by constructive critique or resentful that their skills are undervalued or misused.
With a bit of a reality check, designers can stop tripping over themselves and basically get back to designing.
This made me wonder, does every profession struggle with these sorts of attitude problems, or is it only design? Maybe because UX design is a relatively new profession (~100k UX designers in the U.S), it never had much time to solidify its identity, and maybe never will.
The latter half of the book shares a few ideas for ways of working more effectively, particularly focused on designers within large organizations. Here are three that stood out to me:
If you can’t sell it, did you even design it?
In order for your precious work to see the light of day, a designer needs to not only deliver well designed solutions but articulate how the design solves it in a way that is compelling and fosters agreement.2 Like a politician running for election, what’s almost equally important to their ideas is how those ideas are communicated to the voters. For designers, whether it’s explaining a problem, or the results of a successful experiment, if your communication isn’t clear, it’s like it never happened.
The system is working (just not for you)
Have you ever been really surprised by something, like a project that was cancelled at the last minute, or user behavior that clashed with the data? It turns out that often what can seem like stupidity is often a constraint you can’t see.3 Rather than reacting blindly, or waiting for the perfect internal process to materialize, designers should learn to use system thinking (eg. 5 Whys) to help us understand our environment better and anticipate future hiccups.
The one thing designers forget to do…
Let’s face it. No one ever says ‘involve me as late as possible.’4 Whether you are an engineer, or product marketer, a lack of trust and collaboration with design is a recipe for disaster. That’s why it’s critical for designers to shepherd the work through the organization5 and lead their core team along the design process. In a way, showing the same care for coworkers as you might for the end-users you design for. Again, I think soft skills like active listening, empathy & communication do most the heavy lifting here.
Overall, Why Design Is Hard is a short, slightly bitter perspective on how to be effective as a designer (especially within a large organization).
Thankfully, there’s not too many grand proclamations or predictions on the future of design, just good advice on how to stop getting in your own way.
- Why Design Is Hard by Scott Berkun and Bryan Zug ↩︎
- Why Design Is Hard by Scott Berkun and Bryan Zug ↩︎
- Why Design Is Hard by Scott Berkun and Bryan Zug ↩︎
- Why Design Is Hard by Scott Berkun and Bryan Zug ↩︎
- Why Design Is Hard by Scott Berkun and Bryan Zug ↩︎
-
Being wrong for the right reason

March 15, 2025 @ 9:30am – Richmond, Victoria Last year, I DNF’d a difficult bike race.
It was painful for me in many unexpected ways and I wrote about it a lot.
I compared it to a temper tantrum:
You kick up a big fuss because things aren’t going your way.
I got existential:
You start questioning yourself. Why am I here? What am I doing this for? When all you need to do is ride your bike to the finish line, asking “what’s the point?”, is not very helpful.It’s the type of question that invariably creates more questions. Do I even like this? Why do I do this to myself? Who do I think I am? What am I getting out of this?
I blamed my ego:
It was dramatic (I’ve lost the love, I’m quitting.) It was proud and sought validation (I’ve done a lot of training, but it wasn’t enough). It was dismissive (Things change. I’m interested in different things now. Cycling is not for me)
I blamed my body:
When we run low on water or nutrition, our mind goes crazy. I was bonking, dehydrated and out of carbs. I hadn’t planned enough, paced enough or trained enough, and paying the price.
I blamed masochism:
No one told me to grit my teeth. Although it gives me a certain kind of energy, it doesn’t feel very pleasant. And if I’m honest, it rarely helps with whatever I’m trying to do. It doesn’t make me smarter, faster, funnier, kinder.
Even in my dreams I was questioned, prodded and mocked by satisfied race finishers who demanded I take responsibility for my result.
Once the psychic dust had settled, the diagnosis was blindingly obvious. I hadn’t prepared enough.
A year later, I was back and ready to ride again. My determination was still there to finish the job.
But this time, I had a plan. I mean, I literally had a training plan, a single PDF page which told me very simply what to do and when to do it. On Monday I rested. On Tuesday, I rode my bike.
I had one rule. Stick to the plan as best as you possibly can.
As the race loomed closer in my calendar, I noticed how much I resisted following a structured plan that was almost guaranteed to help me.
I started to resent ‘grinding‘ through it day by day and wanted to invent my own approach. I hated to defer to a ‘stupid’ ‘rigid’ instructions and wanted to ride with vengeance, ‘destroying’ my previous time.
Famed San Francisco 49ers coach Bill Walsh calls these distracting ego-traps ‘faulty reasons’. It’s when “your logic is skewed by emotions, pride or arrogance.”1
In other words, when your ego gets in the way and tries to run the show.
Like what happened last year to me.
He noticed early in his career that he consistently got into trouble when he was “trying to prove you’re right and trying to prove someone else is wrong. Of course, they amount to the same thing and often lead to the same place: defeat.”2
Outside of the football field, Bill points to Ernest Shackleton as an example of the ego trying to “force a plan past the point of reality.”3 Before Shackleton set off on his mission to cross Antartica by foot, whalers told him that the Weddell sea was unusually packed with ice that season and advised waiting. Sticking to his plan turned into an epic disaster.
On race day, I rode with a clear head, fresh legs and surprising ease. My boring plan and preparation freed a huge amount of bandwidth to enjoy the car-free roads, nature, meet strangers and help teammates.
I reigned in all point proving, theatrics or anything else stupid.
My ego suffered, but I finished the race.
It’s not a surprise that decent planning and preparation helped. Of course it did!
But sticking to the plan rather than the tempting demands of the ego, meant that even if I had failed, I would have failed for the right reasons.
This journal is also published on Substack.
-
Where should people begin if they want to have a more friendly inner voice?

February 21, 2025 @ 8:13am – Richmond, Victoria This question was originally asked of Alain de Botton. You can listen to his answer here.
Here’s the problem, and it’s a big one. Most inner voices are not noticed.
The most helpful and important thing one can do with an inner voice is to nudge it into the daylight. There, one can deal with it simply, like an incorrect charge on your credit card bill.
If you can see it, an inner voice will reveal itself as non-complex. It’s just a bit of commentary.
But when it is left in the dark, it’s dangerous.
A personal example. I’m getting ready to leave my house to go camping for the weekend. I need to brush my teeth, eat breakfast and pack my bags. But as I do these tasks, a critical voice follows me.
- “You forgot to turn off that light again.”
- “Toast is taking too long, you should have made cereal instead.”
- “You’re making a mess. Slow down.”
- “You’re not thinking very clearly are you?”
I could go on, but I think you get the picture. Lots and lots of negative commentary.
Heres’ the kicker:
When one is not aware of an inner voice, we implicitly agree with it.
In one smooth, habitual action, we’ve listened, agreed and responded to something that might not be worth responding to.
We might reason to ourselves, “I know it’s a mess, but I’m in a rush.” Can you see how ‘mess’ has been folded into that thought without question?
And that’s how most of us live with an unfriendly voice. It sets the scene for every moment of our lives and narrows the scope of the actions available to us.
You didn’t answer the question. Where should people begin if they want to have a more friendly inner voice?
With a little awareness of an inner voice, one has many great options to deal with it. Instead of responding to an inner voice automatically, don’t. Pause. Question it. Get it a cold drink. Suggest that there are nicer, kinder ways of speaking (or thinking) that the voice may not have considered. Point out the invariably faulty logic and contradictions. If you are being critical of the quality of someone’s cooking, ask this unfriendly voice if it thinks it is a Michelin star chef.
A nasty inner voice doesn’t have the ability to introspect or to seek balance. It’s a hot headed 14 year old with a keyboard, an anonymous comment section and a point to prove.
It’s not about making an inner voice friendlier. It’s most important to make it conscious, so it can be seen for what it is, a weak, repetitive bit of commentary that you respond to without flinching. Then, with an appropriate amount of objectivity, one can form a more mature relationship, whether that’s ignoring, tempering, laughing or even (gasp) showing some compassion.


