The idea seems to make it faster to push, but does it reduce work, or does it increase it? I'm thinking end-to-end time, as that's what to measure. By pushing

The idea seems to make it faster to push, but does it reduce work, or does it increase it? I'm thinking end-to-end time, as that's what to measure. By pushing, perhaps 'speed convenient' for the pusher, what incentive is there to put a meaningful message? Is the incentive greater or less than had it been in an email or other tracking tool already in use? Is tagging a page clearer than a screenshot and URL with a giant red box around what a problem is? For tracking, is someone going to have to document a change? If a 'push' went into a tracking tool from the start, this cost would be front-loaded. If from this method of pushing, is this cost offloaded from the pusher rather than removed? If a cost of pushing is reduced, will the number of unnecessary pushes increase? Is 'necessary' to again negotiated through email or other threaded back-and-forth, and will this increase that? Is there a social annotation aspect, like hypthes.is-like comments in the tagging? If so, is there a benefit vs. a cost? I could see this working very well on a 'dev' site for example that's under active change, with 'social' in the comments (and wildly imagining a 'rewind' conversation function like Google Wave back in the day). Does it reduce end-to-end workload, or discover value somehow? That'd be my key barometer.