Menu

Posts tagged “mental health”

Link roundup for November 8, 2023

It’s been a bit quiet on the blog lately, so I thought I’d bring back the link roundup thing I used to do quite a bit. Here’s some stuff I read and enjoyed recently outside the regular product/business topics I usually write about here…


Very good summary of The OpenAI Keynote by Ben Thompson. This bit stood out to me:

The fact of the matter is that a lot of people use ChatGPT for information despite the fact it has a well-documented flaw when it comes to the truth; that flaw is acceptable, because to the customer ease-of-use is worth the loss of accuracy.


I’ve been following Craig Mod’s work for over a decade and know what to expect, yet his reflections on “Aloneness” took my breath away.

The real shitter is that if you’ve inured yourself to living in this state of aloneness, it can be difficult to break the habits that have led to it. Aloneness as default becomes comforting, and habits built around aloneness feel palliative because they’re known, and we tend to repeat familiar actions, even if they hurt us.


Great essay by Anne Helen Peterson on how friendship changes over time—including a period she calls “The Friendship Dip”:

Right now, the way our society is organized, we have a prolonged stretch of adulthood that is not conducive to forging or sustaining friendship or community. In many cases, I’d say it’s actually hostile to it.

7MqYrBBr8gSDreEKTjraPC 1920 80

Everything about the new U2 show sounds amazing. So sad I don’t have tickets.

Zoo TV had predated reality TV, fake news, social media—all these things. Bono had heard about this new venue in Vegas with nearly 20,000 seats, custom sound and an incredible screen that was akin to the whole audience having a VR experience. In the post-Covid era, it was appealing not to have to travel every night


Every new house in Portland uses this font for the house number, and now I can’t get this article out of my head. “The gentrification font: how a sleek typeface became a neighborhood omen”:

As Neutraface house numbers have become too commonplace to ignore, some now associate them (along with gray paint jobs) with neighborhoods overtaken by construction and renovations.


Feels like spam is about to get a lot harder to detect… “Inside the Underground World of Black Market AI Chatbots”:

We’ve got folks who are building LLMs that are designed to write more convincing phishing email scams or allowing them to code new types of malware because they’re trained off the code from previously available malware.


And finally, for my fellow Northerners… “How to light the dark months” has some excellent advice—not just the normal stuff we’ve all read a thousand times.

Lighting winter is an art and a daily practice, an act of survival and a gesture of love. Here are 10 ideas for fighting the gloom in the dark half of the year.

How to spend your life force as a product manager

I’ve been spending lots of time recently thinking about and working with my team on what I can only refer to as “how we should spend our life force.” If that sounds weird, hold on to your hats because I’m going to make it even weirder by (and I apologize in advance) throwing a 2x2 matrix into the mix. So. Come with me in this post as we discuss how our biggest strength as product managers can easily become our biggest weakness, and how we can protect our health and sanity in the midst of all the turmoil in our companies and the world at large.

First, without getting too deep into the metaphysical or get myself in trouble about things I don’t know enough about, I do think it’s import for each of us to make conscious decisions to spend our “life force” on things that make us generally feel fulfilled and bring us closer to the person we want to be. That can take many forms—a bike ride, a fun side project, a bad action show (The Night Desk is so bad good!), an interesting problem at work… those can all be good ways to spend our life force! Being on the internet too long, on the other hand, is rarely that:

This is true at a macro level in our daily lives, but also when we zoom into how we spend our time at work. PMs in particular have this annoying habit where we tend to gravitate towards the wicked problems—a trait that makes us good at what we do, but can also be self-defeating because when we spend too much of our time depleting our life force, burnout eventually finds us.

So 2x2 matrix incoming! I think of the way we spend our life force as PMs on two dimensions: the difficulty of the task, and our likelihood of influencing the task’s success.

Some tasks fall in the easy bucket (relatively speaking—don’t @ me!). Think about things like customer interviews, collaborating with designers on a good user experience for a feature, or puttering around in JIRA making comments here and there. But then there are the difficult tasks—solving an organization’s quality problem, fixing development and deployment dependencies, understand team dynamics and creating a safe and open work environment where the whole team feels happy and fulfilled… you get the idea.

