If documentation is the root cause of that then you should fix that by creating enough documentation to allow your software to continue to work

Or create a better UI that doesn’t require so much documentation.

In long term development, sensible and updated documentation is far more important than the software working constantly. You will have downtimes. You will have times before the PoC is ready.

But if your documentation sucks or is inexistent, you cannot fix any problems that arise and will commit a ton of debt the moment people change and knowledge leaves the company.

1. Hack together a proof of concept
2. Works well enough that management slaps a “done” sticker on it
3. Pile of hacks becomes load bearing
4. One or two dependencies change, the whole thing falls over
5. Set evenings and weekends on fire to fix it
6. Management brags about moving fast and breaking things, engineers quit and become cabbage farmers and woodworkers
7. New graduates are hired, GOTO 1