Brian Balfour: 10 lessons on career, growth, and life

Brian Balfour (00:00:00):
I think historically I've gotten really caught in this trap where at any moment in Reforge, it's like, "Ah, if I just solve this one thing that's X problem, everything's going to get easier." That might be landing some big hire, some executive hire, or figuring out some major lever or defining some strategy. But the reality is that the opposite is true. The more problems you solve, you just end up taking on bigger and bigger problems over time. And hoping it gets easier is the thing that just sets you up for this frustration, this anxiety, this stress. And I think switching to that mentality of getting rid of that hope and more of like, "Hmm, if I solve this thing, I get to take on an even harder thing," I think is the thing that actually reduces the stress.

Lenny (00:00:57):
Today my guest is Brian Balfour. Brian is the founder and CEO of Reforge, which is by far the best place in the world to get in-depth training on growth and product and related topics.

(00:01:08):
Previously, Brian was VP of Growth at HubSpot, co-founder of three other startups, and in my mind, Brian is the sensei of growth.

(00:01:16):
With Brian on the podcast, I wanted to do something special. So instead of going into the typical stuff that he writes about and speaks about, we instead talked through 10 of the biggest and most interesting lessons Brian has learned from his career and from his life. These come from a list that he keeps where he gathers lessons that he learns over time, which turns out is over a hundred; we only have time for 10.

(00:01:38):
There is so much gold in this episode, and I believe there is something for everyone. I can't wait for you to listen to it and to hear what you think.

(00:01:45):
With that, I bring you Brian Balfour after a short word from our sponsors.

(00:01:51):
You fell in love with building products for a reason, but sometimes the day-to-day reality is a little different than you imagine. Instead of dreaming up big ideas, talking to customers and crafting a strategy, you're drowning in spreadsheets and roadmap updates, and you're spending your days basically putting out fires.

(00:02:08):
A better way is possible.

(00:02:10):
Introducing Jira Product Discovery, the new prioritization and road mapping tool built for product teams by Atlassian. With Jira Product Discovery, you can gather all your product ideas and insights in one place and prioritize confidently, finally replacing those endless spreadsheets.

(00:02:27):
Create and share custom product roadmaps with any stakeholder in seconds. And it's all built on Jira, where your engineering team's already working. So true collaboration is finally possible.

(00:02:37):
Great products are built by great teams, not just engineers. Sales, support, leadership, even Greg from finance; anyone that you want can contribute ideas, feedback, and insights in Jira Product Discovery for free. No catch. And it's only $10 a month for you.

(00:02:53):
Say goodbye to your spreadsheets and the never ending alignment efforts. The old way of doing product management is over. Rediscover what's possible with Jira Product Discovery.

(00:03:03):
Try it for free at atlassian.com/lenny. That's atlassian.com/lenny.

(00:03:11):
This episode is brought to you by Coda. You've heard me talk about how Coda is the doc that brings it altogether and how it can help your team run smoother and be more efficient. I know this firsthand because Coda does that for me. I use Coda every day to wrangle my newsletter content calendar, my interview notes for podcasts, and to coordinate my sponsors.

(00:03:31):
More recently, I actually wrote a whole post on how Coda's product team operates, and within that post, they shared a dozen templates that they use internally to run their product team, including managing the roadmap, their OKR process, getting internal feedback, and essentially their whole product development process is done within Coda.

(00:03:49):
If your team's work is spread out across different documents and spreadsheets and a stack of workflow tools, that's why you need Coda. Coda puts data in one centralized location regardless of format, eliminating roadblocks that can slow your team down. Coda allows your team to operate on the same information and collaborate in one place.

(00:04:07):
Take advantage of this special limited time offer just for startups. Sign up today at coda.io/lenny and get a thousand dollar starter credit on your first statement. That's C-O-D-A.io/lenny to sign up and get a starter credit of $1,000. coda.io/lenny. Brian, thank you so much for being here and welcome to the podcast.

Brian Balfour (00:04:34):
Thanks for having me.

Lenny (00:04:35):
So instead of going deep on the typical topics, you go into growth loops and frameworks and all that kind of stuff, what we're going to do is we're going to go through 10 of the most important, interesting, unique lessons that you've learned from your career, your work and your job.

(00:04:50):
And as we were aligning on these topics, I learned that you keep this Notion doc of lessons that you learn throughout your work. Tell us about this Notion doc.

Brian Balfour (00:05:00):
I think one of the things that I've learned over time for me, I don't know about you, is that I just don't tend to remember things unless I write them down.

Lenny (00:05:08):
100%.

Brian Balfour (00:05:10):
And in enough effort to not repeat mistakes, I basically just started keeping this Notion doc that I call 'lessons learned.' And some of these are from things that I've picked up from others, as we'll talk about; some are things that I've learned the hard way, like myself, they're kind of OG Brian lessons, and some of them from others. But I've experienced all of them in some way, shape or form.

(00:05:37):
And what I do is I literally write down a one-liner of what the lesson is and then a few sentence description. And then the way I use this is that whenever I'm thinking about a big maybe strategic question at Reforge or something else, I kind of return to this Notion doc, and usually it's like two or three lessons jump out to me as relevant to that specific situation and help either unblock me or guide me to a better answer or one of those pieces.

(00:06:11):
And so I started only doing this maybe, I'd call it a few years ago, and I think there's a hundred and some lessons in there at this point. So we're going to only cover maybe 10-ish percent of them today, but I've found it very useful just as a mechanism to unblock or ignite some new thoughts when I'm getting stuck.

Lenny (00:06:36):
I love that we have 10 more episodes we can do after this to go through all of them.

Brian Balfour (00:06:40):
There you go.

Lenny (00:06:42):
It's also amazing that you do two things that people wish they did. Like I imagine everybody wished they had a list of all their lessons. It's like, "Oh, I should have been doing this." And then you actually use them, which is also the thing most people don't do if they have a list like this. So it's pretty incredible you actually find a way to operationalize it.

Brian Balfour (00:06:57):
That's why you have to keep it light. That's what I learned. Because when I've read books, I used to take a ton of notes and all of that kind of stuff, but that also just ... It's not only creation friction, but it creates friction in actually using it as well. Because then it's like I got to sift through all of these notes.

(00:07:13):
So now I'm just like, "Well, what is the one liner? What is the essence of this thing?", whether it comes from a podcast or a book or a conversation I've had, those types of things.

(00:07:25):
And so that's what I've found, is it's quick to create, quick to return to, reducing friction. Maybe that should be the number one growth lesson we should talk about, but yeah, that ends up being the key.

Lenny (00:07:36):
Amazing.

(00:07:36):
Okay, well, let's just get into it. What is lesson number one?

Brian Balfour (00:07:40):
I think the first ones we're going to cover are more related to startups, founder life, company, which I've been [inaudible 00:07:47] the past seven years as founder and CEO of Reforge. We'll cover some growth ones later.

(00:07:53):
But one of them that I have just felt so strongly with in my entire career and what a lot of Reforge was founded on, but I didn't find the words for until I was listening to something by Frank Slootman, is just inspect the work and not the person.

(00:08:12):
And what that really means is, and the way that Frank puts it, is I just think it's really hard to judge a person from a conversation, whether that's a hiring conversation, a performance conversation, or something else. That just never resonated with me.

(00:08:31):
And what it's saying instead is actually trying to draw a conclusion just from a conversation is honestly kind of bullshit. You just have all these biases involved. And instead of trying to just inspect the person from the conversation, it's like, how do you go to the work? How do you see what their output is, the things that they've either historically created or currently created? Because that's, in the work environment, ultimately the thing that shows you what this person is capable of, how they approach the work, who they work with; all of these things that are a much more meaningful signal than asking, "Tell me about a tough situation you faced in your career," those types of things.

(00:09:17):
And so I've always applied this from day one of Reforge. Even in our hiring combos, 80 to 90% of the decision is based on either some type of portfolio review or what we call a simulation. A lot of people call them exercises.

(00:09:34):
And I get a lot of pushback from that internally from my team because it's a lot of work to come up with these things, it creates friction in the hiring pipeline, all of these types of things. But every time I've made an exception on one of those things and said, "Okay, [inaudible 00:09:50] not do it", I have regretted it. I have flat out regretted it.

(00:09:53):
And so I think this is one of those things. When you're actually trying to make a decision ... So much of our work is based around people; trying to judge a person or come to a decision just from a conversation on the surface almost always misleads you. And instead, it's really just, how do you just go look at the work, the actual assets and things that they have helped create and bring to life in this world? Because I think that tells you so much more about the person.

Lenny (00:10:20):
You touched on this is useful for hiring, but also performance, like how they're doing at the job, right? There's always just like, "Here's what I've done", but you look at what they've done and it's like ... I don't know.

Brian Balfour (00:10:28):
Yeah. Well, because even ... Especially as a company grows, there's all sorts of processes to put somebody up for a promotion and all that kind of stuff, and the way a lot of those processes are designed is the individual that's going up for promotion tries to tell a story about what they have accomplished and then the manager's going to advocate for them. And I think in that process, there's just too many opportunities to either twist what actually happened or there's all sorts of biases that end up involving.

(00:10:59):
And so me as a potential decision maker on a yes or no on that decision, all I have to go off of, being multiple steps away from this person's work, is essentially these words that are being promoted. And how can I actually make an accurate yes or no decision on that? I can't.

(00:11:18):
And it works in the reverse direction too. People who are doing amazing work, but maybe not the best at advocating for themselves, or maybe have managers that aren't doing the best job at advocating for themselves, end up feeling disenfranchised and forgotten and just a lot of bad feelings emerge. And that's how you lose essentially these really talented people.

(00:11:40):
So even in processes like that, it's like, how do you surface the person's work over the past time period so that the ultimate decision maker can look at that work, go straight to the source rather than relying on this game of telephone that's happening as well?

