Hacker News new | ask | show | jobs
by yegle 403 days ago
Nit:

- Decision doc: It'll be great to have a "Stakeholders" section listing each stake holders' name , and they can add their concerns in that section to start discussion.

- Investigation doc: There should be a "things we tried so far" section listing the actions took to validate each hypothesis, and the outcome of those actions, in timeline order.

- 1:1 meeting note: there's a built-in building block support in Google Docs: https://youtu.be/S1ef5vvMT2k

1 comments

I don't disagree outright, but every time I read something like this it's obvious that it doesnt come from experiential success in the relevant area, just kind of a vibe about how things should be done, without tangible proof. IE the legendary Dropbox analysis on here. Never in my professional career have I cared about anything you listed here
Except for the last one, the other two are from my experiences needing to write those docs.

For decision doc, do you prefer tracking stakeholders comments scattered in multiple places (and also track down the closed comments), or have a single places to read their concerns and address them explicitly as part of the decision making process?

For investigation doc, have you not had the need to hand off to someone else, maybe because you need to go on vacation, or you need to hand off to a colleague in a different time zone? How does the one who took over know what was done for a line "we investigated this hypothesis and it didn't work"? What if the action taken to validate the hypothesis is not comprehensive or the conclusion from the actions is not correct?

Wait have you never had a work experience where people make decision without properly asking around then someone on another team chimes in to say actually you missed X. Or you tried to fix something or an incident but have to read through a slack thread to figure out what's been tried? These seem like common work scenarios at most places