If engineers aren't working closely with the end-users who do each piece of work their systems directly support most frequently on a regular basis in the course of development, doing deliveries once (whether that's one delivery or one shift) a month won't make up for that fundamental process defect, and if they are, then it won't add anything meaningful for what that process already provides.

These days it's a lucky accident when the engineers and the end users are on the same continent and maybe speak the same language. The business will certainly optimize for lowest cost until it becomes so bad that it's impossible to overlook.

Managing by walking around is still amazingly more successful than managing by arbitrary metrics, but it's still rare.

> These days it's a lucky accident when the engineers and the end users are on the same continent and maybe speak the same language

Seems to me that dealing with that is even more of a problem with requiring engineers to do one particular class of the work one day a month as it is for having the engineers engage with those during the work as part of product design and development, so I’m not sure what relevance it has to the present discussion.

That sounds like every company everywhere.

Engineers are usually far removed