designDoc VS madr

I love spreadsheets! I start with a design doc which usually contains tables in my process: https://github.com/ryanallen/designDoc

Here is the document I use to organize my projects. https://github.com/ryanallen/designDoc

I track my work in some type of design doc that works for whatever org Im helping. Here is a templated version youre free to use and modify - https://github.com/ryanallen/designDoc

Happy to be helpful. I have that process template in github markdown docs here: https://github.com/ryanallen/designDoc

Speaking of process, if it is helpful, here is mine in a template: https://github.com/ryanallen/designDoc

Get the important deliverables and when they want them and plot them out in a table. Timelines are helpful pre and post production. Here is the design doc i use to trace all that stuff throughout a project if its helpful for you: https://github.com/ryanallen/designDoc

As a lean product designer, I agree with OP. If it is helpful for you here is a lean design document process I use for every project that can take an idea from napkin to mvp through pivots on to scale: https://github.com/ryanallen/designDoc

MADR [1] in its reframed "Any Decision Record" form can be a good tool for that. RFDs [2] also appear to capture a similar intent.

[1]: https://adr.github.io/madr/

[2]: https://rfd.shared.oxide.computer/rfd/0001

Markdown Any Decision Records

There is an interesting win-win tool called log4brains, that can turn your markdown into a static website. It's also integrated into MADR template. I haven’t had time to try them yet, but it's in my backlog.

It can be helpful to write down the context of why you made your decision, so that if/when you revisit it later it’s more clear. ADRs are one way to do this: https://adr.github.io/madr/