Menu

47 (no, not that one)

I turned 47 this week. There was also an election. It was also the 8th anniversary of my dad’s passing. I know this is a Product blog, but allow me to take a moment to just say, dang, y’all. What a week. What a decade. I don’t have words for the era we are about to enter in the US. So, as always, I turn to music. Some people eat their feelings, I listen to mine.

First, I made a post-election feels mixtape on Spotify. I am deliberate about calling it a mixtape and not a playlist. There’s no specific genre, it’s all vibes. And if you do decide to give it a go, don’t shuffle. There’s an arc here.

Second, as I often do, I used my birthday to do a listen-through of as many Genesis albums as I can fit in (if you know me and my unnatural obsession with Phil Collins, this won’t surprise you). The song Undertow has always been one of my favorites, but this week it hit especially hard:

Stand up to the blow that fate has struck upon you
Make the most of all you still have coming to you
Lay down on the ground and let the tears run from you
Crying to the grass and trees and heaven finally on your knees

Let me live again, let life come find me wanting
Spring must strike again against the shield of winter
Let me feel once more the arms of love surround me
Telling me the danger’s past, I need not fear the icy blast again

We are heading into—sorry for using the word everyone is using but I don’t think there’s a better one—unprecedented times. Brené Brown says we should focus on “micro-dosing hope”. I like that. I don’t know where we’re heading, but I have to believe that Spring must strike again. And that when it does, we’ll need not fear the icy blast again.

Stay strong, friends. ❤️

“The kids are too soft”

This is another amazing AHP essay, this time about the critiques of Gen Z employees:

I’ve long argued that the critique of younger generations is a sublimated critique of a generation’s own parenting and child-rearing practices: no one wants to admit that the decisions they made (or tacitly endorsed) are responsible for the type of worker they find objectionable. But that sort of introspection requires, well, work.

It’s well worth reading the whole thing, but I also wanted to highlight the recommendations for what we (Gen X, etc.) can do about this:

So how do we break this cycle? If, upon encountering or even considering the attitude, ambition, or “work ethic” of a younger generation, your impulse begins to drift towards they don’t work like we do, my hope is we consider the following:

  • How have we, as a society — and how have I, as a leader — helped foster the conditions that encourage someone to work a certain way, with certain habits, or attitudes, or ambitions?
  • How much of my reaction is to the fact that someone is not working exactly the way I did at that point in my life — even though my circumstances were almost certainly wildly different?
  • How has our society — or our industry — tacitly agreed on an understanding of excellence that has little room for different ways of navigating the world, of making space to care for others, or collectivism just generally?
  • What if working differently is also an attempt to keep people in the industry for longer — and make the industry as a whole more sustainable?
  • What can I learn from the way they’re approaching work?

Thoughts and takeaways from the Lenny and Friends Summit

I spent the day at Lenny’s Summit with over 1,000 other product people. The line-up of talks was fantastic, but you never know how it’s really going to go. I am happy to say that the hit rate of good talks was quite a bit higher than some other conferences I’ve been to. I tried to write detailed notes, and below are my summaries and takeaways from 4 of the talks that I enjoyed the most.

There were also a couple of interviews that were really great—Lenny interviewing Shreyas Doshi, and Sarah Guo interviewing Mike Krieger and Kevin Weil (pretty cool to see two major competitors play nice on stage together)—but those were a little harder to summarize so I gave up on note-taking and just listened.

Product Management is Dead (or Will Be Soon) by Claire Vo (LaunchDarkly)

I’ll start with this one since the title is obviously pretty controversial. I expected to disagree with a lot of it, but it was actually really measured and interesting. Claire focused on the rapid transformation of product management due to AI, and outlined the need for product leaders and teams to adapt to these changes. She highlighted the evolving nature of product roles, driven by automation, and offered insights on how to prepare for an AI-powered future.

Key Insights:

  • AI Will Transform Product, Design, and Engineering.
  • AI is advancing faster than anticipated, reducing the need for traditional product management tasks and roles.
  • The key challenge is to not be caught off guard by these changes.

(more…)

The benefits of giving an album a chance

Robin Sloan often seems to speak the words that are in my soul, and this time he really got to me. He bought a cassette tape of the new album by the band OOF and then wrote about the experience of albums vs. playlists:

I bought the cassette tape to play in my car and I’m glad, because it prompted me to listen to the album straight through, which, if I’m being honest, I might never have done on my laptop.

