The discussion is about giving admins “Level_x” goggles to temporarily view the site as a user with lower trust levels. ganncamp suggests this feature to easily switch between admin and non-privileged user views without having to log out and back in. Canapin notes that there aren’t many visible differences between trust levels, but acknowledges the usefulness of such a feature for testing purposes.
ganncamp emphasizes the importance of being able to see what lower-level users can see and do before instructing them on features they may not have access to. Others suggest alternative solutions, such as creating a test user IAmGav and JammyDodger, who uses a separate browser for testing.
sam mentions that this feature has been discussed before, particularly for theme component designers who may accidentally rely on staff features. The feature would allow admins to “impersonate down” to lower trust levels, making it easier to test and design components.
There have been a few times recently when I needed to see what something looked like from the perspective of a non-privileged user. What I’ve done was find an example user & “impersonate” them.
When I’m done, I have to log out & back in.
It would be nice if I could stay “me” and just temporarily downgrade what I’m seeing.
But there aren’t many “visible” differences between trust level users. You won’t “see” much through your goggles unless you have heavily customized your trust level. These are mostly usage restrictions.
As a trust level 3, you’ll be able to edit title/categories from others’ topics, stuff like this, but that doesn’t seem that interesting to “see” until you know, and there is little to know. You could have a secondary account and change its trust level before impersonating it, it’s a matter of a few seconds. This is what I do.
Have you some valuable examples of what you’d be interested in seeing through these “goggles”? 
Yes, exactly. Shortly after I gained global admin, I completely forgot which parts were and were not visible to me prior to gaining the privs. I’d like to see what lower-level users can see/do before I tell them to use features they don’t have access to.
create a test user and use it for testing.
problem solved
I have a test user logged in with a different browser (ie. me in Chrome, and test user in Firefox) so I can swop between them easily. I also sometimes use an incognito/private window, but that’s only good for anon things, and not logged in things.
I think something similar was requested recently in this topic:
"Regular mode" for admins and moderators (e.g. something like "sudo")
We discussed this feature a bit here:
We do agree that there is a common desire to be able to “impersonate down” to TL1 etc. It is something that cal help theme component designers quite a lot cause sometimes you lean on staff features by mistake and then get surprised when the component is deployed to production.