It definitely is true that a design which could easily be created by hand is harder to create on a computer. The things where computers shine are actually managimg the complexity of a large and complicated systems. What I think the article leaves unspoken (but implied) is the "curse of tools", if you give a person tools he is likely to use them, even if they might not be applicable. Meaning that someone might decide…
In general it is almost universally true of software nowadays. (Because change/progress leapfrogged any kind of teleological end-to-end design OR it's simply unmaintained, for example see any US government IT system. Or the ubiquitous extremely fragile corporate synthetic snowflake software that only runs on Windows XP SP1 + that 3 particular patches with that exact vc6.dll copied over from an old CD.)
A good quality information processing tool is designed for the process that it's meant to augment, ideally considering the original problem, and ultimately improving the process itself.
(Just digitizing a form likely leads to worse outcomes. Because those forms were designed for pen and paper. Screens and keyboard navigation requires different flows.
And the usual process is even worse, which consist of reinventing the wheel without context, as in speedrunning through all the problems of corporate politics and procurement, delivering some half-assed milestone-driven monstrosity, and forcing it on employees.
Of course, due to the aforementioned universal internal incompetence-fest and quarter-driven development budgets are bad, required time and effort is underestimated, learning curves are ignored, software gets set in stone too soon, and thus efficiency remains well below the expected, planned, possible, and hoped for.)