You're right that suggested solution might not be the best, but the problem is trickier than you'd think. For example, I know writers who like isolation. Not ju

You're right that suggested solution might not be the best, but the problem is trickier than you'd think. For example, I know writers who like isolation. Not just being alone. Going to a remote place where they have no connectivity to the outside world whatsoever. So while software that lives and connects to the internet gives a user "a lot of devices in a lot of places" to do their work, it does not give you the "ability to work anywhere." Now you have to make sure you solve the problem of - having the software and the user's work in progress (WIP) on whatever device(s) they take out of internet connectivity, and also making sure the updated WIPs get pushed back to the internet as soon as they reconnect. We could try to simplify the problem with an assumption, like only run the software one device (instead of only one USB stick), but you've created new limitations to how they work. Maybe they get by with their mini laptop in the cabin, but they prefer a different computer at home. The USB works better with the multiple locations and, in theory, devices, until you get to the multiple OS (and releases) problem discussed in the parent comment. So while it's not the job of the product owner to use the solution presented, it is their job to think about why that solution was suggested, and run their own proposed solutions through those reasons.