Product

Anyone want to compare notes on how they write product specs? Feel free to reply with critiques / feedback, or share one of yours.

As a solo dev I could yolo features without writing specs, but I find that the deliverable makes me more methodical and thoughtful.

So I'm curious how / if others write theirs.

Anyone want to compare notes on how they write product specs? Feel free to reply with critiques / feedback, or share one of yours.

As a solo dev I could yolo features without writing specs, but I find that the deliverable makes me more methodical and thoughtful.

So I'm curious how / if others write theirs.

https://eventsxyz.notion.site/Recurring-Events-Public-6215091ea67b44508c691af87fc1faa6?pvs=4

design @splits | /latenightcrew /event-pass /feud

i take a really similar approach to this doc but break it down a bit more into sections. for me the goal of the doc is three parts:

1. understand all assumptions
without this communication really suffers and half the time sharing the doc is eaten up by doing this anyway

2. align on the (ideal) end goal
much easier to talk about how to get to a shared goal than discuss many approaches to a near term goal. also for solo work it really helps long term focus

3. figure out how to get there
explore the different spaces and write down all the approaches so I can remember why later and also discover assumptions

so most docs end up taking the form like
1. problem
2. goal
3. current state
4. solution
5. post-solution
6. alternatives

doing stuff onchain | bc skier | surfer | baker

this is great thank you! a lot of that is in my head and just didn't make it out onto the page, but can do next time