> requiring more effort from the people consuming the content
This hasn't been my experience; if anything, quite the opposite, in that it's enabled my team to contribute much more actively to design. The effort of providing actionable feedback is admittedly slightly higher, but that's not a bad thing; needing to (and having time to!) write up feedback seems to yield more actionable results than doing it verbally in the moment, and for things that do really need talking through we have several sync touchpoints during the week with our embedded designer.
Of course, in contexts where no such touchpoints exist or where design and eng generally don't have a close relationship, I could see Loom being difficult - but I'm not sure I'd blame that first on the tool; if Design and Eng communicate only by throwing things over a transom at one another, I think the tool much more likely exposes problems you already had and didn't know about.
This hasn't been my experience; if anything, quite the opposite, in that it's enabled my team to contribute much more actively to design. The effort of providing actionable feedback is admittedly slightly higher, but that's not a bad thing; needing to (and having time to!) write up feedback seems to yield more actionable results than doing it verbally in the moment, and for things that do really need talking through we have several sync touchpoints during the week with our embedded designer.
Of course, in contexts where no such touchpoints exist or where design and eng generally don't have a close relationship, I could see Loom being difficult - but I'm not sure I'd blame that first on the tool; if Design and Eng communicate only by throwing things over a transom at one another, I think the tool much more likely exposes problems you already had and didn't know about.