Sunny

← All weeks

What I’ve been reading (W27, 2023)

How Notion builds product · Excellence is a habit, but so is failure

How Notion builds product What Notion missed in the early days

There is a difference between engineers who think about product, and product managers who are out there talking to users and bringing in user feedback constantly, coordinating closely with go-to-market teams, and thinking deeply about product strategy. And I think that was missing at Notion early on.

Product development process

We have a process where at four points in the product development process, we have a “check-in” . The check-ins: The statement of the user problem A discussion of possible directions—what are the three or so high-level possible approaches to solve the user problem, and what does the team recommend? The full solution, with high-fidelity designs and everything scoped out The ship candidate, ready for a final quality check

Async work

async check-ins don’t work for some types of discussions. What are all the options you explored, and how do you think about each of them? Why did you choose them? Putting that in a doc and explaining that in writing takes a lot of time. People were spending way too much time documenting this stuff, and then when you take into account the email exchanges and then the responses and all of that, the process would drag out for quite a while.

End to end relationship in roles

We care about your view of your role and how expansive it is. “End-to-end ownership” We want EMs and PMs to have joint responsibility for everything. Both should be staring at the team, figuring out what it needs to achieve their outcomes, and be willing to do whatever is necessary, without rigidity around role definition. Ideally, the EM and PM are joined at the hip or mind-melded. And yes, the PM will not necessarily be reviewing the full-on details of a tech spec, and an EM might not be working on the details of a launch video with product marketing. But they together own the product and business outcomes. If a PM needs to have one-on-ones with engineers every week, they’ll do that, and if an EM needs to work directly with Customer Success, they will.

Hiring

One theme, for example, is that we love working with people who care about craft and attention to detail. When we interview engineering managers for product teams, we have an exercise where we give them a product spec and ask them to comment on it as if it were something their team was working on. And we’re interested in everything from what the person says about the problem statement, to how they comment on whether the work is worth doing relative to other things and the ROI to the business, to which pixels or UX elements look off.

Excellence is a habit, but so is failure

  • Avoiding bad habits is just as important as cultivating good habits.
  • Incrementally neglecting and small missteps can accumulate and lead to negative outcomes.
  • You don’t become addicted to drugs overnight. You don’t become overweight overnight. You don’t ruin relationships overnight. It happens over hundreds of moments.
  • We must become aware of our patterns of incremental neglect and then take deliberate steps to counteract them and foster healthier habits.
  • Recognizing and addressing these patterns of neglect early can make a significant difference in preventing larger problems down the road.
  • We often hear that making small incremental improvements every day can lead to great things. This popular piece of advice rings true, and it’s a powerful reminder to keep pushing ourselves forward.

Rise of AI engineer

  • LLMs created a whole new layer of abstraction and profession.
  • “Prompt Engineer” is misleading. It’s not just prompting alone, there’s a lot of glue code/infra around it. Maybe “AI Engineer” is ~usable, though it takes something a bit too specific and makes it a bit too broad.
  • ML people train algorithms/networks, usually from scratch, usually at lower capability.
  • LLM training is becoming sufficiently different from ML because of its systems-heavy workloads and is also splitting off into a new kind of role, focused on very large-scale training of transformers on supercomputers.
  • In numbers, there are probably going to be significantly more AI Engineers than there are ML engineers / LLM engineers.
  • One can be quite successful in this role without ever training anything.
  • Software 3.0 (= prompting LLMs) is amusing because prompts are human-designed “code”, but in English, and interpreted by an LLM (itself now a Software 2.0 artifact).
  • AI Engineers simultaneously program in all 3 paradigms (Software 1.0, 2.0 and 3.0)

Nobody tells this to people who are beginner

“Nobody tells this to people who are beginners, I wish someone told me. All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it’s just not that good. It’s trying to be good, it has potential, but it’s not. But your taste, the thing that got you into the game, is still killer. And your taste is why your work disappoints you. A lot of people never get past this phase, they quit. Most people I know who do interesting, creative work went through years of this. We know our work doesn’t have this special thing that we want it to have. We all go through this. And if you are just starting out or you are still in this phase, you gotta know its normal and the most important thing you can do is do a lot of work. Put yourself on a deadline so that every week you will finish one story. It is only by going through a volume of work that you will close that gap, and your work will be as good as your ambitions. And I took longer to figure out how to do this than anyone I’ve ever met. It’s gonna take awhile. It’s normal to take awhile. You’ve just gotta fight your way through.” ― Ira Glass