(00:11:58):
And so something that we've started to try to implement at Reforge, what we're doing it very slowly, is building in regular processes for people to record the work that they've accomplished internally, kind of keep a log of it, the things that they've helped create and ship, so that when it comes to those conversations, it's already easily packaged and can be surfaced as part of that process.

(00:12:23):
So I think it works in a bunch of different avenues, but it just kind of comes back. There's so much more you can glean from inspecting the actual creations of somebody than just a surface level conversation.

Lenny (00:12:39):
Amazing.

(00:12:40):
Just one more question before we get to our next lesson; along that same line you just mentioned of just how to actually do this.

(00:12:46):
So you mentioned exercises in the interview. I think the extreme of that is something Linear does, which I recently learned about, where they have a work trial where they work with the team for five days, one to five days. You just mentioned keeping track of your wins. Is there anything else you can share of just how you actually implement this sort of lesson?

Brian Balfour (00:13:04):
Well, I think it's not even wins. It's like a log of what you've helped ship and your role in that piece. Because even if it's not a win, it's possible that you did some really amazing work, but there's all sorts of other possible circumstances for why it ended up not being a win.

(00:13:23):
And that's also what gets lost I think a lot in these processes, is that somebody could be doing really amazing work, but maybe it's not an obvious win from the metrics or some other perspective, however else it's being judged, and you never do that.

(00:13:42):
And so I think where we started with this, the question is, how do you make it super lightweight? And I think internally what we've been trying and we've been trying to figure this out is it's not about writing a book about your work every couple of weeks, right? It's grabbing a couple screenshots and writing down a few bullet points of how you participated in creating and shipping this piece.

(00:14:04):
I will also say that this also keeps the emphasis on things that have shipped to end customers, which is the ultimate goal of most functions. You know, finance is a little bit different, like some of these internal functions, where their customers are the internal employees, versus I think ... We even had a pattern of this in the past at Reforge is people put a lot of emphasis on creating the awesome internal document. And it's like, "Look, you can create some awesome internal document, but if that's not translating to shipping something that's impacting the customer, that's a loss for the company." And I think once again, a lot gets caught up in these processes, where the judgment gets placed in the wrong places.

(00:14:49):
And the last thing I'll ... For a quick plug; Reforge has created this product called Artifacts, which is a place to both store and showcase the things you've actually created in your work. You can think about it as a portfolio or GitHub for everybody. And that could be ... Look, if you're a manager and creating performance review processes or career ladders or interview simulations, all these types of things, that is work that showcases what you're capable of as a leader or a manager. Or you might be an individual PM and be involved in shipping a feature. And so we've created that place to not only store and showcase that stuff, but for folks that are coming along and solving a similar problem after you, they can use those things as ingredients to potentially solve their problem in a slightly similar, but different way as well. Similar to open source code.

Lenny (00:15:38):
On Artifacts, how do people find that?

Brian Balfour (00:15:39):
You can just go to reforge.com and sign up. It's right there on the homepage. You could also just go to artifacts.reforge.com. I have a bunch of mine posted up there, including the original doc I wrote for my hypothesis around Reforge seven years ago. It's an interesting blast from the past around that to see what I got right, what I got wrong. And some of the lessons we'll talk more about today.

Lenny (00:16:01):
Awesome. Okay. And we'll link to that in the show notes.

(00:16:03):
Okay. Lesson one: inspect the work, not the person. What is lesson two?

Brian Balfour (00:16:07):
Lesson two: tell me what it takes to win, then tell me the costs.

(00:16:12):
And I couldn't remember quite where I picked this up, the language for this up. It might be from Bezos, so some listener can probably credit for me.

(00:16:20):
But a problem that I've experienced, especially as my team at HubSpot grew or the team at Reforge has grown, is that as the team grows, a lot more of the initiatives and ideas obviously come bottoms up from the organization. But oftentimes, by the time it would get to me, the person would've taken an approach or all of these filters would've gotten put in place. They would be thinking, "Well, I don't want to propose something that's going to get denied", or, "This might sound a little bit too wild and I don't want to be interpreted that way", or, "Somebody else in the organization told me that this is going to be a lot of hard work." Right?

(00:17:02):
And so by the time it gets to the person that is either green lighting the project or funding the project or making that decision, it loses the ultimate thing that you need to achieve, which is, in startups, you basically just have to do whatever it takes to win. And so the saying is, "Well, just tell me that first, and then even if the costs seem really high, now we can collaborate on, 'Well, what might be a way to approach this where the costs aren't so low?'"

(00:17:36):
But I don't want my team spending time on watered down things that aren't going to ultimately help us win. That's just a waste of time and a waste of resources. I would rather be having the conversation on, "Well, here's what I think it's going to take to win at this particular item. Now we can be having the conversation of, 'Well, how do we actually go do that?'" That's the conversation I want to be having.

(00:18:01):
But if I've got to be pushing the team of like, "Hey, this is too conservative," or, "This isn't going to be enough," or, "I don't know if it's going to be worth the resources," I don't want to be pushing the team. I want the team pushing me, and then we can start to pare it back to figure out how to actually achieve this thing.

Lenny (00:18:17):
This touches on a lesson that comes up a lot on this podcast is this idea of working backwards from the ideal instead of working forwards and incrementally getting to something, and then it's just like, "Here's the perfect world. What would it take to get there?" Maybe we'll never get there, but it's a nice forcing function.

Brian Balfour (00:18:32):
In my hundred or so lessons, I have a different version of [inaudible 00:18:35] that one is, which is define the ideal end state and then iterate towards it.

(00:18:41):
That ends up being a little bit tricky in teams to implement because people can very much attach themselves to that ideal end state. But the thing is you have to revisit that ideal end state every so often and revise and update and iterate on that as well. Because you identify, you define this thing, you iterate towards it, you learn some things, and you're like, "Hmm, that ideal end state isn't quite right," or, "I need to push the horizon out a little bit more, and so I need to update and redefine it."

(00:19:11):
So the key on those things is, how do you land that ideal end state to align the team to iterate towards it, but not in a way where folks are like, "Well, the pixels didn't end up like this," or, "We said we were going to build this exact feature, but you said X, but we're actually now doing Y." And it's really hard to land that in-between of, "We're not going to do this exact set of things, and this is about directional alignment, but we want you to work towards making this thing a reality."

(00:19:46):
And then the second part is just finding the time to take the step back to reupdate that ideal end state. I think that's the other component of that, that there's a lot of friction there and it's just hard to find that time in those types of things.

(00:20:00):
But I actually think that is a better version of yearly planning than what most people do with OKRs and stuff. I think most people would be better served just working in product visuals, saying, "Ooh, how might we want the product or the user to experience the product a year from now?", and giving that to the team. That is way more meaningful, I think, for folks, those visuals, than a nicely formatted set of OKRs.

Lenny (00:20:25):
Wow. I love that.

(00:20:27):
Do you work that way? Do you try to work that way?

Brian Balfour (00:20:29):
We started working this way about, I'd say four or five months ago.

(00:20:34):
We went through a few crazy years at Reforge where everything we were shipping was working and we were just trying to keep up with all of the growth. And then of course when all the macro stuff hit a year or so ago, we were kind of in the bullseye of it, being in the L&D space, a lot of our customers in tech, all of these types of components.

(00:20:55):
And I think in that crazy period, we had taken multiple shots at different planning processes, and they were all disasters, to be frank. They were all disasters.

(00:21:07):
And we had so many smart people around the table who had gone through these processes before, but I think when you're in that incredibly fast-growing stage, or you're in the earliest stage where you're landing a bunch of new bets that are a bit ambiguous and it's more like product marketing fit mode, kind of closer to that end of the spectrum, I think you're much better served by incredibly light planning processes where 80 to 90% of the assets produced are actual visuals of the experience.

(00:21:42):
It doesn't have to be product visuals either. I've started forcing marketing teams to show me what the potential marketing assets might be rather than giving me a Notion doc. Or we do a bunch of stuff on the supply side of our network and I'm like, "Well, what is a customer facing asset? How might they experience this?" Because we're going to have a way more productive conversation over that type of asset than a bunch of words on a Notion doc.

(00:22:09):
And so we have started working like this in the past six months. We found it way more effective.

(00:22:14):
Now how long that can last and how long that can scale: huge question mark, right? All of these processes, OKRs, all these kinds of things, they've been created for a reason in scale. But I think where we're at as a company, you know, 75 people, still landing a bunch of new product bets, trying to iterate ship quickly, keep the coordination costs down low, all those types of things, we're finding this method to be far more effective.

Lenny (00:22:40):
And it doesn't matter if it can't scale because you're going to change it anyway. Right? The way I thought about planning always, it's just the best idea you have at the time, "Let's just do it this way."

Brian Balfour (00:22:49):
Yes.

Lenny (00:22:50):
In terms of org and strategy. Like, "This is the best idea right now. We're going to rethink it anyway in six months if things are going well; especially if they're not going well."

Brian Balfour (00:22:57):
Yeah.

(00:22:58):
And that's why you want to get it out as fast as possible.

Lenny (00:23:00):
Right.

Brian Balfour (00:23:01):
Whereas I think in a lot of planning processes, you get those things out really fast, and then 80% of the process is churning on the last little bits that ultimately don't matter in the end.

(00:23:14):
And I think that's the piece that feels just awful to the team, and it makes these things drag on for a really long time; it's also what gets people really attached to the plan and more upset when you ultimately do change things, like you were saying.

(00:23:31):
So I think that's why you need to find methods to just get those big chunks out incredibly quickly and then move on, right? Like, "Hey, move on. Start shipping, start iterating towards that ideal end state." Because that's going to help you update whatever that new ideal end state will be in the future.

Lenny (00:23:51):
There's all these bonus lessons that are coming up as we're going through these lessons, but just to close the loop on this lesson, it was 'tell me what it takes to win and then tell me the costs.'

Brian Balfour (00:23:59):
You've nailed it.

Lenny (00:24:01):
What is lesson number three?

Brian Balfour (00:24:03):
Ooh. Lesson number three is one that I've learned the hard way, and I'm still trying to improve that myself. And this one's very much for founders, which is just, 'problems never end, and that's okay.'