We are probably all familiar with that dimension. But the dimension we don’t always take into account is the probability that our work will actually influence the outcome of the task to ensure its success. Maybe the collaboration with the designer has a low probability of success because they report into a different org with different values. Maybe fixing development and deployment dependencies have a high probability of success because you have a really good relationship with engineering leadership and you all are highly motivated to solve the problem.

Which leads me to my main point. It’s in the combination of the ease/effort involved in a task, as well as our known sphere of influence, that we are able to make the best decisions about where to spend our life force. Let’s break out that long-promised matrix now, shall we?

You’ll have to excuse me, I’m not good at naming things. But let’s go through these.

Just don’t

Let’s get this one out of the way first. There are tasks that are easy, that we might be tempted to pick up—especially when we’re already tired and close to burnout—that simply don’t make sense because there really is no winning.

Maybe you are a JIRA wizard, and you think it would be an easy win to redo some of your workflows. But maybe the engineering team has no interest in changing any workflows and they see no benefit in learning a new system. They dig their heals in, and before you know it you’ve spent weeks on an “easy” task that only served to erode trust between you and the engineering team.

Just don’t.

Unnecessary hill-dying

This bucket is really interesting to me because I think a lot of ambitious, smart PMs gravitate towards problems like these. We want to go for the hardest, “wickedest” problems out there, and prove to ourselves and the world that we can solve them. This is such an admirable quality, but not a sustainable way to live your work-life.

Think of our example of solving an organization’s quality problem. This is likely a really hard problem that requires coordination and buy-in across multiple teams, with a lot of resistance and meetings and meetings about meetings and meetings to talk about how bad that one meeting went. With extensive effort and superhuman patience and collaboration skills you might get to a point in 9–12 months where the quality of the organization’s output has seen a marked improvement. At that point it will feel amazing and you’ll be proud—as you should be. But it might also kill your drive, enthusiasm, and ambition and turn you into a relentless cynic.

I think we should all attempt a task like this at least once in our careers. But it is no place to build a home.

Hero makers

Oh, we love these kinds of tasks too, don’t we. Really hard problems with enough social and organizational capital to make a real difference in a reasonable time frame? That’s PM catnip right there! This box is definitely a better use of life force than unnecessary hill-dying, but we have to limit ourselves here too. Because even though the payoff / enjoyment / fulfillment of this work can be huge, so can the cost. This is difficult work that can also become addictive, and if we don’t pace ourselves and limit the number of tasks we take on in this box, burnout will find us here. So choose these carefully, and try to shift more of your life force to…

Huge impact

As we progress in our careers some tasks that used to be difficult become second nature to us. What sometimes happens is that we forget that it wasn’t always easy, so we erroneously start to think that everyone on the team already knows what we know, and we start to undervalue our contributions / knowledge.

Take a moment to think if this is happening to you. Maybe you have gotten really good at JTBD interviews, or facilitating group FigJam sessions, or getting a team to define a customer problem / business outcome effectively, or… What are the things that you can do in your sleep, but only because you’ve spent so much time on those tasks that you have a level of familiarity that others on the team simply don’t have?

Those, my friend, are high impact tasks that take very little energy/life force, and often gives you energy because of how electrifying it can be to be really good at something. You should always be on the lookout for ways to apply those unique skills to problems/opportunities where it can be really impactful. Unfortunately we can’t spend 100% of our time on tasks like these—and frankly, we shouldn’t want that, because then we’ll stop growing. But the number should definitely be more than 0% and probably closer to 20% of our time.


The main point I want to make with this post is that as PMs we generally have a lot of autonomy over how we spend our time, and that can be a blessing and a curse. A blessing because we get to prioritize our impact. A curse because we too often spend our life force on tasks that drain us and lead us towards burnout.

So take a moment to breathe, and think about the amount of time you spend in each of the life force buckets I mentioned here—and where you might need to make changes to avoid the road to exhaustion and burnout. And please, come up with better names for the buckets than I did.

