Tom's answer will solve most of your issues there, because the me part of making that list view means that whomever is looking at that list, it will be filtered to only their items. (if set up correctly)
SharePoint Pages
The extra bells and whistles I was suggesting are simple just that, play around with SharePoint pages, and you'll start to see what you can do with a page, and some 'connected' web parts. It really does lead you by the hand for a lot of it.
The only thing that won't be *as* hand led is the permissions, but once you've figured it out (hopefully you have a managers 365 group which would make it simples) then you can only allow the management team to see the page, and you can put a lot more relevant data on there as well as the list that you wish to customise for them.
MS Forms
Don't think about the Microsoft Forms web part until you have a direct use for it. MS Forms are only good for direct input, they can't reflect information.
However, that's also why they're powerful, because you can really easily ensure very specific choices are made.
I used them to power an automated project hub site. Whereby anyone that was starting a new project would fill in the form on the hub site front page. It would then create a Microsoft Teams team with a "prj-" prefix, which created the O365 (at the time) group, which created everything else needed, too. Just a few additional little special calls on the SharePoint Send an HTTP request action were needed to fully build graceful project sites, which all fed into a main tracker.
This could be done many ways, but the Forms have a much nicer UX than other elements around the 365 stack and more closely align to what people are used to elsewhere in life.
