Your team is discussing a new feature and there is pressure to start building quickly. Before committing engineering time, you want to be clear on the user problem, the expected outcome, and why this feature matters.
How do you think about the why behind a feature before your team starts building it?
Can you identify the underlying user need before discussing solutions?Can you frame the feature using a Job to Be Done?Can you decide whether the idea is worth prioritizing?Can you define success criteria before engineering starts?