Hypervigilance is not a sustainable lifestyle for leaders

In This will only take a minute the Raw Signal team shares some much-needed advice for leaders who feel like they never have time to think and reflect. This state of constant hypervigilance is not a sustainable lifestyle because:

On one level, you’re a human being. Regardless of your title or role, you are worthy of work that doesn’t wreck your health, or your happiness, or your ability to enjoy lunch away from your webcam. On another, if you’re a manager, you’re responsible for the work of a team of other human beings. If you don’t have the time to be thoughtful about your own work, the odds are very high that your team doesn’t either.

They go on to share some ideas for how to make this time to step back a priority, once you are “past the point where working a little bit more is going to clear your plate”.

The 90s, having time, and always rushing to the next thing

I’m sure every generation writes lots of articles like Freddie deBoer’s It’s So Sad When Old People Romanticize Their Heydays, Also the 90s Were Objectively the Best Time to Be Alive. But hear me out. This is the impassioned, forceful, yet balanced Gen X take I wish I had the skill and wherewithal to write. It is a balm to the nostalgic soul in a way that somehow doesn’t feel like cringey old-person fanfic.

Here he is on the experience of visiting a record store:

When you were there you were Doing Music. Now we’re never doing anything—we’re always getting through something to get to something else to get through, using various time-saving techniques that maximize the amount of time we have to get through things while keeping our attention divided into a thousand things we then get through. When you went to a record store you were intent on music, and sometimes, you’d care enough about a particular artist that you paid for their album, real money, so that the artist got a cut that was more than the .002 cents they get per stream now.

This reminds me of the question Alan Jacobs asks: What exactly are we’re rushing towards with all our 2x listening and cliff notes skim-reading?

My question about all this is: And then? You rush through the writing, the researching, the watching, the listening, you’re done with it, you get it behind you—and what is in front of you? Well, death, for one thing. For the main thing. 

But in the more immediate future: you’re zipping through all these experiences in order to do what, exactly? Listen to another song at double-speed? Produce a bullet-point outline of another post that AI can finish for you?

Maybe the 90s have a thing or two to teach us yet.

Mono no aware

What would happen if we look at time through the lens of attachment theory? That’s the question my friend Simon asks in Attachment Styles to Time. I definitely have an “anxious attachment style” with time:

An anxiously attached person to time will try to arrest it: to find comfort again in a space where time felt distant. A coping strategy is to try and keep things the way they were. To hold onto people and places even if you aren’t present anymore.

The framing also reminds me of the Japanese phrase Mono no aware:

Mono no aware (物の哀れ), lit. ‘the pathos of things’, and also translated as ‘an empathy toward things’, or ‘a sensitivity to ephemera’, is a Japanese idiom for the awareness of impermanence (無常, mujō), or transience of things, and both a transient gentle sadness (or wistfulness) at their passing as well as a longer, deeper gentle sadness about this state being the reality of life.

That is also basically what the entire “synthwave” genre is about so if you’d like to hear what that concept sounds like as a song, just make your way over to Los Angeles by The Midnight.

Link roundup for January 29, 2023

Distractions, monk productivity, and the importance of “between-time”

Sometimes the internet seems to think about the same things at the same time. Last week we were all in on meetings (see here, here, here, and here), and this week we’re all talking about distractions. Here are three excellent articles about this topic that all came across my feeds this week.

First, there is a new interview with the father of deep work, Cal Newport (NYT gift article link). He talks about context switching and “slow productivity”—and it’s really good:

I’m trying to develop this notion of productivity that’s based on, at the large time scales, the production of things you’re proud of and that have high impact, but on the small time scale, there’s periods where you’re doing very little. […] So how do you actually work with your mind and create things of value? What I’ve identified is three principles: doing fewer things, working at a natural pace, but obsessing over quality. That trio of properties better hits the sweet spot of how we’re actually wired and produces valuable meaningful work, but it’s sustainable.