Smart things smart people said

  • “A great way to understand yourself is to seriously reflect on everything you find irritating in others.” – Kevin Kelly
  • “If you find the right balance between desperation and fear you can make people do anything.” – Trevor Noah
  • “The happiness of most people is not ruined by great catastrophes or fatal errors, but by the repetition of slowly destructive little things.” – Ernest Dimnet
  • “It doesn’t take much to convince us that we are smart and healthy, but it takes a lot of facts to convince us of the opposite.” – Dan Gilbert
  • “Don’t try to fix people. Just set boundaries.” – Shibetoshi Nakamoto
  • “Better to get your dopamine from improving your ideas than having them validated. “ – Nat Friedman
  • “It’s good to have people in your life who you don’t want to disappoint.” – Warren Buffett
  • “Injuries done to us by others tend to be acute; the self-inflicted ones tend to be chronic.” – Nassim Taleb
  • “The most accurate metric for your love of someone is how you feel about their flaws.” – Mark Manson
  • “Assuming you rise to the top, please remember: what made you great may not be appropriate for the next generation.” – Richard Hamming
  • “Nobody gives a shit about anything except how they feel.” – Will Smith
  • “Your capacity for gratitude is inversely proportional to your sense of entitlement.” – Mark Brooks
  • “Your calendar is a better measure of success than your bank account.” – James Clear
  • “The way to be safe is to never be secure.” – Ben Franklin
  • “There are two types of stability: active and passive … People get in trouble when they confuse the two types of stability. Relationships, for example, require attention and care. If you assume that your relationship is passively stable, you’ll wake up one day to divorce papers.” – Shane Parrish
  • “Write your obituary, then work backwards to live it.” – Buffett

Others

Substack edition

View the original post

How Notion builds product

What Notion missed in the early days

There is a difference between engineers who think about product, and product managers who are out there talking to users and bringing in user feedback constantly, coordinating closely with go-to-market teams, and thinking deeply about product strategy. And I think that was missing at Notion early on.


Product development process

We have a process where at four points in the product development process, we have a “check-in” .

The check-ins:

  • The statement of the user problem

  • A discussion of possible directions—what are the three or so high-level possible approaches to solve the user problem, and what does the team recommend?

  • The full solution, with high-fidelity designs and everything scoped out

  • The ship candidate, ready for a final quality check  


Async work

async check-ins don’t work for some types of discussions. What are all the options you explored, and how do you think about each of them? Why did you choose them? Putting that in a doc and explaining that in writing takes a lot of time. People were spending way too much time documenting this stuff, and then when you take into account the email exchanges and then the responses and all of that, the process would drag out for quite a while.


End to end relationship in roles

We care about your view of your role and how expansive it is. “End-to-end ownership”

We want EMs and PMs to have joint responsibility for everything. Both should be staring at the team, figuring out what it needs to achieve their outcomes, and be willing to do whatever is necessary, without rigidity around role definition. Ideally, the EM and PM are joined at the hip or mind-melded. And yes, the PM will not necessarily be reviewing the full-on details of a tech spec, and an EM might not be working on the details of a launch video with product marketing. But they together own the product and business outcomes. If a PM needs to have one-on-ones with engineers every week, they’ll do that, and if an EM needs to work directly with Customer Success, they will.


Hiring

One theme, for example, is that we love working with people who care about craft and attention to detail. When we interview engineering managers for product teams, we have an exercise where we give them a product spec and ask them to comment on it as if it were something their team was working on. And we’re interested in everything from what the person says about the problem statement, to how they comment on whether the work is worth doing relative to other things and the ROI to the business, to which pixels or UX elements look off.