(00:24:20):
Here's what I've personally experienced, and I've talked to a lot of founders about this as well, where I think historically I've gotten really caught in this trap where at any moment in Reforge, it's like, "Ah, if I just solve this one thing that's X problem, everything's going to get easier." That might be landing some big hire, some executive hire, figuring out some major lever or defining some strategy. But the reality is that the opposite is true. The more problems you solve, you just end up taking on bigger and bigger problems over time.

(00:24:59):
And hoping it gets easier is the thing that just sets you up for this frustration, this anxiety, this stress. And I think switching to that mentality of getting rid of that hope and more of like, "Hmm, if I solve this thing, I get to take on an even harder thing," I think is the thing that actually reduces the stress.

(00:25:24):
And so this was one that I've also felt for many, many years, but had a tough time finding the words for, and then Ray Dalio had this passage in one of his books that just hit the bullseye. And so his passage, which we've actually worked into the cultural values at Reforge, is, "Every day there's going to be problems. Some big, others small; sometimes in waves, sometimes slowly. But they're never going to end. The more successful we are, the bigger our problems will be, and how we react to those problems is up to us. To achieve our goals, each individual must be a problem solving machine." He calls it the 'problem solving machine.'.

(00:26:02):
I think there's some adaptations in there-

Brian Balfour (00:26:00):
He calls it the problem solving machine. I think there's some adaptations in there, but I thought that captured it so well. And when I find myself getting caught in this, oh, if we just solve this one thing, life will be so much easier. I kind of return to this statement. Not only to remind myself that that's not true. But to try to switch my framing around of how to think about the problem. But learning this, it's a grind. It's a hard mentality switch for I think a lot of founders.

Lenny (00:26:32):
This reminds me a number of things. One is just I heard someone describe basically any leadership job as your professional firefighter, you're just putting out fires all day.

Brian Balfour (00:26:41):
It is true. It is true. Those are the things that bubble up. The things that are going easy, the things that are going great do not bubble up. And so as a result, yeah, you end up being like this catcher for all of the problems. And I think that's why a lot of people end up in these management and leadership roles and then they just hate them. They're not good at them. And they're not good at them because they don't like it. Both of those things end up being true.

(00:27:13):
And a lot of that has just been driven by our construct of how people think they have ... what they have to do in order to progress in their careers is like the only way to progress in my career is through management. And there's three components of that. There's title, most people view that as a higher social capital thing. Most people see that's the only way that I can get higher compensation as part of that. As well as getting more compelling roles in my career.

(00:27:42):
So this is also something that we've recently changed in the past six months at Reforge. Which is through a lot of the macroeconomic changes, we massively flattened the org. We converted a lot of managers back into what we call Captain IC roles and-

Lenny (00:27:59):
Captain IC. Ooh.

Brian Balfour (00:28:00):
Yeah. Yeah. We have this framework called players, coaches, captains, and we talk about a little bit of the differences. And it helps distinguish the different type of leadership between senior IC and a manager. A manager is more of a coach, they're kind of coaching from the sidelines. And IC is like leading from being on the playing field. And those two things are very different. We kind of put that in place. We changed our entire compensation structure so that there is zero compensation trade off, whether you just want to keep growing as IC and stuff. There's more of these captain roles internally than there are manager roles internally. We've created the same titles for all of the levels, so people don't feel like they're making a trade-off on that external signaling factor.

(00:28:45):
We give all the strategic problems to the captain level IC roles. The managers and coaches are purely around hiring, coaching, positioning players on the field. Identifying problems, but then handing those problems off for others to go solve. All of these types of things. But one of those things that's really bothered me for a long time is that you end up on this manager death cycle. When people think that's the only way that they can progress or the only way that they don't have to make these trade-offs, you end up with a lot of folks in those roles who are neither good at them or don't really want to do at them. And oh, by the way, you've also taken your star IC players off the field in the process of all of that.

(00:29:31):
And then they go and just repeat the cycle. They create meetings and processes and all those things because what managers are supposed to do. And then they coach their team as that's the way you progress in this org. The whole thing repeats itself and it ends up being a really big mess. And so I think a lot of these principles are not new, especially in software engineering. I think that's where they've been around the longest. But we've applied it to every single function within the organization. And I think we'll take further steps in the future to even compensate the captain IC roles higher than the managers to essentially really provide a counteracting force. And people have to make a negative trade-off to become a manager, to make sure that people who end up in those roles are the ones who truly want to be there and truly do that type of work. And be the problem catcher, that type of work as part of it.

Lenny (00:30:24):
I feel like this also just a very common theme now across companies. I feel like if you haven't written about this, I think just sharing this in depth would be really useful to a lot of people. Because I think a lot of startups are trying to think about this.

Brian Balfour (00:30:34):
I think a lot of folks have really come to this realization through some of these hard times where a lot of pressure gets put on prioritization and budget cuts and stuff. I would go as far to say as I think this is where the world is headed. All of this AI tooling is going to give these super ICs, these captain level ICs even more leverage in solving problems and their creation abilities as part of that.

(00:31:03):
And so I think in the future, what we're going to see ... and I'm not the first one to say this, there have been others like Scott Belsky and others that have written about this. Which is just, I think the future is actually companies that are ... they're much smaller teams where all of these AI tools are giving one person a wider set of creation abilities. And as a result, you don't need as many people to solve the same size problem as you want to. And that's great. There's less coordination, there's less all of the things that people end up hating their jobs over. Whether that's writing updates and reviews and all of that type of stuff. I think it's a very positive thing and as a result, we're going to see happier people, happier companies, and more creative output as part of it. And so I don't know. I think the future favors these super IC types over the manager types.

Lenny (00:31:58):
I'm so curious if that's how it ends up playing out. It all makes sense that that's where things would head if AI gets powerful enough. But there's also these incentives that just drive companies to hire. It's like, oh, right, we could do more. Why don't we hire more engineers? Oh, we could build this team. We could go faster.

Brian Balfour (00:32:12):
It is so hard. This is something we've also put in our cultural values, which is our second cultural value is small teams do bigger things. And we have some guidelines on there of we only add somebody to the project when we feel like it's absolutely necessary, we know what the right next steps are, all those types of things. But I think if you could sum up the last two years is that we basically funneled a ton of capital and people into things that were kind of working, but not fully working. And I think that's where a lot of companies found themselves. Including Reforge, we funded some of those things and we had to unwind them.

Lenny (00:32:50):
Which makes sense. As a company, you're looking for new things that will grow and become huge opportunities. So I don't think there's anything wrong with that. It's like we're just going to plant all these seeds, we're going to try stuff, see if anything blows up. And then we double down, like in a good way. I guess so.

Brian Balfour (00:33:05):
I was going to say-

Lenny (00:33:06):
[inaudible 00:33:06] really normal. I think a lot of people dislike all these companies investing in all these new ideas and random things, when that's really how you build another business line or you find and unlock for growth. That's pretty normal.

Brian Balfour (00:33:20):
Totally. When we went from one product to multi-product at HubSpot, we seeded multiple bets at once. And only a couple of them ended up making it through the filter, which ended up being the CRM and the sales tool as part of that. And then there was projects we ended up killing and unwinding as part of that.

(00:33:39):
But the key about each of those bets was that we seeded each of those bets with a very limited amount of funding in a very small team. There was still the constraints involved. And I think where the mistake ends up happening is you kind of have this thing that's working but not really. And because you've got all these other people sitting on the sidelines or this cash sitting on the sidelines, you end up piling that stuff in there. And when you tend to add those things to stuff that are only kind of working, it gets worse, it doesn't get better. And that ends up creating a lot of issues.

Lenny (00:34:13):
Which is that a value? What is it that you have about small teams?

Brian Balfour (00:34:17):
Yeah, just small teams do bigger things. We felt like we needed to like-

Lenny (00:34:20):
Small teams do bigger things.

Brian Balfour (00:34:20):
Encode this in us to be a forcing function for us going forward.

Lenny (00:34:27):
All right, all these bonus lessons. You're just full of lessons, Brian. Okay, so I'm going to close the loop on lesson three, which is problems never end and that's okay.

Brian Balfour (00:34:36):
Yes.

Lenny (00:34:37):
All right, lesson four.

Brian Balfour (00:34:39):
All right, now we're getting into the product and growth lessons. This one I actually learned at HubSpot, which was the year is made in the first six months. And where this really comes from is that I think especially when you're going through planning or thinking about growth and milestones and hitting those goals and looking forward in that way. This is particularly relevant as everybody's probably going through yearly planning right now. Is that I've seen a lot of plans where you realize in the first three to six months you kind of have a line of sight to what the constraints are and what you can actually do and the limitations of those things. And so in the first three to six months of a year, your growth goals end up being kind of realistic, kind of on target. But then you're like, oh, I've got to hit this ambitious target, so I'm going to build this inflection point in the back half of the year to hit that goal.

(00:35:36):
The reality is that's just not how it works. To make your year, it's really about the first six months and the things you accomplish in those first six months. And the reason is for quite a few products, most products, this isn't true for all products. Is that the buying cycle or the decision window for a lot of customers is so long that by the time you get to the second half and you do the calculation of like, well, if we put this thing in place and the time it takes to impact a customer and then the time it takes for that customer to make the buying decision, you're already into the next year when you put those things in. This is really true for SaaS, where the buying windows could be anything from a few months to up to a year long, depending on what type of market that you're tackling.

(00:36:31):
And so if you don't do the things in the first six months, the options you're left with to actually influence the numbers in the back six months of the year is incredibly small. Incredibly, incredibly small. Now, this might be different for a consumer social product where the friction is very low and there is no buying things, and maybe I can pull some levers like paid acquisition or stuff that have really short time windows. But even in those products, when those products tend to be more influenced by things like viral loops and working on engagement and retention, the amount of times it takes to build and ship those things and then have it propagate through the user base and actually impact your numbers ends up being longer than most people think about when they're thinking through the next year. And so anyways, if you want to hit your year number, it's all about the first six months. Otherwise, you're being a little bit unrealistic with these very back weighted, second half plans.

