> I wonder if the other end is a person who'd rather have stacks of physical objects as their task list: read what the issue is, write down how to fix it, hand it over to someone who'll run and fix the problem, and give the replacement object and the paper to a delivery driver, job done.
Happens, yes. Part of my job is digitizing analog processes, mainly for technicians in the field. And often you have the problem that the back-office really wants to get back the information what they need to reorder, what they cause bill the customer and so on, as fast as possible. But technicians don't want to bother with having to type into their smartphones or tablets while they are in the field. They just want to jot it down onto a paper, load the whole stack of at the end of the week and let the back-office do the rest.
One of the many sources of 'friction' if you make something digital that was done on paper before that, not made easier by the fact that the offices now want the information even faster, cause "you have the machine with you. You should do it the moment you've done the work."
Happens, yes. Part of my job is digitizing analog processes, mainly for technicians in the field. And often you have the problem that the back-office really wants to get back the information what they need to reorder, what they cause bill the customer and so on, as fast as possible. But technicians don't want to bother with having to type into their smartphones or tablets while they are in the field. They just want to jot it down onto a paper, load the whole stack of at the end of the week and let the back-office do the rest.
One of the many sources of 'friction' if you make something digital that was done on paper before that, not made easier by the fact that the offices now want the information even faster, cause "you have the machine with you. You should do it the moment you've done the work."