Are you writing some new functionality in some niche Enterprise Software (think, ERP)? If so, you should also be the one writing the end user documentation (not the README). Because only when you try to explain to your user how to do something, do you realize how dumb you probably made the workflow. If your workflow subsequently makes YOU angry, there's a very good chance it's making your End User 10x more angry. If your workflow makes you feel uncomfortable, there's a very good chance it's making your End User 10x more uncomfortable.

There are people in the world who foolishly believe the saying, "People who can't DO, Teach."

That's dumb.

Teaching someone your ideas is a critical form of self reflection and learning. Writing end user documentation is probably the closest a developer will ever get to, "Teaching," and reflecting.

Write your documentation. Learn your mistakes from the perspective of the end user. Then build a better product.