Lenny (00:37:33):
Something you didn't mention, which is also just reorgs. You often just rethink everything halfway through. It's like, oh shit, the world has changed. And so you're probably not even going to get to that back half the way planned.

Brian Balfour (00:37:43):
Yeah, that's fair. I think it's just a human tendency to essentially overestimate how fast ... not only how fast you can do something, but how fast it will take in effect. Especially this becomes even bigger, the larger your customer base becomes. Because the larger the baseline you're working with, the larger the number you need on the new thing to actually show a meaningful impact. And so I think it's just very easy for us to overestimate those things when we're going through that type of forward-looking thinking.

Lenny (00:38:20):
Awesome. Okay, lesson four. The year is made in the first six months. What is lesson five?

Brian Balfour (00:38:28):
Okay, this is probably one that I think about the most. And comes up the most often, not only in Reforge courses, but investing, in advising. Which is growth is a system between acquisition, retention and monetization. You change one, you affect them all.

(00:38:46):
We've written about this a ton, you've written about this to some degree. But I think people underestimate how deep this lesson goes. And it's not just about understanding your system, which is the growth model. Understanding that if you do change one thing, you have to change the other one. But it's also understanding when you have a problem in one area, sometimes the solution is in a different part of the system. So a lot of times retention problems are created because you're acquiring the wrong folks. Or a lot of times monetization issues are stemming from engagement problems. And so what I've often found teams to really do is that they identify the problem, which is like, hey, we might have low revenue retention or low revenue conversion or something like that. And they go straight to trying to work on levers within that specific part of the system. But without taking the step back to say, well actually what part of the system is creating this problem? It might actually be something within it. Maybe we just have terrible pricing pages or something of that nature or terrible dunning flows.

(00:39:58):
But I think oftentimes the actual solution, the actual lever to move that problem ends up being in a different part of the system. And so this system type of thinking is probably the number one thing that I think separates great folks who work on growth from your average good folks. I think the average good folks get all of the simple levers of how to reduce friction, increase reward. They might understand things around growth loops, all that type of stuff. But system level thinking is I think the thing that separates the great from the good. Even more so in marketplace and network products because the system dynamics are amped up multiple time degrees. Yeah.

Lenny (00:40:44):
I'm curious if there's an example that comes to mind either at Reforge or at HubSpot. I'll share one from Airbnb that you made me think about. There was a team at one point on Airbnb that was just focused on retention, guest retention. They're just like, how do we get people to travel more and come back to Airbnb more? And they did all this work, all this analysis. And they just found it's related to how good was their trip? And so it became a thing that they're like, okay, there's not much we can do as a retention team, we've got to focus on trip quality and host quality. And that actually led to creating a team and putting more resources into let's improve trip experience. Which was mostly around host response rate, reviews, things like that. And so it was just like, okay, this team should not exist. We should not have a retention team, we should work on trip experience.

Brian Balfour (00:41:29):
So examples, I think early HubSpot sales days, the renewal figures on our early paid product were only okay. And I think the team we initially wanted to work on, well, what feature could we add to all of these things? But when we actually went into customer combos, what we found was that a lot of the people that the sales team were selling to ended up being either not the persona that we ended up building for or they were selling a use case that we actually hadn't designed for. And that's because look, salespeople are there, they're cranking, they're just trying to close deals. Which is like that's what their role there is for. And so at some point we had to redesign the incentives for the sales team. I don't remember exactly how it worked, but I think we did something as drastic at some point as saying, hey, if you sell this type of persona or this type of company, you will not get comped on it. And that immediately changed behavior and we started selling the right.

(00:42:32):
So that was an example where engagement and retention problems were created up at the top of the funnel. Similarly, I think in early Reforge days where we had a lot more in-person collaborative dynamics as part of our programs, we had this application process. And we learned over time that there were different behaviors and mindsets of coming ... or desires for what somebody wanted out of a program that actually created those peer-to-peer compelling experiences. And so sometimes people wanted to come into the program and all they wanted to do was network with peers and they didn't want to engage with the content at all. And then sometimes we had the opposite and they just wanted to be on their own little solo journey and not engage in stuff. And so over time, we iterated on that and we started to learn, what are the right questions to ask in order to create this better down funnel experience? Now over time, we've evolved the programs as COVID hit and we got rid of the in-person component. And all of these other changes that rendered those lessons not relevant in today's environment. But those are two quick examples that I can think of off the top of my head.

(00:43:55):
We're now in a place where we've started layering on marketplaces to Reforge, and so this system level thinking is coming up more and more daily. Because as you know, every conversation we have about demand that we end up talking about supply. And every conversation we end up talking about supply, we end up talking about demand because that's just how it works.

Lenny (00:44:16):
Good old marketplaces. I think just that lesson alone is really powerful. It's just how much the people you bring in impact every other metric and how everything looks. Like a story I often here is just paid users are just innately ... everything's going to be worse, basically. Retention's going to be worse, people that you're driving through Facebook and Google Ads and you just cut that out. And like, wow, retention went up. Wow, look at us go.

Brian Balfour (00:44:38):
Yeah. I mean, I think we both mentioned it in here, but we have this concept in Reforge that we teach around calling it good friction. And I think a lot of people are taught to always reduce, reduce, reduce friction. But actually oftentimes, the right thing to do is to add the right amount of friction to create those experiences and those right engagement metrics down funnel. It's all the incentives internally are not aligned to doing that. Because almost every time you add good friction in a product, in the very short window it's like conversion will go down and stuff, and you have to wait for those down funnel things to propagate. But people love quick wins. People love looking at those short-term metric boosts and are often rewarded and applauded for it. And so I think those types of things are actually hard to implement and even advocate for inside of organizations and products. And I think that's why you tend to see these things get chipped away at over time.

Lenny (00:45:42):
I think an example of that is how you actually, at Reforge, I noticed, you turn away a lot of people. There's tons of applications and you've just learned, here's who is going to have a good time. And we'll reject anyone that ... even though they're so excited about joining Reforge, they're going to have so many ... people are going to join, you're going to make all this money. But you just know they're going to have bad time, they're going to have bad reviews, it's going to create bad word of mouth. And so I think, to me, that's a really good example of that in action.

Brian Balfour (00:46:05):
Yeah.

Lenny (00:46:06):
Okay. Lesson five, if I can summarize, is basically that growth as a system between acquisition, retention, monetization and basically changing one impacts others. So think about if you see one thing happening here, is there another part of the system that you may want to work on?

Brian Balfour (00:46:21):
Bingo. Nailed it. All right, lesson number six.

Lenny (00:46:24):
Lesson six.

Brian Balfour (00:46:25):
Ooh, I like this one. Do the opposite.

(00:46:29):
So I think a story from very early Reforge days. So when we started Reforge the norm in the education space online, that thing that everybody was talking about at the time was essentially these short form, self-serve, low-priced, available for everybody courses. And that was the thing, I don't know if you remember the term [inaudible 00:46:58] or massively online courses. That was the rage. It was like, ah, this thing is going to revolutionize our world. And there was just so many people going after that.

(00:47:09):
And so when Andrew and I did the first growth series, we essentially did all the opposite of that. We didn't let everybody in, it was for a small group of people, it wasn't purely online, we did some stuff in person. We priced it super high, it wasn't purely self-serve. We had these live components. We essentially did the exact opposite of what's out there. I think if anybody was looking at the time, it was just very counterintuitive. It was like, who's going to really actually be interested in this? But of course the first one that we did, we had an amazing response on the first one, and then the rest is history. With Reforge and then cohort based courses became a thing and all those things.

(00:47:56):
But I think the real lesson in here is that if you want to gain traction around something, you often should be looking at what everybody is doing. And the purpose of looking at what everybody is doing is not to necessarily understand those best practices, so that you can repeat them. Your goal is to understand them so you can ask the question, well, what is the opposite? Because in every kind of major trend that everybody's pointed to, there's almost always an opportunity on the other side, on the 180. A couple other places this applies is that if you're trying to figure out a new ad channel as an example, a new paid acquisition channel. One of the best things that you can do is you can look at what all the other advertisers who are advertising to your audience are doing, like look at their creative, all that kind of stuff. And then basically figure out how to do something completely opposite, completely different. And that's how you will stand out, that's how you will get the CTRs and that's how you'll get the performance.

(00:49:01):
But most things have these gravitational forces where everything converges. There used to be this meme where every SaaS product had the same exact character design that Slack had. And I can't remember, I think maybe Intercom had it. Anyways, that was the thing. And so you can visually see this. But this dynamic I think actually takes place everywhere, whether it's in a strategy within a category, a design of a product, ad creative within a channel, a specific growth tactic as part of it.

(00:49:35):
A third quick example is that about 10 years ago when I probably really started to write a bit more on my blog is the playbook at the time that was really developed by HubSpot was that you would do a lot of high volume short content. At one point, the HubSpot team was I think pumping out like 10 articles a day. It was something crazy. And that worked at the time because they were early in the game, they had the domain authority to rank for each one of those. And a lot of people followed that playbook.

(00:50:09):
But then I and a few others in the space started writing really low volume, very long content. And I think as a result, it stood out and it performed much better among the noise. And most of my email subscribers probably came from all of those early things because it did stand out. And this is a constant game because of course, as you figure something out and you do the opposite of some piece, some other people are going to start to copy you. And then you got to take a step back and be like, well, what is everybody doing? And how do I flip the pendulum back to the other perspective? But the major lesson here is if you're trying to get traction in something, whether a new product, a new growth tactic, a new channel. The goal of learning what everybody else is doing is not so you can mimic them, it's actually to figure out how you can do the opposite of it. That's the ultimate goal of that behavior.

