This is the second of a series of articles. Follow-up articles will be released semiweekly. If you’re curious about the next one, or just want to have a chat, follow me on Twitter. 🙂 In the first article of this series, we took a look at how to set a good goal. Starting out with a clear and well-defined goal is important: It helps us stay on track, makes sure
Between two workshop sessions at last year’s Productized conference, I had a great conversation with a fellow attendee about the new job she had just started. The following is what I wish I would have told her, although I definitely wouldn’t have been able to cram it into a coffee break. I believe it can be used by most product teams, no matter what their resource situation looks like.
We want to make sure we don’t waste resources on changes with no or negative impact, but we oftentimes feel like we lack the data we need in order to make an informed decision. But there are good reasons to move forward with features we’re not entirely certain about.