• Thoughts

When there is no right answer, product philosophy guides our choices

What should be upheld when schedules and quality, or rules and exceptions, clash? The role of product philosophy in making collective choices consistent.

Even when our choices differ, the values we seek to uphold together give us direction.

I believe one of the most difficult questions in a self-introduction letter is, "How did you resolve conflicts with others?" Until I joined the company, I had rarely experienced significant conflicts with people.


If opinions differed, I conceded to some extent, choosing to maintain smooth relationships even if it meant taking a slight loss. For most relationships, that was enough.


However, the company was a bit different. In a company, roles, schedules, and responsibilities are directly intertwined. A task I once helped with because the other person seemed busy naturally became accepted as my own role at some point.


In order to gain concessions at truly critical moments, I would give in on other things; but when concessions were repeated, they were eventually taken for granted, and I found myself in situations where I had to keep conceding.


I worried a lot about how to resolve this. How should I speak to persuade the other person? How should I act so that no one's feelings get hurt?


That is why I became interested in psychology and listened to people's inner thoughts while belonging to various groups. Through several trials and errors, I realized there was something I needed to think about before asking, "How should I speak to persuade the other person?"

Conflict begins from different standards

Conflict often occurs not because someone did something wrong, but because what each person considers important is different. For someone who values the schedule, finishing quickly is the best choice, while for someone who values quality, making it properly even if it takes time is the best choice.


From each person's perspective, neither was wrong. Therefore, the problem is not easily solved by persuading someone to accept one side's opinion.


One step above the individual standards, we must first agree on the value we wish to pursue together. I believe this is a crucial standard for viewing conflict.


Ultimately, it is because we are moving forward together for a single goal and a single product.

When there is no right answer, a higher standard is needed

Then the question naturally follows: What kind of value do we want our product to have? I believe the answer to this question is the product philosophy.


In books dealing with software architecture or databases, various quality attributes such as performance, stability, scalability, and maintainability appear repeatedly. These standards are important because it is impossible to maximize everything simultaneously.


Choices change depending on what is viewed as more important, and a standard is needed to make those choices consistent.


That said, philosophy is not something grandiose. It can be expressed simply, such as "user-centric," "simplicity," "safety," or "visibility." While the power of the phrasing is important, what actually matters is whether that value can be applied at the moment of choice. What will be chosen when the schedule and quality clash?


Which one will be used when new technology clashes with proven technology? When you can have everything, philosophy is not needed.


Philosophy is needed to decide what to protect at the moment you must give something up. Value is declared, and philosophy is chosen. It is easy to say, "We value quality."

Value is declared, and philosophy is revealed through choice

However, whether one can give something up for the sake of quality even when the schedule is tight is what reveals the actual philosophy.


Ultimately, a product's philosophy is not a sentence written in an introductory document, but is revealed through the choices we repeatedly make. Therefore, if the decision-maker's choices do not embody the philosophy, it is difficult for those working together to feel that philosophy within the product.

Why philosophy is needed more than rules

To create a good product, we create numerous rules such as coding guidelines, development procedures, review methods, and testing standards.


But rules alone cannot explain every situation. If the answer to the question "Why must we follow this?" is simply "Because it's the rule," people may follow the rule, but it is difficult for them to carry forward the intention.


Conversely, if one understands what value the rule was created to protect, they can make a new judgment based on the same philosophy even when a problem arises that is not covered by the rules.

Rules are the result of past deliberations, and philosophy is the standard for judging problems we will face in the future.

Therefore, I believe sharing the reason why a rule was created is more important than the number of rules. People who share a philosophy can make judgments in a similar direction even without rules for every situation. In that way, even if many people work for a long time, a single direction can be maintained.


Of course, having a standard does not mean always making the right choice. There will be times when we realize the value we thought was important was wrong and we must change the standard itself. However, if there is a standard, we can at least look back.


We can discuss based on what standard we made this choice, what result that choice produced, and whether we should maintain that standard moving forward. Conversely, without a standard, it is difficult to know even what went wrong when the result is poor.


At first, I wanted to find a way to get along with people without conflict. But now, I believe that eliminating conflict itself is not the answer.


If there are people with different thoughts, conflict occurs naturally. The important thing is not deciding who will concede, but knowing what we are working together for.


If there is a common standard, individual assertions can be let go little by little. This is because we can talk about "Which choice is closer to our standard?" rather than "Is my thought correct?"

Traces of choice remain in a good product

Making a good product does not only mean putting in many good features. It means constantly contemplating what we consider important and upholding that value at every single moment of choice.

And when looking back at the product over time, a single consistent value naturally becomes visible through the numerous choices we made. That is how value is embedded in a product.

Comments 0

Share your thoughts on this article.

Comment inquiries

Loading comments…

A Trip to Suncheon and Yeosu, Day 3

The last day, ending with some studying and a run.

Seungmin Yang

A Trip to Suncheon and Yeosu, Day 2

The second day of the trip, from a clear morning by the sea to sunset and dusk on Baekyado Island.

Seungmin Yang

A Trip to Suncheon and Yeosu

A trip to Suncheon and Yeosu.

SkyDive Team
See all