Matt Reynolds has a catchy title in Wired: Easily Distracted? You Need to Think Like a Medieval Monk. It’s a fun exploration of how medieval monks were, as he calls them, “the original LinkedIn power users” who kept trying to one-up each other with how distraction-free they were living:

These kinds of stories reminded monks just how hard it was to stay focused. They weren’t expected to be concentration machines. They too would come up short every now and then. “Acknowledging that upfront is a kind of compassion,” says Kreiner. “Monks are really good at being compassionate to each other, and to how hard it was to really follow through on stuff.” Freeing ourselves from distraction is really difficult. We don’t have to feel awful about not always matching up to our lofty goals.

And finally, in a short read Mandy Brown talks about the importance of Between-time:

We live in a world full of distractions but short on breaks. The time between activities is consumed by other activities—the scrolling, swiping, tapping of managing a never-ending stream of notifications, of things coming at us that need doing. All that stuff means moments of absolutely nothing—of a gap, of an interval, of a beautiful absence—are themselves absent, missing, abolished.

If I had to find a thread through all these pieces, it would be this:

  • Not every moment needs to be filled with work that produces output. Cal Newport calls this working at a natural pace: “one with more variability in intensity than the always-on pace to which we’ve become accustomed.”
  • Everyone gets distracted. Have some grace for yourself, and others. And try to distinguish between “distractions” (filling time with stuff) and “between-time”—those real breaks that we all need but get so little of.

The one thing missing from UX today? Hope

This is a wonderful essay by Vivianne Castillo that encourages designers to hold fast to the belief that things could be better for users—and for themselves. From The one thing missing from UX today? Hope:

Today, it’s clear that many designers are feeling overwhelmed, disillusioned, and even unsafe within their organizations—and design leaders are recognizing that conversations around burnout and stress aren’t quite cutting it. I’ve found a deep sense of comfort in the words of American activist, grassroots organizer, and abolitionist Mariame Kaba: “Hope doesn’t preclude feeling sadness or frustration or anger or any other emotion that makes total sense. Hope isn’t an emotion…Hope is not optimism. Hope is a discipline… we have to practice it every single day.” 

Kaba’s quote is a reminder that the answer to feeling hopeless isn’t toxic positivity or forced optimism. The answer is to make our engagement with hope a discipline because of what’s at stake if we don’t: namely that designers will begin to believe that a better future is not possible within our lifetime.

She goes on to provide examples of how to uphold a comittment to hope in creative, human-centered ways, specifically as it relates to values of belonging, integrity, and power.

Product managers are responsible for team safety

Matt LeMay’s post on how to build safety into team communication might not immediately seem that relevant to product management, but Why is Psychological Safety at Odds With the way we Work? is an excellent reminder for all of us:

Now let’s talk about the product managers who are willing to take on the individual risk that comes with creating psychological safety for their teams. These product leaders often don’t have the opportunity to step into those big “visionary” roles – not because they lack vision, but because they are so busy doing the emotional labor of cleaning up after the other product leaders who are making those big, lofty promises. These are the product leaders who earn the trust and respect of their teams by helping leadership understand the real-world trade-offs that go into actually delivering products, even when leadership doesn’t want to hear about it. And here’s the thing: over time, they actually train company leadership to be better! They sharpen their organization’s focus by saying, “You can have this OR you can have that. Which is more important given our goals and constraints?” These product leaders deliver so much value to the companies they work for, and the truth is, they don’t always get rewarded for it.

Over the years I have become more and more convinced that team safety is the most important job a product manager has.

“There should be no guilt for refusing to work hysterically”

Katy Cowan’s interview with Frank Chimero is really great from start to finish, and covers so much ground on design and technology and how to think about our work. Frank’s view on the importance of not overworking yourself is refreshing, and we’ll hopefully continue to see more of this kind of thinking:

It’s really easy to think that not working full bore is somehow failing your teammates or that withholding effort is poor work ethic and moral weakness. That thought is worth interrogating, though, and it all seems kind of ridiculous once you get it out in the open. There should be no guilt for refusing to work hysterically.