Martin ErikssonGuestChristian IdiodiHost
Yeah, even take a step back, because like I said, I want this to be a model that people use to look at their organizations, not a slavish framework that they have to like tick the boxes on, right? And there's a lot of word salad in here as well, right? Like we talk about vision, we talk about strategy, and these things mean so many different things to so many different people.

So I actually ended up taking a step back and asking, like, what are the questions we're trying to answer here? And for me, I think every organization, every product has to be able to answer five questions.

Where are we going? How are we going to get there? What's important right now on that journey? And how do we measure that progress? What are we actually going to do to move forward? What are the actions we're going to take? And then finally, how do we choose between those actions? And they sound very simple, but if you start asking these questions in organizations, again, very quickly, it starts falling apart.

And so I do use vision, strategy, objectives, opportunities, and principles to answer those.

But my point is you can use other tools, right? I know not everyone's an OKR fan.

You can use NCTs, you can use VMOST, you can use other tools to answer that kind of question about what do we need to do right now? What's important right now? And how do we measure progress? And so the tool is kind of meant to be flexible enough to allow other options.

But what's most important is that connection, the stack, and that these things connect, as we said, from the top to bottom and bottom to top so that you actually understand how everything fits together.
And I actually love that you're describing it as a mentor model than a framework.
I mean, at the end of the day, you're saying we've got these funny words we call things in product and discipline, but you're just really trying to answer the question, why are we here? Where are we going? What is important right now? How do we know we're successful? Which of those questions do you think is most commonly the hardest or missing in a company?

I think a lot of people struggle with the kind of what's important right now and how do we measure progress? I mean, OKRs are infamously difficult to get done.

But I actually find where you don't get an answer is actually the strategy question, right? How are we going to get there, right? A lot of people have a good sense of what the vision is, right? Most companies have a pretty good sense of their purpose, what they're doing, why they're doing it.

But then you actually start asking, OK, how are we going to get there? How are we going to make that vision come to life? How are we actually going to achieve that? And you can start getting very fuzzy answers, right? If you're lucky, you get something like, oh, we're going to grow 25% this year.

It's not a strategy, right? It's not a choice, but at least it's an answer to the question.

But too often you kind of get a like fuzzy, like, oh, we're going to do a bit of everything for everyone and, you know, be anything for everyone.
Okay, I want to dig into strategy, but let's kind of walk it in the way you stacked it.
Because, I mean, I've always thought strategy is the most important layer because it actually connects everything up to the tactical things that come below.
Many of them, I feel, don't have visions that actually help teams make a decision in that way.
Maybe define a good vision for me and maybe what separates a fuzzy statement from an actual real vision.

So I think a vision does have to be fairly precise, right? It definitely can't be the standard cookie cutter template, right? To be the leading slash best, you know, provider slash supplier, like fill in the blanks kind of ad lib thing that you can do.

I really learned this when we ran Mind the Product, right? So we started Mind the Product as a hobby.

Yeah, even take a step back, because like I said, I want this to be a model that people use to look at their organizations, not a slavish framework that they have to like tick the boxes on, right? And there's a lot of word salad in here as well, right? Like we talk about vision, we talk about strategy, and these things mean so many different things to so many different people.

So I actually ended up taking a step back and asking, like, what are the questions we're trying to answer here? And for me, I think every organization, every product has to be able to answer five questions.

Where are we going? How are we going to get there? What's important right now on that journey? And how do we measure that progress? What are we actually going to do to move forward? What are the actions we're going to take? And then finally, how do we choose between those actions? And they sound very simple, but if you start asking these questions in organizations, again, very quickly, it starts falling apart.

And so I do use vision, strategy, objectives, opportunities, and principles to answer those.

But my point is you can use other tools, right? I know not everyone's an OKR fan.

You can use NCTs, you can use VMOST, you can use other tools to answer that kind of question about what do we need to do right now? What's important right now? And how do we measure progress? And so the tool is kind of meant to be flexible enough to allow other options.

But what's most important is that connection, the stack, and that these things connect, as we said, from the top to bottom and bottom to top so that you actually understand how everything fits together.
And I actually love that you're describing it as a mentor model than a framework.
I mean, at the end of the day, you're saying we've got these funny words we call things in product and discipline, but you're just really trying to answer the question, why are we here? Where are we going? What is important right now? How do we know we're successful? Which of those questions do you think is most commonly the hardest or missing in a company?

I think a lot of people struggle with the kind of what's important right now and how do we measure progress? I mean, OKRs are infamously difficult to get done.

But I actually find where you don't get an answer is actually the strategy question, right? How are we going to get there, right? A lot of people have a good sense of what the vision is, right? Most companies have a pretty good sense of their purpose, what they're doing, why they're doing it.

But then you actually start asking, OK, how are we going to get there? How are we going to make that vision come to life? How are we actually going to achieve that? And you can start getting very fuzzy answers, right? If you're lucky, you get something like, oh, we're going to grow 25% this year.

It's not a strategy, right? It's not a choice, but at least it's an answer to the question.

But too often you kind of get a like fuzzy, like, oh, we're going to do a bit of everything for everyone and, you know, be anything for everyone.
Okay, I want to dig into strategy, but let's kind of walk it in the way you stacked it.
Because, I mean, I've always thought strategy is the most important layer because it actually connects everything up to the tactical things that come below.
Many of them, I feel, don't have visions that actually help teams make a decision in that way.
Maybe define a good vision for me and maybe what separates a fuzzy statement from an actual real vision.

So I think a vision does have to be fairly precise, right? It definitely can't be the standard cookie cutter template, right? To be the leading slash best, you know, provider slash supplier, like fill in the blanks kind of ad lib thing that you can do.

I really learned this when we ran Mind the Product, right? So we started Mind the Product as a hobby.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.