Lenny (00:51:09):
I love this one. I feel like you need to write a book, Brian. I feel like there's so much depth to each of these lessons that we don't have time to cover. This makes me think about, I'm reading Rick Rubin's book right now, the Creative Act, I think it's called. And he has a similar concept of just experiment as you're making things and just try the opposite. Just instead of where there's quiet, add noise. When something's blue, I don't know, make it yellow.

Brian Balfour (00:51:33):
Yeah. Totally.

Lenny (00:51:35):
And I think-

Brian Balfour (00:51:35):
You can see this now, too, with all the AI stuff is you see a new gravitate ... everybody's kind of trending towards a similar set of things. And I think the real winners are going to be the ones who kind of look at that and be like, actually, we're going to set that up as a guardrail of what we're not going to do.

(00:51:52):
I actually thought there was an ... I did a LinkedIn post about this because I saw LinkedIn doing this. The playbook right now with AI is, oh, I'm going to use AI to generate a ton of content for content marketing to rank and-

Brian Balfour (00:52:00):
I'm going to use AI to generate a ton of content for content marketing, the rank in Google, and all that kind of stuff. I thought it was actually interesting, LinkedIn has this new feature where they're actually not using AI to generate the content, they're using it to lower the friction to more UGC driven content, which ends up being a more unique, and ranking more highly. So they actually looked at that and said, "We could probably generate a ton of content using AI, and just use our domain authority to rank for these things." But they're like, "Oh, actually we're going to use AI to try to figure out how to extract more of the opposite of what everybody else is doing, which is actually human generated content." So I thought that was another interesting recent example of somebody I've seen doing something very clearly distinctly opposite of what everybody else is doing.

Lenny (00:52:53):
What's interesting here is, it's not like you need to do the opposite, it's not like the opposite will work. It's that this is just an interesting area to find new opportunity.

Brian Balfour (00:53:01):
A hundred percent, yeah.

Lenny (00:53:02):
And it makes me think about podcasts a little bit. There's always this feeling people don't have any attention span, they want short things, TikTok clips, all these things. And then there's Lex Friedman, who talks for seven hours with Balaji. That's the number one technology podcast in the world.

Brian Balfour (00:53:17):
Yeah, I'm not hooked on Lex, but I'm hooked on Acquired, which is three to four hours [inaudible 00:53:22].

Lenny (00:53:21):
That was the other one, exactly. I was just going to say, Acquired is they release an episode once a month, it's very long, they don't have any guests. That's the opposite of what usually the advice is, have guests, get on each other's podcasts, all these things, and they're the third top [inaudible 00:53:37].

Brian Balfour (00:53:36):
Yeah, we're kind of experimenting with something similar, we just released a podcast called Unsolicited Feedback. We kind of looked at it, and we were like, "There's already a ton of great interview podcasts like yours." I was like, "We could do another one, but how is that going to work? How is that going to stand out? How can we do different?" So we tried to figure out... We explored areas that would be the opposite, and so the format of the podcast is totally different.

(00:54:02):
We do bring on a guest, but we don't interview them. We actually bring in two or three product or feature releases from the past couple weeks that have been out there, and then we pretend that we are the VP of product at that company, and we just analyze it, and break it down, and talk about what we like, what we don't like, half the time. We give unsolicited feedback on it. And I don't know if it's going to work yet, it's gotten some good traction so far, and it's been a lot of fun to create. But it's just another example of trying to find the white space.

Lenny (00:54:40):
Amazing. How do people find that podcast? That's awesome, let's make sure people know how to find it.

Brian Balfour (00:54:43):
If you just Google Unsolicited Feedback Podcast, it'll come up. You can also go to reforge.com/podcast/unsolicitedfeedback as well, you can find it on our website. But we're on Apple, Spotify, all the main pieces. But yeah, we've had some spicy episodes so far, so hope you all enjoy them.

Lenny (00:55:02):
What's a good one for people to start with if they want to dive in?

Brian Balfour (00:55:04):
Well, we just released today one with Elena Verna, breaking down Airtable's surprising shift from PLG to enterprise. So there's definitely some hot takes in that one. So that's the most recent one, that's a fun one. But we've covered Zoom's product strategy, Slack's most recent announcement, a few others.

Lenny (00:55:25):
People should go check out that episode with Christopher Lochhead, where basically his pitch is that the most legendary companies always create their own category. Some people agree with that, some people don't.

Brian Balfour (00:55:33):
I'm on the disagree side of it. But that being said, that's what HubSpot did. Which is they did create a category around inbound, and the way that you get traction around those things is you define the opposite, and you play off of it. So their whole messaging was, "Hey, everybody's doing outbound marketing. Here's the problem, there's a better way, it's called inbound marketing." And then they set themselves up for that. But you have to do that in category creation, because you have to start with the thing that people understand, and then pivot off of it to teach them what the new thing is. And that was something that HubSpot did amazingly well. But even Dharmesh, the founder, talks a lot about category creation. And he's like, "Look, even though we did it, it's rarely the right answer to go do it." So I probably shift on the other end of the spectrum, which is I'm not sure. I think it can create a lot of value, but I'm not sure I agree with the ultimate premise.

Lenny (00:56:29):
Yeah, there's many camps, we're going to dig deeper into that topic on the podcast coming up. This episode is brought to you by Wix Studio, your agency has just landed a dream client and you already have big ideas for the website, but do you have the tools to bring your ambitious vision to life? Let me tell you about Wix Studio, the new platform that lets agencies deliver exceptional client sites with maximum efficiency, how? First, let's talk about advanced design capabilities. With Wix Studio, you can build unique layouts with a revolutionary grid experience, and watch as elements scale proportionately by default. No-code animations add sparks of delight, while adding custom CSS gives total design control. Bring ambitious client projects to life with any industry with a fully integrated suite of business solutions, from e-commerce to events, bookings and more, and extend the capabilities even further with hundreds of APIs and integrations. You know what else? The workflows just make sense. There's the built-in AI tools, the on canvas collaborating, a centralized workspace, the reuse of assets across sites, the seamless client handover, and that's not all. Find out more at wix.com/studio. All right, lesson seven.

Brian Balfour (00:57:42):
Lesson seven is use cases, not personas. So the trope I think is always to talk to your customers, know your customers, and it just puts a lot of emphasis on understanding the person or category of person. And then this typically results in creating some type of persona definition and segmentation that the team orients around. But I actually think most of the meat that is actionable, that helps you define, not only what to build from a product perspective, but how your growth motion and growth model should work, is actually defined in the use case that you're going after, and the different uses of your product. Some people kind of relate this to jobs to be done, we think about it a little bit differently internally in Reforge. Which is a use case is simply a combination, and starts with, what is the problem that you are trying to solve? What is the value prop that you're trying to create against that problem? What's the alternative for the user? And then most importantly, why are they choosing you over the alternative? That often goes mixed.

(00:58:48):
Those components once you define them, what the extend into are the things that actually start to help you on the growth side of the equation. Which is once I understand what the problem is, I can start to ask questions, "Well, what is the natural frequency of somebody encountering that problem?" That starts to define your retention metrics, which then starts to define your activation metrics, and it kind of works all the way downstream. You can also ask the question, "Well, what is the natural frequency of adoption of a solution around this problem?" A lot of people don't think about that. Especially in SaaS tools, which is for most SaaS products, your persona, your target customer, it actually only in market for that once every fewish years or so.

(00:59:36):
And as a result, what most people end up focusing on is just trying to capture that small sliver of those that are in market. And they don't think about, well, how do I capture the attention and build a relationship with folks that aren't in market yet, but are going to be eventually? And that was HubSpot's biggest thing when they developed the whole inbound marketing playbook and content marketing, is that most people thought of HubSpot, they just thought of them as a blog. They didn't even know that they was a SaaS tool, if you asked our audience. But what that created was the moment they were in market for that tool, where was the first place that they were going to go? They were going to go to HubSpot, and they were like, "Oh, I already have a relationship with this brand." And that ended up reducing quite a bit of friction.

(01:00:24):
The reality is that most products today are actually adopted by multiple personas, and that leads to trying to solve for multiple use cases, multiple problems across these personas. And I think that is the way more detrimental thing, than narrowing in on a single use case that might be adopted by multiple personas. So it's kind of flipping it on its head. So that's how we define everything in Reforge, is essentially, what are the different use cases that we are trying to build against? And then we might go ask the question, "Who has those problems? Who has those use cases?" And most of the time we've actually been surprised that there are people in the market that have those problems, and that have those use cases, that we would not have identified through any sort of persona research, but we can make those people successful. We can capture those people as part of the process.

Lenny (01:01:19):
So the framework you use for this use case, just to summarize, which is really interesting, I imagine it's kind of like this one pager template you use. Where here's the problem, here's the value prop that would convince someone to try this thing, here's the alternatives to what we have, and here's why they would choose us over the alternatives.

Brian Balfour (01:01:36):
Yeah. We call it the use case map, and this was actually developed originally in our Retention Program with Casey Winters and Shaun Clowes. But it's essentially what you described, it's essentially a set of rows, and there's a specific order. I might get the order slightly wrong right now, riffing off it live. But it starts with you define the problem, you then have a simple statement of who might have this problem. You then say, "Well, what are their alternatives to solve this problem?" That leads into the why, why are they going to choose you over the alternative?

(01:02:08):
It's kind of calling out differentiation essentially. And then it flows into, okay, well, what is the natural frequency of this problem? Which flows into all of your retention and activation metrics. You can also ask, "What is the natural frequency of adoption?" Which starts to help you understand more around your acquisition metrics, what percentage, how many people might be in market for this in a given year, and what we might need to do to actually sequence and capture all of that value. So that's kind of how that whole thing flows. And then some people start to layer on and solve multiple use cases over time. But the biggest thing that we find in Reforge, when we have people go through this exercise, which is the next thing we'll talk about, is that they end up mapping out eight different use cases. And we're like, "Whoa, that's way too much. You're obviously trying to solve for too much here."

Lenny (01:03:04):
Before we get to the next lesson, just to keep plugging some Reforge stuff, is there an artifact or a course for people to go check out on that specific thread?

