This is why I encouraged my team to go on periodic walks throughout the day. I've always found that thinking can be easier when you move your body a little bit and getting out into the sunshine can improve your mood and cognitive abilities. If you can type at least 60wpm, as any professional dev should be able to do, the sitting at your desk part is just data entry and only needs to be done for a fraction of your day.
Getting organizational buy in, though, was a lot harder. At review time, when we were measuring employees against each other (don't get me started on the stupidity of stack ranking, but that was the system we had to follow), other managers would try to use it against my team saying that they're always away from they're desks and trying to compare them against their own team's long hours and heroic firefighting of production issues. It took me about 18 months of convincing before I got our directors to realize that my team was producing just as much functionality, with much more complexity, and doing it while seeing a fraction of the production issues that other teams saw. I had to get testimonials from our support team along the lines of, "we don't answer many questions about their stuff, it just works."
By the time I'd left, I'd just started to get through that busy isn't a virtue and hard work is only a good thing if it can't be avoided. Time spent reflecting is crucial to doing the least work necessary. Skipping that time will only create the appearance of productivity.