given this notional use case (and the relative inexperience of the implied user), I think its even more important to (as Gunnar mentioned) contextualize this advice as to whom its for, and how they should use it.
doing that properly would take more than i have for this at the moment, but i’d appreciate epistemic tagging regarding things like; this only could work at a new/small scale (for reasons including because the cost of keeping everyone 100% context scales with org size and because benefits don’t) that strategy has to fit the employees you have, and this sort of strategy constrains the type of person you can hire to those who would fit it (which is a cost to be considered, not a fatal flaw).
given this notional use case (and the relative inexperience of the implied user), I think its even more important to (as Gunnar mentioned) contextualize this advice as to whom its for, and how they should use it.
doing that properly would take more than i have for this at the moment, but i’d appreciate epistemic tagging regarding things like;
this only could work at a new/small scale (for reasons including because the cost of keeping everyone 100% context scales with org size and because benefits don’t)
that strategy has to fit the employees you have, and this sort of strategy constrains the type of person you can hire to those who would fit it (which is a cost to be considered, not a fatal flaw).