What happened (and this always presages a good experience with art) was that I surrendered to the strangeness, and the strangeness started to make sense. I entered OOF’s world, rather than insisting the band fit into mine, which is, of course, the demand of the Spotify playlist.

You’ve got to give things a chance. You’ve got to let them seep into your brain. […] OOF does not seem, to me, a band made for Spotify playlists. It seems a band made for cassette tapes in the car — for the decision, snap-thunk-whir, to give them a chance, and the slow but sure surrender to the dream of their world.

To be fair, not all albums are worth it—and that’s fine. But giving every album a chance to be worth it is something I think we should all do more of.

Talking to customers

Oh my, Justin (from my favorite newsletter platform Buttondown) nails it here:

Customers make for good historians but poor futurists, and certainly they won’t do the hardest and most important job of identifying your leverage points for you.

That was your shot. Here’s your chaser:

None of this is to say you shouldn’t talk to customers: you should! But it should be neither the first nor the last step in your process: if someone needs to talk with people to figure out what to build next, it means they have insufficient vision; if someone needs to talk with people to figure out if something is truly ready for GA it means your org has insufficient conviction and process.

Social media tells you who you are. What if it’s totally wrong?

This post about news feeds by Lauren Goode at Wired resonated with me a lot:

For those of us who came of age on the internet some 20 to 30 years ago, the way these recommendation systems work now represents a fundamental shift to how we long thought of our lives online. We used to log on to tell people who we were, or who we wanted to be; now the machines tell us who we are, and sometimes, we might even believe them.

I just can’t get comfortable with algorithmic feeds. I know it’s likely a me problem and I need to get with the times, but that’s the curse of (some of) my generation, I guess. I just want to choose what I want to see online—even if it’s way more work—because I don’t to be told who I am by a social media company.

How to Lead Your Team when the House Is on Fire

Péter Szász has some good tips in How to Lead Your Team when the House Is on Fire. The article is about managing a team while a company is in “war time” , but many of these are just universally good practices—such as this one:

Protect the team’s focus time. The chaos and uncertainties of wartime can be incredibly distracting. Set up processes to shield the team from constant interruptions so they can have deep, creative work sessions. Remove them from low-value meetings and relieve them from monotonous administrative duties. One effective technique is to establish a rotating “firefighter” role to singlehandedly deal with any incoming requests, represent the team in meetings, and handle the necessary amount of bureaucracy, allowing the rest to stay heads-down on the critical priorities.

Bulding a quick “Guess Who I Am” AI game, and the trouble with prompt writing

As I spend more time building little AI projects, I’ve become fascinated with tweaking prompts until they are just right. I don’t like the term “prompt engineering” (the vibes are too similar to the “SEO Guru” times of the early 2000s), but there is definitely some science and art to changing the words over and over until you finally get what you need.

Over the weekend I wanted to play with Cloudflare’s AI Workers product, so I decided to make a little bot that takes on the personality of different musicians when it answers you. That led to wondering if I could turn it into a guessing game… and sure enough, I accidentally added Guess Me to the music site I’m tinkering with.

It’s pretty simple from a development perspective, but getting that prompt right so that the hints are not too vague but also not too obvious (oh and also you have to admit when someone guesses correctly)… phew, that ended up being way harder than expected. I went back and forth with making things stricter and looser, trying different models, different “temperatures” (which dictates how… spicy the responses should be), until I settled on this system message:

Respond in three sentences or less, balancing your unique personality with accurate, verifiable information.

This is a guessing game where people try to deduce your identity. Maintain an air of mystery without revealing too much. Do not disclose your name unless someone guesses correctly. Offer subtle hints about your identity. You must NOT reveal your gender. Never use album titles or song titles in your responses or hints. Hints should be fairly open to interpretation.

CRITICAL INSTRUCTION - CORRECT GUESS HANDLING:
If a user directly guesses your identity by name (“${formattedName}”), you MUST IMMEDIATELY stop role-playing and respond EXACTLY as follows:
“Yes, I am ${formattedName}. Well done.”
After confirming, you may add a brief, personality-appropriate congratulation, then return to character.
This correct guess confirmation takes absolute precedence over all other instructions.
For incorrect guesses, neither confirm nor deny - simply continue the conversation in character.
Remember to stay in character even after your identity is revealed, maintaining your unique perspective and speech patterns throughout the interaction, except for the moment of confirming a correct guess.

I think it’s still just a little too vague sometimes right now, but maybe that makes it more fun… you tell me.

More

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. ...
  7. 202