People tend to describe good software as simple, as if simplicity were a raw material. It is not. Simplicity is an outcome, and it is usually the expensive one. Complexity is what you get by default: every request granted, every edge case handled, every option exposed. Simplicity is what you get when someone keeps making the harder choice.
Where simplicity actually comes from
Saying no, politely and often
Every feature has a cost beyond its construction. It must be explained, tested, supported and carried forward. A feature that serves a few people but complicates the experience of everyone else is a bad trade, even if it is easy to build.
Understanding the problem more deeply than the request
Requests arrive as solutions: add a button here, a field there. Behind each one is a need. When you understand the need, you can often meet it with less than was asked for, or with something that also quietly solves three other problems.
Choosing sensible defaults
Most people never change a setting. The default is the product, for them. Spending time on defaults is spending time on the actual experience of most users.
Removing things
Software accumulates. Deleting a feature, a screen or a step is uncomfortable and often the best improvement available. A product that can shrink as well as grow is a healthy one.
A practical check
Before adding something, try explaining it in a single plain sentence to someone who has never used the product. If that sentence is hard to write, the idea is not finished yet. If, after shipping, it still needs a paragraph to explain, the design is asking the user to do work that the product should have done for them.
Simple is not minimal for its own sake. It is what respect for the user looks like in practice.