I used to broadly believe that Jobs-types were over-fluffed charismatic magnets myself by hanging out in these places until I started working and found out how useful they were at doing things I couldn't or didn't want to do. I don't think they deserve more praise than the underlying technical folks, but that they deserve equal praise. Sort of like how in a two-parent households, different parents often end up shouldering different responsibilities but that doesn't make one parent with certain responsibilities the true parent.

Engineer was building a calculator app, and got a little tired of the boss constantly requesting changes to the UI. There was no "UI builder" on this system so the engineer had to go back and adjust everything by hand, each time. Back and forth they went. Frustrating.

"In a flash of inspiration," as the story goes, the engineer parameterized all the UI stuff (line widths, etc.) into drop-down menus, so boss could fiddle with it instead of bothering him. The UI came together quickly thereafter.

https://www.macfolklore.org/Calculator_Construction_Set.html

Engineers are great at solving problems given a set of constraints. They are not necessarily all that good at figuring out what constraints ought to be when they are given open-ended, unconstrained tasks. Jobs was great at defining good constraints. You might call this pruning, and if you intended that pejoratively then I think you're underselling the value of this skill.