Adam Jacob

If your customer knows the product as well as you do, understands all the details, maybe they're going to give you like a really delightful solution, but usually they don't. You have to think about how do you build a roadmap that allows you to talk about the general direction that the technology and the platform is going to head while leaving the space to allow the specifics to evolve?

If your customer knows the product as well as you do, understands all the details, maybe they're going to give you like a really delightful solution, but usually they don't. You have to think about how do you build a roadmap that allows you to talk about the general direction that the technology and the platform is going to head while leaving the space to allow the specifics to evolve?

If your customer knows the product as well as you do, understands all the details, maybe they're going to give you like a really delightful solution, but usually they don't. You have to think about how do you build a roadmap that allows you to talk about the general direction that the technology and the platform is going to head while leaving the space to allow the specifics to evolve?

Because on any given day, I know less today than I'll know tomorrow about what would actually make my customers happy, what would actually make the product better, what would actually make those things happen. So you have to give yourself the space to be able to embrace that truth and move through it. I look at a year out, and what you do is think about themes.

Because on any given day, I know less today than I'll know tomorrow about what would actually make my customers happy, what would actually make the product better, what would actually make those things happen. So you have to give yourself the space to be able to embrace that truth and move through it. I look at a year out, and what you do is think about themes.

Because on any given day, I know less today than I'll know tomorrow about what would actually make my customers happy, what would actually make the product better, what would actually make those things happen. So you have to give yourself the space to be able to embrace that truth and move through it. I look at a year out, and what you do is think about themes.

And inside there, you've got stuff that you vaguely believe is important to do, and you have reasons why you believe it. And so you tell those stories to each other and to your people who ask you about the roadmap by saying, look, in System Initiative's case, we need to increase the number of assets that you can use. So we need more coverage of various cloud providers.

And inside there, you've got stuff that you vaguely believe is important to do, and you have reasons why you believe it. And so you tell those stories to each other and to your people who ask you about the roadmap by saying, look, in System Initiative's case, we need to increase the number of assets that you can use. So we need more coverage of various cloud providers.

And inside there, you've got stuff that you vaguely believe is important to do, and you have reasons why you believe it. And so you tell those stories to each other and to your people who ask you about the roadmap by saying, look, in System Initiative's case, we need to increase the number of assets that you can use. So we need more coverage of various cloud providers.

And we also need to do some improvements to the authoring experience. And we need to add some security RBOX stuff to it. And maybe we have to do SOC 2 compliance or whatever.

And we also need to do some improvements to the authoring experience. And we need to add some security RBOX stuff to it. And maybe we have to do SOC 2 compliance or whatever.

And we also need to do some improvements to the authoring experience. And we need to add some security RBOX stuff to it. And maybe we have to do SOC 2 compliance or whatever.

You can take those things and you put them roughly on a map according to time and you talk about them not in terms of the specific features you're going to build, but of the thematic through line that is important to the evolution of the product. That allows you to get feedback on whether those themes resonate, right? Because people can listen to the story of the theme and say, yeah, that's right.

You can take those things and you put them roughly on a map according to time and you talk about them not in terms of the specific features you're going to build, but of the thematic through line that is important to the evolution of the product. That allows you to get feedback on whether those themes resonate, right? Because people can listen to the story of the theme and say, yeah, that's right.

You can take those things and you put them roughly on a map according to time and you talk about them not in terms of the specific features you're going to build, but of the thematic through line that is important to the evolution of the product. That allows you to get feedback on whether those themes resonate, right? Because people can listen to the story of the theme and say, yeah, that's right.

I do care about that. That generalized problem domain is the thing that that that resonates with me as a user or me as a customer. And then it also leaves you the flexibility to discover what's the exact right thing to build, right? And how do you evolve that in the right way? And it allows you to move things around a little bit in space and time, right?

I do care about that. That generalized problem domain is the thing that that that resonates with me as a user or me as a customer. And then it also leaves you the flexibility to discover what's the exact right thing to build, right? And how do you evolve that in the right way? And it allows you to move things around a little bit in space and time, right?

I do care about that. That generalized problem domain is the thing that that that resonates with me as a user or me as a customer. And then it also leaves you the flexibility to discover what's the exact right thing to build, right? And how do you evolve that in the right way? And it allows you to move things around a little bit in space and time, right?

Because as the landscape changes, as your experience of actually writing the code, the truth of the system, plus the the exterior landscape of what's happening in the world, those things will always manipulate your roadmap in some way or another.

Because as the landscape changes, as your experience of actually writing the code, the truth of the system, plus the the exterior landscape of what's happening in the world, those things will always manipulate your roadmap in some way or another.