Getting lost in the weeds

I'm in the process of creating a new product. With that always comes a certain level of excitement, so it's very easy to just start doing stuff. After all, sitting around and planning for months is a bad idea, since speed is key.

However, jumping right into product development without first planning in advance misses one key benefit: Writing down assumptions.

You don't have to go full Scrum on Day One. However, by writing down and planning individual features, you have the opportunity to write down all your assumptions regarding this feature. How do you expect people will use it? What's important to include in a first iteration and what can wait?

If you're not sure about one of your assumptions, you can always circle back to your initial customer base and ask for feedback.

But this requires writing down your assumptions in the first place.

Yours,
Søren