Standard Solution Decision

☕ Problem

In complex software projects, solution decisions often suffer from a few recurring problems:

1. Decisions are sometimes driven by the loudest voice or the most senior person in the room, rather than by what is best for the company. As a result, stronger alternatives may never get a fair chance.
2. Approval may depend too heavily on individual authority instead of clear rules and evaluation criteria. This makes outcomes inconsistent and overly dependent on personal capability, which is difficult to assess objectively.
3. When solutions are controlled by individuals rather than by a council or a defined process, the team cannot fully benefit from collective wisdom.

---

🎯 Actions

1. Define which problems require council review.
   Cross-functional epics involving frontend, backend, and product management should be reviewed by the council.

2. Clarify the decision-making endpoint.
   1) Anyone can propose a solution. All proposed solutions should be compared and reviewed.
   2) The solution that receives the strongest support through voting becomes the approved solution.

3. Set approval standards for solutions.
   1) A solution should be simple, protect customer interests, and meet the company’s security requirements.
   2) A solution should follow industry-standard best practices.
   3) At least two-thirds of council members must approve it, and all approval and rejection records should be documented.