Excellence is a habit, but so is failure

  • Avoiding bad habits is just as important as cultivating good habits.

  • Incrementally neglecting and small missteps can accumulate and lead to negative outcomes.

  • You don’t become addicted to drugs overnight. You don’t become overweight overnight. You don’t ruin relationships overnight. It happens over hundreds of moments.

  • We must become aware of our patterns of incremental neglect and then take deliberate steps to counteract them and foster healthier habits.

  • Recognizing and addressing these patterns of neglect early can make a significant difference in preventing larger problems down the road.

  • We often hear that making small incremental improvements every day can lead to great things. This popular piece of advice rings true, and it’s a powerful reminder to keep pushing ourselves forward.


Rise of AI engineer

  • LLMs created a whole new layer of abstraction and profession.

  • “Prompt Engineer” is misleading. It’s not just prompting alone, there’s a lot of glue code/infra around it. Maybe “AI Engineer” is ~usable, though it takes something a bit too specific and makes it a bit too broad.

  • ML people train algorithms/networks, usually from scratch, usually at lower capability.

  • LLM training is becoming sufficiently different from ML because of its systems-heavy workloads and is also splitting off into a new kind of role, focused on very large-scale training of transformers on supercomputers.

  • In numbers, there are probably going to be significantly more AI Engineers than there are ML engineers / LLM engineers.

  • One can be quite successful in this role without ever training anything.

  • Software 3.0 (= prompting LLMs) is amusing because prompts are human-designed “code”, but in English, and interpreted by an LLM (itself now a Software 2.0 artifact).

  • AI Engineers simultaneously program in all 3 paradigms (Software 1.0, 2.0 and 3.0)

Nobody tells this to people who are beginner

“Nobody tells this to people who are beginners, I wish someone told me. All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it’s just not that good. It’s trying to be good, it has potential, but it’s not. But your taste, the thing that got you into the game, is still killer. And your taste is why your work disappoints you. A lot of people never get past this phase, they quit. Most people I know who do interesting, creative work went through years of this. We know our work doesn’t have this special thing that we want it to have. We all go through this. And if you are just starting out or you are still in this phase, you gotta know its normal and the most important thing you can do is do a lot of work. Put yourself on a deadline so that every week you will finish one story. It is only by going through a volume of work that you will close that gap, and your work will be as good as your ambitions. And I took longer to figure out how to do this than anyone I’ve ever met. It’s gonna take awhile. It’s normal to take awhile. You’ve just gotta fight your way through.” ― Ira Glass

Smart things smart people said

  • “A great way to understand yourself is to seriously reflect on everything you find irritating in others.” – Kevin Kelly

  • “If you find the right balance between desperation and fear you can make people do anything.” – Trevor Noah

  • “The happiness of most people is not ruined by great catastrophes or fatal errors, but by the repetition of slowly destructive little things.” – Ernest Dimnet  

  • “It doesn’t take much to convince us that we are smart and healthy, but it takes a lot of facts to convince us of the opposite.” – Dan Gilbert

  • “Don’t try to fix people. Just set boundaries.” – Shibetoshi Nakamoto

  • “Better to get your dopamine from improving your ideas than having them validated. “ – Nat Friedman

  • “It’s good to have people in your life who you don’t want to disappoint.” – Warren Buffett

  • “Injuries done to us by others tend to be acute; the self-inflicted ones tend to be chronic.” – Nassim Taleb

  • “The most accurate metric for your love of someone is how you feel about their flaws.” – Mark Manson 

  • “Assuming you rise to the top, please remember: what made you great may not be appropriate for the next generation.” – Richard Hamming

  • “Nobody gives a shit about anything except how they feel.” – Will Smith

  • “Your capacity for gratitude is inversely proportional to your sense of entitlement.” – Mark Brooks

  • “Your calendar is a better measure of success than your bank account.” – James Clear

  • “The way to be safe is to never be secure.” – Ben Franklin

  • “There are two types of stability: active and passive … People get in trouble when they confuse the two types of stability. Relationships, for example, require attention and care. If you assume that your relationship is passively stable, you’ll wake up one day to divorce papers.” – Shane Parrish  

  • “Write your obituary, then work backwards to live it.” – Buffett

Others

Originally on Substack