What do you base your decision on when taking a risky decision in favor of speed or quality?

When making a risky decision in favor of speed or quality, I evaluate several key factors:

• Project goals and business priorities. If a quick market entry is important, sometimes a compromise on quality is justified, but with a clear plan for subsequent improvement.
• Impact on users. If a mistake can lead to serious problems for users, quality is always more important.
• Ability to quickly fix issues. If possible to quickly correct potential errors, taking a risk for speed can be justified.
• Resources and deadlines. Sometimes limited resources dictate a choice in favor of speed.

In Go projects, I strive to write clean, maintainable code, but if the task requires a quick prototype, I can make simplifications with subsequent refactoring.