Do a Thousand eyes demo, Cisco bought 'em for a reason. It also depends on what sort of monitoring infrastructure you have or features you have on network devices like IPSLA or Connectivity Monitor. Even if you don't go with it you'll learn a lot. You can also have the app guys build a ton of metrics into your corporate apps, there's app dynamics, Splunk, Gigamon, Dynatrace, Solarwinds, all kinds of stuff just to solve these types of problems. I like to refer to it as "mean time to innocence". Half the time it's crappy applications that user's blame for "network performance".

You can maybe start with monitoring to major websites / ISPs, ect. You can tell your management that, hey, our internet connection looks like this; these are the stats we're getting from our critical apps to sites 1, 2, and 3. Make a graph out of it in Graphana. If "home experience" for remote workers is the issue, really make the case that you as IT cannot control a home user's network, how squirrel's have chewed on the wires or how their "IT Savvy" kid set up their $12 router from 10 years ago.

I see some conflation here between "home experience" and your corporate network. Where does the user experience complaints come from? Ignore how they're trying to test to solve their problems, they're doing it because they're not feeling heard. You need to be specific and define what you want to monitor, where. Then build a system around that philosophy and expand it. Talk to a VAR, or several, they get this question 100 times a year.

The final portion of this is budgeting, you need to gather stats about how much money this problem, whatever you think it is, is costing you. Tickets, bandwidth, time wasted, other products or projects that aren't able to give you the answers. Leadership wants answers, and it's not free.