Celebrate Milestones and Wins: Treat stability improvements like achievements. Celebrate each release that reduces crash rates, improves performance, or enhances app reliability. Recognition for meeting these milestones can build a strong sense of accomplishment.

The way I define quality is.. 1. What you build must never crash, 2. What you build must work as designed, 3. What you build must do what it say will do for the customer, and finally 4. What you build should make the customer renew & recommend it to others. So right from the beginning, making it clear that stability, resiliency is table stakes is important. If you do that in an ongoing manner, you will rarely have to stop building new cool stuff and focus "only" on stability.

- Give them some important tasks to increase their efforts and make them feel important - Sometimes make them feel better by saying thank you and having a small celebration - Support them by allowing them to bring their own ideas and abilities to work - Show your trust to them in action

I think that's a bit challenging yet with *constructive and transparent conversation* with team, this can be resloved. I would like to share What has been working for me for various teams handling variety of product/projects. - Start with Why? (As Simon Sinek says) Communicate with team and connect to share why this is the need of the hour from your perspective as a leader. - Share the real world example of other product or project that did this in past. Example: what zoom did in Covid times. - Share the data how is the usage of your product - 80-20 rule. Most of the time only 20% of features are used 80% of time. - Acknowledge the journey and accomplishments. Then ask them to be empathetic and what will they decide on priority & why?

Stability is the foundation of building something bigger and greater. Stability should be celebrated as a mark of achievement for the team. When things are stable team gets space to think outside the box and come up with new ideas. Time is invested into new things. Work personal life gets better. Make the goals clear by setting proper milestones. If in this month there are reported X crashes or ANR. In the next month it should be X-Y. Ones who are mostly working on stability feel the pressure of working on the same thing over a long time and don't feel motivated and their contributions are not clebrated as much as a feature/product that is live. This should not be the case. All achievements should be celebrated.