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 like the why / what / how structure. short & simple

i think the most important part is just to drill as hard as you can into the "why {does this matter / is this worth doing}?"

in your posted example, why are recurring events important? (e.g. hosts and attendees both desire / value longer term relationships.) why is events the right team/product to include this? (e.g. is it complementary to ad hoc events and requested by existing [power] users? relevant to your mission? strategy?) what is painful about the current experience? potentially even who, if anyone, has given you feedback specifically on this (for motivation, grounding, & follow up). the section on channel calendars is interesting but i would move it to the "how" (at least the details of it, could still be worth mentioning in why briefly)

good points, will clarify my thinking in the doc!