Brian Balfour (01:03:12):
I think there will be an artifact on this soon, if there isn't live today, but we can get one live. But this actually is so fundamental, it's in almost all of our growth courses now. But the one we go deepest on, is our Retention and Engagement Program.

Lenny (01:03:25):
Awesome. Okay, so lesson number seven, use cases, not personas.

Brian Balfour (01:03:30):
Correct.

Lenny (01:03:32):
Awesome. What is lesson number eight, Brian Balfour?

Brian Balfour (01:03:35):
Okay. If there's one line that I probably repeat the most in a Reforge course, it's this one, which is solving for everyone is solving for no one. I think this extends to everything in life, and I have a couple interesting examples from this. So let me start with the product and the marketing one, because I think that's the one that... Of course I think everybody might be nodding, like, "Of course, of course we can't solve for everybody."

(01:03:59):
But that's honestly where a lot of product and growth mistakes I think come from. It's not about being specific about who you're solving for, it's about being specific about who you aren't solving for. I've found that is the thing that ends up being the one that helps being the better guardrail for a team, because for some reason when all you do is define who you are solving for or what you're solving for, going back to the use case thing, a lot of people start to justify or rationalize a bunch of adjacent use cases, or a bunch of adjacent people. And it's kind of like, "Well, yeah, it's like 50% what we're solving [inaudible 01:04:39], 50% not."

(01:04:40):
And so you have to define, you have to draw on the lines around it. And so there's an actual HBS case study done on this from early HubSpot, which is early HubSpot, they kind of built this marketing tool. They sold it to a bunch of people, they were having retention problems, they went and did all of this research. And what they found was actually they had ended up selling into four use cases, that on the surface feel very similar, but actually in reality are very different. And the four use cases was they had this mid-market... They call her Marketing Mary, a VP of marketing, who was looking for a solution in an all-in-one marketing solution, because she didn't want to aggregate a bunch of point solutions. They then had this enterprise... I think he was called Enterprise Eddy or something like that. Enterprise who was looking for a more compliant marketing solutions, secure, all of these types of things, still solving marketing, still trying to solve inbound marketing.

(01:05:36):
So on the surface seemed the same, but when you got down into it was kind of different. They also had this very small business owner, that looked like the SMB customer. But there's a very big difference between an owner of a 20 person company using your product, and that business actually having a head of marketing using the product. And their needs ended up being very different beneath the surface. And then they had this technical marketer, who wanted to get in there, and customize, and all that kind of stuff. So they ended up focusing on that mid-marketing, Marketing Mary persona and use case around the all-in-one. But the bigger thing that they did was they said, "We are not going to serve these three use cases." And going back to what we talked.... This was before my time. They aligned all the sales comp behind it, they aligned the success, they aligned all of the marketing around it.

(01:06:28):
And whenever these folks came up in the funnel and kind of indicated that they were in one of these use cases, it was like, "Ah, HubSpot is not for that." But I think this is where most teams get stretched, and where most debate comes from, is that if you haven't clearly defined who you are not solving for, you can almost always make a case for how this person or this use case fits the thing that you have defined. Now, the thing that I've realized is that this actually extends into a bunch of other places, hiring culture being one of the biggest ones. And I've seen so many super generic culture statements, and they end up being generic because they are trying to accommodate for everybody. And so they just get watered down, and watered down, and watered down. But culture is really about being super opinionated, and actually acknowledging this is not a place for everybody. And you've got to encode those values that actually say, "This is a place for who, as well as for who it's not."

(01:07:33):
And so this is an artifact that we have live, you can see ours. And so half of our values are defining the value, but actually half of the values doc is saying, "What does this not mean? What are anti-patterns to these values?" Because those are the things that actually help us understand more of, who is the right fit for the type of company that we are trying to build? And who is not right for those things? And those things get implemented in hiring, and in all of these other places. The last piece is, I've noticed this actually extends to almost all life as well. I'll give a really strange example. This is something that I've brought up before but not a lot of people know about me, is that before my life in tech, I was actually a wedding planner for a few summer summers in LA.

(01:08:21):
My uncle is a wedding planner down in LA, and I went and worked with them for a few summers, and it was actually a phenomenal experience. I got exposed to so many things I probably wouldn't have been exposed to otherwise. But one of the things that I learned in that, reflecting on that experience, is that the most miserable couples in the wedding planning process were the ones that were trying to solve for everybody, their fiance, both sets of parents, the friends, that annoying Uncle Eddie that you might have. And that's where all the stress of the process came from. And the people who tried to accommodate all of those things are the ones that didn't have their best experience for what's supposed to be an amazing and magical day. And instead, I think in that process, my uncle would try to get them to essentially say, "Who's the most important group here? Is it your family? Is it your parents? That's okay if it is, there's nothing wrong with that, but let's focus on that. Or is it your friends, or is this really an experience for you two?"

(01:09:33):
And because what you design and build around, the experience that you build around for a wedding really determines. And then when all of these edge things came up, you could ask the question, "Well, is this really for you? Or is this for this group of people or set of people that you've distinctly said, you know what, we know they're going to have a say, but we're specifically not designing this experience for them?" So anyways, I think this happens also in relationships too and work-life balance, where people are trying to solve for all the things, friends, the career, the kid, the family, the spouse, the hobbies, all the things. And at the end of the day, everything's a trade-off in work and in life, and not acknowledging those trade-offs, and not actually specifically saying what you're not solving for, I think that's where a lot of my stress and anxiety has probably come from.

Lenny (01:10:30):
This one really hits home. My wife often tells me that I'm trying to make too many people happy at once, and I have this people pleasing tendency. And she's like, "You're not going to make everyone happy, and so don't cause all these problems by making sure everyone's doing great."

Brian Balfour (01:10:45):
Well, what have you done with that? Have you gotten better at identifying the groups, to be like, "You know what? I'm making this trade off, and that's okay."

Lenny (01:10:55):
Mostly I'm like, "No, I'm not. Leave me [inaudible 01:10:58]. I don't have this problem." But no, there's definitely some of that. So it's just realizing that that's something that I try to do, and then I'm like, "Okay, I don't need everyone to be happy. It's going to be okay."

Brian Balfour (01:11:08):
That's right. That random Uncle Eddie, he will be okay. If you don't give him what he wants, it's okay.

Lenny (01:11:15):
On the values piece, I thought I just wanted to double-click on that, because I think it's really important. It's something that I learned also from this guy, Douglas Atkin, who I worked with at Airbnb, that helped us define our values at Airbnb. And he said exactly the same thing, "It's really important to make it clear who's not a fit." Not being mean or just exclusionary, but just if this doesn't feel right to you, you shouldn't work here, this is what we believe. And so a lot of values are just integrity, trust, things that are true for everyone. And so if those are your values, that's not of any value really, because everyone's like, "Yeah, every place has that.

Brian Balfour (01:11:46):
I think this also comes down to I think a common topic that you probably get asked about too, even in all your series about how we do product. You just did one on Linear, and there was actually quite a bit of Twitter response to it. Which was like, "This only works in this methodology." But there's actually multiple ways to do product management.

(01:12:10):
At Airbnb, it was from what I understand, much more designer forward. And in some organizations, it's actually much more engineering led and engineering forward. And in other cases it's much more product manager forward. And there's different types of people, different shapes of people, that help you create that environment, and are successful and happy in that environment. But it's when you actually haven't acknowledged and defined those things, is when you bring the people who don't fit onto the team, and then they're trying to pull the team in a different direction, and that creates a ton of friction. It creates just a ton of friction internally, and those are just frustrating conversations.

Lenny (01:12:55):
Yeah, that is absolutely true. I think with the Linear post, which we'll link to, just if folks haven't seen that. Something I've found, so I've done these posts on how many different companies have done product, maybe 10 at this point. And I think one of the takeaways, and I'm planning to do a little what have I learned across all these companies, is exactly what you said. There's so many ways to do it. There's the linear approach, we're not going to hire product managers for as long as we can, it's going to be designers and engineers running the show. And there's basically every other company, where they often did hire product managers really early, and it worked out great. So I think there are many ways to do it, I think a lot of it depends on who your founders are, and what they value, and the people you hire, and how much do they want to do product?

Brian Balfour (01:13:31):
A hundred percent based on founders, I think the second thing is who your customer and who you're building for are. The thing in Linear's case is that they are building a product for themselves essentially right now, that product is designed for modern software development teams who are most used by engineers and designers. So it makes sense that they have an intuitive sense of what the customer wants, whereas if they're building a product for, I don't know, call it sales folks, the engineers and designers just are probably not connected to that audience in the same exact way. And as a result, you need a specific type of way of developing product that serves that specific customer. But I agree with you, and a lot of it stems from founder, but I think also a lot of it stems from who and what you're building.

Lenny (01:14:23):
And I think in that case, it's not like the designer and the engineer couldn't do that well. It's just that is not going to be a fun job, if you're a designer that's spending time talking to salespeople all day and writing research briefs and [inaudible 01:14:37].

Brian Balfour (01:14:36):
Yeah, I think it's time too. I think when an engineer and a designer are building for another engineer and designer, they can get to those answers, get to those sense much more quickly. But I think it would consume way more time if they're building for a totally different audience that they don't really have a lot of experience or intuitive sense for. And so then at the end of the equation, you're right, it's not just them being unhappy, but they're spending so little time writing code or doing the design that it ends up being a less productive way to get to the ultimate goal, which is building a successful product.

Lenny (01:15:15):
Absolutely. The other thing that I think of, because we're going down this thread of Linear, because yeah, I was surprised by the reaction a little bit. Is that in my Notion deep dive, on how Notion builds product, one of the interview answers was just like, "We should have hired product managers earlier." They waited a long time for similar reasons, "We don't need product managers." And looking back, they're like, "That was probably not a good idea." And I think it was a similar situation, whereas designer led, building for themselves. So it's more of a question of just, when does it make sense? I just hate that there's this anti-product management [inaudible 01:15:49].

