When you launch a new feature or module in your product, consider how the user will discover that feature and interact with it.

Your new feature must create an emotional response of "want to use it" in the user's mind.

During the launch of the product, you decide on a simple pricing model for your product. When your product evolves, is your pricing changing equally? Is your pricing competitive and straightforward for the users as it was initially?

Re-work the pricing strategy of your product so that your existing customers do not feel cheated for what they have paid, and new users can see the value.

You need to continuously get feedback from existing customers and improve your product. It is equally important to talk to people who were your customers in the past and understand what turned them away.

Although you and your team's thought process evolves and becomes mature over time, your product needs to use the same personality and expression to communicate with each user.

You need to revisit those old modules from time to time and make changes for consistency.

Often improvements that will have a less overall impact get prioritized because of a specific and pressing need of your customer success/support team.

Make sure that the improvements are made based on the overall impact.

Teams often spend a lot of time discussing outlier user behavior during their team meetings. Although these conversations are exciting and test the limits, they don't serve the major cohort of your users.
You need to know who the 80% of your users are and prioritize solutions that will serve them.