The goal of everyone learning to code is a noble one, but it's just not a good one for the vast majority of companies.
Various companies have tried releasing tools which allow the "normal office person" to create their own solutions - which is why we have stuff like Visual Basic, macros in Office, etc etc. And those solutions are the bane of any software developer's life.
They are unmaintainable, missing the basics of modern coding principles, and lead to problems further down the line - pretty much every company has that one spreadsheet that performs some core, mystical function that no one wants to touch...
Software development is more than coding - to test properly and consistently, the developer should be using unit testing, which means the developer should be splitting their code up using inversion of control, which means the developer needs to know isolation and other principles. So it's down the rabbit hole you go.
And then comes the supporting system that a good software developer needs to have - source control, analysis tools, coding standards. Further down the rabbit hole.
No, you don't want everyone coding.
But the people you are talking about can still be helpful, they can still take part and you can still access that knowledge.
Get them to learn a specification language - get them to define their needs and wants in something that looks like code, but which can be directly translated to code, and something which can be used to test the produced code.
I use something called SpecFlow for this, and it can be used successfully by most non-developers out there, because its syntax is this:
Scenario: Add two numbers
Given I have entered 50 into the calculator
And I have also entered 70 into the calculator
When I press add
Then the result should be 120 on the screen
Getting end users in a business using something like SpecFlow means you can directly take the specification for a new feature or application and build software from it. It means you can then directly see if the end product matches the specification, because you also derive your tests from the specification.
Get everyone writing specifications - that's what they want to do anyway, they just normally do it in a meeting or via email or a Word document. If you get them using a formal specification language, they become much closer to the action, they get to define what they want in more exact terms, and they get much better feed back from the developers following the specification.