You're facing user feedback that demands major app design changes. How do you tackle this challenge head-on?

To approach the redesign, also consider if the redesign aligns with your company's vision and its business goals. The goal is to find a balance. The redesign should have a positive impact on the users as well as the business, so advocating for a solution that will work well for both sides (user and the business) is the balance!

Analyze user feedback to identify reasons for redesigning the application's architecture. Ensure the new architecture is scalable and open for future enhancements. Evaluate if user confusion is due to the UI, and determine if changes are needed for the frontend, backend, or both. If backend modifications are necessary, design the architecture to accommodate future feature enhancements.

When redesigning the application, it is important to prioritize tasks based on their urgency and impact. Utilize frameworks such as the Kano Model, Weighted Scoring, MoSCoW , Eisenhower Matrix, or Cost of Delay (CoD) to determine which tasks require immediate implementation and which can be deferred. Ensure that the prioritization process considers the impact of the redesign on customer satisfaction.

We can utilize agile methodology for the prioritization process, considering the impact of the redesign on customer satisfaction. Sprint planning and execution should focus on tasks that require immediate implementation while deferring less urgent tasks. Iterative design changes will keep the user base up-to-date and maintain their trust in the application.

To ensure users are comfortable with design changes, we should keep them informed through emails, notifications, and video blog articles. Before implementing design changes, engage with the user base to maintain their trust and keep them informed about upcoming updates.

It is a good idea to roll out updates in phases to minimize distruption. To monitor the impact of each change and make adjustments if necessary, the BML (Build, Measure, Learn) approach can be used. Build: Features being rolled out Measure: You want to ask yourself "What do you want to measure" and "How do you want to measure it". Learn: You may identify concerns that you never considered before. Also you can validate the concerns that you are already aware of, when the updates are released.

I'd like to highlight that in scenarios where user feedback necessitates major app design changes, the key factor is what has already been done or not done, rather than future plans. Especially if the app is new and still evolving, but not exclusively - it is the architect’s job to take preventive measures: * Ensure the architecture is flexible, allowing for the addition of alternative features or switching between them * Avoid over-engineering and not waste resources on features until users confirm they need them

When considering a redesign of the application, we should analyze user feedback to identify necessary changes and ensure the new architecture is scalable and open to future enhancements. Prioritize tasks using frameworks such as the Kano Model, Weighted Scoring, Eisenhower Matrix, or Cost of Delay (CoD) to focus on immediate needs and defer less urgent tasks. Utilize agile methodology to plan and execute sprints based on these priorities, considering the impact on customer satisfaction. To keep users comfortable and engaged with the design changes, regularly update them via emails, notifications, and video blog articles, ensuring they are informed and maintaining their trust in the application.