Menu

Reading Well

I love the point Simon Sarris makes here about the importance of reading fiction, and how it’s useful for work purposes as well:

I also tend to stress fiction because I think, especially among my professional peers in the industry of software, that there is too great a fondness for non-fiction. I think this arises from a belief that superior knowledge of the world comes from non-fiction. This thought is attractive to people who build systems, but over-systematizing and seeing systems in everything can be a failure mode. Careful descriptions and summaries miss too much of the world. Hard distinctions make bad philosophy. Reading fiction helps you become an unsystematic thinker, something that is equally valuable but more elided by some engineers. It is easy to maintain an intellectual rigidity. It takes more care to maintain a loose poeticism of thought.

Why the remote-work debate stays so heated

Allie Conti frames the remote work debate really well in this post. In short, how someone feels about remote work and “return to office” is extremely personal:

I’ve given you this narration of my personal experience because, for all the talk of productivity and metrics and company culture, the topic of returning to the office is intensely personal. My needs and desires, for a variety of reasons relating to my age, finances, circumstances, health situation, and lifestyle, might be very different from those of workers who fall elsewhere on any of those axes. Some working parents have said they might value flexibility at school-pickup time. Some workers of color have raised the benefit of being free from in-office microaggressions. Recent college graduates may want to go into the office to make friends. And of course, not all workers are able to work remotely. The physical space in which one works, or hopes to work, intersects with one’s most personal choices. It collides with and reveals what people value most.

It feels like we should find ways to cater for both types of preferences. Hybrid work environments are far from an ideal solution, but it is one way to meet in the middle.

How Process Impacts Your Culture

Josephine Conneely has some excellent thoughts on the feared P-word in How Process Impacts Your Culture. I especially like going back to the purpose of adding process when evaluating what you have in place:

The aim of process in its purest form is to:

  • Facilitate ease of doing work: Design methods for teams to effectively work together, make decisions, and achieve their goals.
  • Reduce risk: Ensure company doesn’t fall foul of legal & compliance obligations or go bankrupt.
  • Ensure consistency and fairness: Aim for all customers and employees to have a similar experience in their interactions with an organisation.

The Product-Led Growth Trap

Oliver Jay wrote a 3-part essay about what he calls “The PLG Trap”, where product-led growth companies grow to a certain point and then suddenly sees that growth slow with no obvious ways through the slowdown. From the introduction to the essays, Oliver says this usually happens after an initial (and initially successful!) expansion into the enterprise market:

Quite simply, despite the complex security and administrative features you’ve launched, your product has not evolved to becoming broadly “enterprise-ready” for the majority of your enterprise prospects.

At this point, you may feel trapped–the PLG Trap. You’ve set growth expectations externally and internally based on how revenue (in particular, from the upmarket segments) has grown in the past few years.

However, what drove revenue in the past, in terms of your product offering as well as your sales and marketing motions, is unsustainable. There is no more bottoms-up, low-hanging fruit to feed the larger sales and marketing engine you’ve built. To pursue sustained revenue growth, you must tolerate a lower efficiency…only to now be punished by the public markets in what appears to be the beginning of a recession.

The essays go through several reasons why companies fall into this trap, and also how to avoid it by making smarter decision about sales, marketing, and product roadmaps early on.

How to receive feedback with grace

Some good tips here from Kax Uson on How to receive feedback—especially when you don’t agree with it:

Validate the feedback with other people. There will be times when we don’t really trust the feedback we receive, or in some cases, the people who gave them to us. This is normal. When this happens, it’s worth cross-checking the feedback with the people we trust. I like to think of it as getting a 2nd opinion vs immediately dismissing the feedback or overthinking it.

Life beyond OKRs: Tools for goal-setting

Ok, here’s the thing. I didn’t share this talk I’m doing on Thursday when it was announced because as much as I tried, I just didn’t feel like the story was coming together. Writing this talk was much harder than some others that I’ve done, but I think I finally got there last night. So with only a few hours to spare, here you go…

In Life beyond OKRs: Tools for goal-setting I’m going to talk about our team’s foundation (principles & values), how we set goals, and how we plan and execute. If that’s your thing, come join us!

Interesting Learnings from Outages

