Improve-this-product and design-for-this-user questions, and structuring an answer around a real user problem.
3 questions in Product Management.
Separate what the design costs users from what you personally dislike, then reconstruct the constraint that produced it: a business model, an organisational boundary, a regulatory rule or a migration nobody can finish. Any change you propose has to survive that constraint or it is not a proposal.
It is a structure test, not a creativity test: state the product's goal and how it earns money, name one segment and one unmet need, generate several options before choosing, then commit to a metric and the risk that would prove you wrong.
Argue from the cost the feature imposes on everyone who does not use it — surface area, decision load, engineering drag — then quantify who depends on it, find where their need lands afterwards, and stage the removal so you learn before you are committed.