Brian Balfour (01:15:49):
That has come up.

Lenny (01:15:49):
"No product managers."

Brian Balfour (01:15:50):
Yeah, everybody's looking for that data point. I mean, that started with Brian Chesky's words getting taken out of context. But there is a anti-PM sort of sentiment at the moment, which is just a fascinating thing to watch.

Lenny (01:16:11):
It's fascinating. We're actually going to have Brian Chesky on the podcast coming up in sometime November, is the plan. So we'll talk about that. And my take there, is I just feel like there are many bad product managers that just come in and slow everything down, take over control. And so I think that's where a lot of this comes from. You ended up working with a bad PM, it doesn't help. My feeling is awesome product managers make everything better, they help you do the work you want to do, they unblock you, give you space to do the work you want to do. That's often what I find, is just great PMs make everything better, bad PMs create this sense of like, "Oh, get rid of product management." [inaudible 01:16:49]. All right, well we got two more lessons, our penultimate lesson. Brian Balfour, what do we got?

Brian Balfour (01:16:58):
Lesson nine, find sparring partners, not mentors or coaches. As you can imagine being in the L&D space, I get asked for referrals to mentors and coaches quite a bit. And I've had mentors and coaches in my career, I imagine you have too. But when I really look back and I think about, where have I gotten the most value? Meaning who has helped me progress the most? It has ended up not being one of those mentors or coaches, it's actually somebody who I would define as a sparring partner. And so I think about this in the boxing analogy. A coach, once again, is sort of giving you direction, yelling at you on the sidelines. But a sparring partner is somebody who's in the ring with you, kind of throwing blows back and forth. And the thing about that sparring partner is they probably share a common set of goals, they're probably also trying to get better at the thing that you're getting-

Brian Balfour (01:18:00):
Common set of goals. They're probably also trying to get better at the thing that you're getting better at. They are on a similar level, but maybe have some slightly different strengths to you as part of it. They're not afraid to push and throw punches to help you get better, which I think is often missing sometimes from a mentor or coach relationship. And they're playing the same sport, so a PM and a PM or however we want to take this analogy. But the most important thing is they are in the arena with you.

(01:18:35):
When you find those folks that have that set of dynamics of the right shared set of goals, they're not afraid to throw punches with you, all of that kind of stuff, they are the ones that I have found have pushed me to a much deeper level than somebody giving me some advice from the outside. Most mentorship programs are extremely forced and not very fluid. You also tend to not share a common worker goal. You can pay mentors or coaches by the hour. They're trying to achieve something different in their career than the path that you might be on, even though there's some similarities.

(01:19:17):
I think oftentimes those discussions just end up being discussions about generalities or how to get promoted or one of those things. Whereas a sparring partner is like ... I've found that person is helping me create and ship something better in the world, which is ultimately I think the thing that you're going to get judged on. So, I've solved this in a few different ways over time. At certain moments in my career, I had what I think a lot of people would call mastermind groups where I would get people at a similar stage of company as me together, we would meet biweekly or monthly and all those types of things.

(01:19:56):
Those I think work for a interesting period of time, but inevitably some people evolve in a different direction, and so the group becomes less and less relevant over time to you. And so you basically almost always have to hit a reset button to blow the group up and reassemble it, and that can be a decent amount of work. Oftentimes these end up being co-founders relationships and starting a company. A lot of times your co-founders are a sparring partner for you. Most recently though, I've been for the past about seven years, been organizing this yearly trip called Recatalyze to Mexico, which is this group of founders. We do it in December towards the end of the year where we're reflecting on the year and we go spend five days in Mexico not only getting to know each other, but inspiring each other with what all of us have been thinking about and accomplishing for the rest of the year.

(01:20:49):
But most importantly is we have these dinner combos that just get super brutally honest and deep with each other and there's tears, there's laughing, there's yelling, there's all of these types of things. It's probably the most productive few days out of my entire year at this point. And so I think there's actually a lot of ways to solve this, but what I often find is that when somebody is looking ... When they come to me looking for a mentor or a coach, they are actually better served by figuring out how to surround themselves with somebody that looks more like a sparring partner. Those folks tend to just be the bonds and the relationships that really push you for many years throughout your career versus some of these other folks.

Lenny (01:21:33):
This group sounds like your own version of the besties.

Brian Balfour (01:21:39):
It is kind of. There are some eccentric personalities in that group for sure.

Lenny (01:21:43):
Are there any folks that you want to name as examples of some of your best sparring partners or are they better kept anonymous?

Brian Balfour (01:21:50):
Yeah. There's a few folks. Two of my former co-founders from a previous company, Aaron White, who's now the CTO of Vendor and then Ariel Diaz. I think those two are both the blend of ... Well, they think so differently than I do that every time I get together with them I'm kind of energized because they have just completely different perspectives or they've been playing around with different things. But on the flip side of that too is they've also given me some of the hardest hitting feedback in my career. Maybe not even intentionally, but they know me so well that they know how to get straight to the heart of it. Whereas a coach often is poking around the surfaces trying to get to know you, and that takes an incredibly long time.

(01:22:45):
Whereas I think folks like Ariel and Aaron, they just provide a one-liner perspective to me where it's just like, oh God, I hate that you're right. It's like that type of reaction. Usually when people say something and you're angry, it's because there's a sense of truth in it, and the question is like, well, what is that truth? But getting those statements, getting that feedback is just so hard because everybody wants to please everybody. So I think those two and those two have been doing that trip with me for the longest, whereas other folks have ... We get new blood in there every year or two.

Lenny (01:23:27):
Is there an example of hard hitting feedback that you can share? And secondary question, is there a way you set up those relationships where people know they can be really honest with you? Do you just tell them, "Please be brutally honest with me," or you do it in return?

Brian Balfour (01:23:41):
I'm going to keep the examples to myself because we do have ... What is it? Chatham house rules or whatever for that trip, which is we just don't talk about what we talk about there. I will say though, if you're going to do something like this, the key is all about setting the tone. So we do have new folks in there and we do set an expectation of here are some of the types of things that we're going to cover and stuff. But that first dinner convo, it's always myself or a few people who have been there before who are the first one to open up the conversation or answer the dinner question that we might have, and they just really set the tone for how open and how deep and how hard hitting we're going to get.

(01:24:24):
And usually you do two or three of those, people follow suit and it opens up everybody else for the rest of the time you have. Whether it's a meeting or an experience like we're talking about. So some folks on that trip have talked about ... They open up with potential divorces or shutting a company down. It's like things that you're definitely not going to get in a hello, nice to meet you type of conversation. It's straight to the point. It's like, "Hey, nice to meet you. Let me tell you about this thing that's going disastrous in my life." And then the other person just tends to reciprocate and that just opens up the whole shebang. It opens people up and everything flows from there.

Lenny (01:25:08):
Sounds like an amazing group. Brian, I don't want this podcast to end, but we're on our very final lesson. Let me summarize lesson nine real quick. Find sparring partners, not mentors or coaches. What is lesson number 10?

Brian Balfour (01:25:23):
Number 10 we chose because I felt like it was fairly relevant for the times. I think where we're at in the ecosystem of things right now, especially among a lot of startups, is that people are in this process of seeing that look, they had some things that were kind of working but not working fully, and as a result they have to layer on some new bets. They have to figure out some new things. And this also goes for even fast-growing companies as well. And the principle of the lesson is essentially you need to give 2X plus the activation energy for things that need to change. The mistake is a lot of times people lean into new things, they dibble and dabble, they dip their toes in it and they take it super, super incrementally along the way. But let's say you have an existing business or an existing growth channel or something else and you're trying to layer on something new or make a change.

(01:26:23):
Well, that existing business, that existing growth channel probably has some baseline growth rate. Call it 50% year over year. It could be anything. Well, for that new thing to actually make a meaningful impact and help you drive the whole thing forward, it has to be growing at a multiple of 50% year over year in order for it to catch up and actually start to show up in the numbers, start to show up for customers and all of those things. An easy example of this is I've seen a lot of businesses where it's been primarily driven by paid marketing and they have a lot of fast growth. And at some point, of course, they're like, "Ah, we got to diversify away from this. It's too risky. CACs are rising." All the typical things that we talk about in problems with paid marketing. And so maybe they try to diversify away and their next bet is on SEO.

(01:27:18):
Well, you have to inject it with enough activation energy for that SEO to be growing at a multiple of whatever rate you're growing at paid acquisition for it to grow up and make a meaningful impact and actually achieve your ultimate goal, which is diversify away from this channel. Now, the hard part about this is going back to our earlier one, which is you don't pile all of this activation energy on at once. Because that tends to just be too much money, too many people, too many voices in the equation around new things. And instead, what I always say is you can flow through the steps faster when you have an existing baseline or an existing business to grow off of, but you can't skip steps on new things. So you still have to start with that small team getting fit on that new thing, but you have to be very quick to support and continue to provide that activation energy and not be incredibly incremental as you step into and lean into that thing.

(01:28:23):
But the net result of this is I think a lot of folks think these new bets are going to come and save them in a much shorter time period than it actually takes them to play out because of this dynamic of like, hey, you have this inertia of an existing machine. Well guess what? If you want the new thing to take an effect, its slope on its line has to be a much steeper slope than whatever your baseline thing is. And I think that's just something that people tend to overlook and something I've overlooked historically as well.

Lenny (01:28:54):
An example of this that comes to mind is when Airbnb was working on trips, it was this whole new bet of just we're going to allow you to do experiences in addition to find a home. And Brian basically focused on that full-time for a while. For a year that's the thing he was focused on. We're going to make this thing work and I'm going to PM this thing and make it work and make it awesome. And when they launched, the easy thing to do would've been like, you come to airbnb.com, what it is mostly with, "Hey, now we have trips." What he did instead is the homepage became trips plus you could book a home. And it felt crazy because everyone's coming there to book a home. That's the entire business. But his bet was like, people know that. They know they can book a home. They'll find it. Even though it became much harder to search for homes. He's like, "They'll figure it out, but we need people to understand we do this also now, and the best way to do that is just like, bam. This is Airbnb. Welcome. You can book experiences and you can also book a home."

