Speaker argues product teams should design around the user's chronological journey rather than building isolated features. Using Lattice as an example, the speaker outlines a typical employee lifecycle (onboarding → goal setup → one-on-ones with manager → quarterly cycle → feedback) and says mapping these steps guides a more holistic roadmap and better customer solutions.
The right way to do it isn't just building sort of random products that you think your buyer might want to build, but instead thinking about the user journey. And what does this sort of human who's using your products, what else exists chronologically in their. In their day, what else do they need and sort of take them through a journey. So, you know, as an example for Lattice, it might be you onboard at the company. You need to get set up with your goals. You need to have one on one with your manager. You going to go through a quarter, you're going to get feedback, you're going to share back how you're feeling, and you sort of think in those terms. And this applies to basically every software category. And that can kind of guide your roadmap and lead to a much more holistic solution for customers.
