
So, in addition to my team reviewing the design of the functions coming to Sber App and developing a design system and UX principles that ensured consistency in scenarios, I started forming an image of the future product through numerous meetings with various departments to create product vision presentations.
Ultimately, it allowed us to align the intentions of 200+ product teams, IT-leads and C-levels by designing high-level visons with an assembly point for 2-3 years for business and IT.
Then, the key product visions were presented and accepted by the First Deputy or Board's Chairman and became a north star to which we are all moving. After that, deprioritizing some crucial points in terms of UX became much harder and each subordinate business goal inherited the key ideas from the Vision for years.

After making a vision to launch a new product in Sber established as a standard, adjusting operational work became much more manageable: at the launch of new products, in making architectural decisions, at the development level, and, of course, in the design review process.
That's what I call design-driven development paradigm and what I was proud to bring to life in Sber.
Earlier, like in other banks, our main screen was just a list of the client's products. But there was an endless sheet of numerous opportunities, not answering real clients needs.