Here’s a good post from Gergely Orosz discussing Interesting Learnings from Outages. It covers internal vs. public postmortems, how investing in reliability can have bumps along the way, and how to make the difficult decision to try and fix something on the spot, or to do a lengthy restore. This point stood out to me:

“Move fast with autonomous teams” often builds up infrastructure debt. Reddit is a fast-moving scaleup where teams move fast, and it sounded like they had autonomy in infrastructure decisions. The wide range of infra configurations caused several outages, and the company is now paying down this “infrastructure debt.” This is not to say that autonomous teams moving fast is a bad thing, but it’s a reminder that this approach introduces tradeoffs that could impact reliability and will eventually have to be paid down, often by dedicated teams.

Threads isn’t depressing, it’s just not for you

I don’t think that Threads—the new Twitter-like service from Meta—is above critique. It’s noisy, it lacks a lot of features, and there seems to be a lot of desperate land-grabbing going on by various celebrities and brands. You might even say the whole thing feels off—and there is even a fairly academic reason for that feeling. In It’s Not Cancel Culture—It’s A Platform Failure Charlie Warzel reminds us about “context collapse”:

Context collapse occurs when a surfeit of different audiences occupy the same space, and a piece of information intended for one audience finds its way to another—usually an uncharitable one—which then reads said information in the worst possible faith.

We’ve probably all experienced this to some degree—you say something and it gets misunderstood or misconstrued (sometimes understandably!) by an audience that doesn’t have all the context. Anne Helen Petersen uses that concept to explain exactly why The Thread Vibes Are Off:

Twitter was for thoughts, and Instagram is for vibes—and Threads is trying to pull your Instagram feed into a Twitter format. And I’m here to tell you: THE VIBES ARE OFF. […]

What’s happening early on with Threads is that influencers are experiencing their own kind of context collapse, where their vague, sometimes vapid messages are traveling toward a different type of audience. This is pretty much what Threads feels like to me now: a place that’s ostensibly interesting (look, so many people are already here!) but is actually totally boring. It’s “fun,” but definitely not funny.

So, like I said: Threads isn’t above criticism and there’s a lot of work to be done to improve it. But I also think it’s important for the complainers to realize that it’s possible that maybe—just maybe—Threads isn’t for us. And that’s ok. One example is the constant complaints I see (and I have as well!) about the lack of a “following-only” feed, and a lot of “how could they launch without it” incredulousness. However, to that point, Sara Morrison makes this observation in TikTok is confusing by design:

TikTok is the ultimate example of how our digital world is shifting from seemingly limitless possibilities and choice—the internet of my formative years—into a controlled experience that’s optimized to know or decide what we want and then deliver it to us. And TikTok is one of the best examples of this change.

That piece is worth reading in full, but it explains how the chronological feed might be a thing of the past—and not because companies want it, but because user data shows that they want it. This is why posts like Facebook’s Threads is so depressing—which I’ve seen quoted and mentioned a lot in my various feeds—really rubs me the wrong way. It is one big wall of snark about how bad Threads is, how it should die, and how it has no redeeming qualities at all. What’s worse is that I’ve seen lots of product people quote that piece and praise it, which I find really confusing.

Yes, Threads has lots of room for improvement. I find it too chaotic (right now) for what I want in a social network. But if you scroll just a little bit it’s clear to see that people on there are having a blast—so how about we don’t judge anyone and everyone who gets on there! Isn’t having empathy for users and curiosity around certain behaviors everything in product? Shouldn’t we be impressed and interested in what we can learn from how Meta built that product to scale to 10 million users in 24 hours without a hitch?

It’s natural to get riled up about products that mean something to us, but we have to guard against blind spots when it comes to how people who are not like us use the web. It’s ok to not like Threads, but it’s not ok to negate and mock the experience of millions of people who are clearly enjoying the product immensely. Not just because it’s unkind and unnecessary, but also because we’d be losing out on a huge opportunity to learn from how that team executes.

P.S. If you are more of a visual person, here’s a 16-second Youtube video summarizing this post.

More

  1. 1
  2. ...
  3. 9
  4. 10
  5. 11
  6. 12
  7. 13
  8. ...
  9. 192