Brian Balfour (01:29:47):
Yeah. This is especially prevalent when you're going from single to multi-product or you're going through a messaging and positioning change because you've probably invested in one type of message or trying to tell people what you do for years probably. And just because you launch it new, it's still going to take years for people to learn what you are at the new thing. And so I was catching up with one of the founders of HubSpot a while back and many years later, even though they have seven different products now in their product suite, a lot of them still refer to them as a marketing automation, email marketing company and what they're really trying to get people to think about them as is a platform company starting with your CRM. And that CRM's, I don't know, seven years old, six years old now. But there was eight years of investment in getting people to know them as a marketing company before that. And so just overcoming that inertia is ... Yeah, you've got to do things like what Brian did with the trips product to really get it to start to take hold.

Lenny (01:31:02):
Yeah. And that's always the fear people have when they're charting. Start with a wedge and just like, we're going to win this one thing and then expand and just like, oh, but maybe people only think of us for that. Such a fine line. I feel like HubSpot also is just a story I want to dig into more. It feels like there's so much to learn from their journey.

Brian Balfour (01:31:18):
Yeah, I learned a ton even from my brief time there, but yeah, that company has executed so well over a long period of time. It's just like, yeah, so many lessons there that I took away and I'm sure exist that I don't have knowledge of now because I haven't been there in some time.

Lenny (01:31:36):
Brian, we got through all 10 lessons. Is there anything else you wanted to touch on or share before we get to our very exciting lightning round?

Brian Balfour (01:31:42):
I think as we mentioned, would love folks to ... We have artifacts on Reforge, things that I've actually created like our values, like our original business hypothesis doc and stuff that you can go to Reforge around on this. And so if you want to dig deeper into them, sign for that. It's free. And would love for folks to check that out.

Lenny (01:32:02):
With that, we've reached our very exciting lightning round. Brian, what are two or three books that you've recommended most to other people?

Brian Balfour (01:32:10):
After having two kids, I get barely any time to read a full book, so my answer to this is going to be-

Lenny (01:32:17):
I know that feeling.

Brian Balfour (01:32:18):
My answer to this is going to be super old and historic. I will say that there are these books that feel magical when you get them for the first time. I remember when I read Ray Dahlia's PDF before he even came out with the book. I almost felt like I was falling into a secret about principles. I thought it was just a very interesting structured way of thinking. I don't agree with all of it in there, but there's I think a lot that I've taken away from that. Of course, like Peter Thiel's Zero to One book had that impression on me the first time. These are all, I think, old recommendations, but I think the ones that get to the root and incredible first principles thinking and try to pack an entire life's worth of lessons into a couple hundred pages versus draw one lesson out over a couple hundred pages, those are the books that I've walked away with the most.

Lenny (01:33:12):
Next question. What is a favorite recent movie or TV show?

Brian Balfour (01:33:16):
My favorite movies for some weird reason are all the movies around the great financial crisis. Why? I have no idea, but I ... Not even the great financial crisis, but Wolf of Wall Street. There's one from the bank's perspective.

Lenny (01:33:37):
Big Short.

Brian Balfour (01:33:38):
Thank you. Big Short. Yeah, yeah, yeah. I don't know why, but I think part of the reason is a lot of those movies are about what we were talking about early is a small set of people who did the opposite. They took counterintuitive bets. For some reason that really appeals to me. In terms of TV shows, there's a couple TV shows that I feel like capture the pain of creating something so well that I have just not found in others. The Bear. Episode seven of season two is I think probably one of the best episodes of television period that I have ... I've watched that episode specifically multiple times.

Lenny (01:34:22):
Is that the one where they're having dinner?

Brian Balfour (01:34:24):
No, it's where he goes and works at Alinea. And he goes through this transformation and you see both the pain and the-

Lenny (01:34:36):
The cousin.

Brian Balfour (01:34:38):
Oh God, it's so good. The other one is Halt and Catch Fire, if you want something specific to the tech ecosystem. Especially the early seasons I think capture the pain of creating something new really well.

Lenny (01:34:49):
Next question. What is a favorite interview question you like to ask candidates that you find-

Brian Balfour (01:34:55):
As we talked earlier, I don't like questions. I just like looking at the work. But when I look at the work, the questions I'm asking are typically breaking down how they thought through the work. What are the steps that they went through, what questions did they ask, how did they approach it. Because then I get a sense of how they might approach a similar problem internally at the org, and that's the thing I'm trying to gain conviction around is that if we give this person similar shaped problems that they've got the approach and process to potentially solve it. I'm not looking for them to have the answer to our problems in the interview. I just want to be confident that they have an approach to find the solution.

Lenny (01:35:40):
Is there a favorite product that you recently discovered that you really like? Either an app or a physical thing, something you bought at a store.

Brian Balfour (01:35:46):
I am not a things person. I don't like buying a lot of things, but I joke around with Adam Fishman is that I basically only buy Vuori clothes at this point. They're just too comfortable for work from home.

Lenny (01:35:59):
I'm wearing some right now.

Brian Balfour (01:36:01):
I'm literally shorts, underwear, and this shirt. All Vuori and they just came out with jackets and so that's covered as well. Now I just need them to make running shoes or something.

Lenny (01:36:01):
Yeah. Do they do underwear?

Brian Balfour (01:36:12):
I think so. Yeah. I'm pretty sure. Or they do boxer. They also have the shorts with the liner in them. That's the ultimate life hack. You just reduced one piece of clothing. Yeah.

Lenny (01:36:26):
Amazing. Yeah, I'm wearing Vuori pants right now. It's my favorite podcasting pants. What's a favorite life motto that you like to repeat either to yourself, that you share with friends?

Brian Balfour (01:36:36):
I don't have my place decked out like yours yet, Lenny. I need to do that, but I have multiple of these of the man in the arena speech. I do think that is the thing that I keep coming back to and the thing that I keep finding the value that I resonate with the most, and it's even what we try to build Reforge around is we're trying to build Reforge around the people that we create programs and stuff, these are the folks that have been in the arena. They've gotten the blood, sweat and tears to talk about. I just highly respect people who enter that arena and do that hard work, and those are the folks that I've learned the most from and want to spend my precious hours building for and spending time with.

Lenny (01:37:19):
I think exactly the same way with this podcast. I try really hard to stick to people that have done the thing and when Casey Winters came on the podcast, after he's just like, "Lenny, make sure you stay close to people really doing the work and not just pontificators." What is the most valuable lesson that your mom or dad taught you?

Brian Balfour (01:37:35):
Both my parents were teachers and so I think probably they did not understand my entrepreneurial life at all early on. Yeah, I got that elsewhere. But I do think the things that I took from my parents were just a lot of lessons around how to learn and that you can learn anything if you actually want to learn it, and I think that's probably the most valuable thing that they taught me was just how to learn and that's something I want to pass down to my kids as well.

Lenny (01:38:09):
Amazing. You mentioned Adam Fishman. For our final question, you were on his podcast, Tech Dads, I think it's called.

Brian Balfour (01:38:15):
Startup Dads. Yeah. Startup Dads.

Lenny (01:38:17):
Startup Dads. We'll to it, and something you shared that has really stuck with me as a dad now is one of your biggest lessons as a dad is that your job as a parent is to bring your kids from being fully dependent to fully independent. Could you just share that lesson for folks? Because I thought it was really powerful.

Brian Balfour (01:38:37):
Yeah. It's like a spectrum. So consider your kid at age zero on one end of the spectrum and age 18 on the other end of the spectrum, and I think your job as a parent is to move them along this spectrum where at age zero obviously they're fully dependent. You're making all the decisions for them. And by 18 what you want to do is that they are making all the decisions for themselves, and what that requires is I think a gradual process of helping them make bigger and bigger decisions over their lifespan and you just end up being an input into those decisions. That even starts at an early age where my kids are still young. They're four and one and a half, but the example I give is I start to see one of my kids playing with some toy that he loves really rough and I know he's going to break it and I can do one of two things.

(01:39:36):
I can either go and intervene and stop and take the toy away or I can get him to pause and get him to think about what might happen if he keeps playing with the toy like that and then let him do his thing. If he decides to break it, he decides to break it and he learns that lesson. But I don't know. That framework has just really resonated with me because I think as we all do, we probably have people in our lives that have a very hard time thinking for themselves and making those decisions. And so that's what my view is by the time I'm 18, I don't want to be deciding the college that my kids go to. I want to help create the environment where I'm helping them get the information they need to make those types of decisions and make decisions for themselves because I think ultimately that's what will hopefully set them up for a successful life.

Lenny (01:40:32):
Amazing. Brian, this was everything I hoped it would be. I am so thankful they made time for this. Two final questions. Where can folks find you a line if they want to reach out and how can listeners be useful to you?

Brian Balfour (01:40:42):
Yeah. You can find me in a few places. My website, brianbalfour.com. I write incredibly sporadically, so don't expect regular-

Lenny (01:40:51):
Very high. Very high-

Brian Balfour (01:40:51):
Yeah, yeah.

Lenny (01:40:52):
Very high.

Brian Balfour (01:40:54):
Other than that, just check out reforge.com artifacts. I'm pretty active within that product as well. And then unsolicited Feedback podcast, join me and Fareed Mosavat on a weekly basis where we give unsolicited feedback to all sorts of products. It's a really fun environment. And other than that, how they can be helpful for me is just for folks that are in this space that want to be part of a development community, join Reforge and listen to the podcast. That's it.

Lenny (01:41:24):
Amazing. Now we have 10 more episodes we can do to go through the rest of the lessons that you've collected over for your life. V1 is done. Brian, thank you so much for being here. This was amazing.

Brian Balfour (01:41:33):
Thanks for having me.

Lenny (01:41:34):
Bye everyone.

(01:41:37):
Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.