We are developing a complex platform with heavy functionality, and I am having a dilemma, concerning whether or not to add a button for the same functionality one-step earlier in the User Flow.
As seen on the wireframe image on the link below, I have shared an example of 2 screens, a Multiple Item View and the Inner View of the item. When the User clicks on an item in the Multiple Item View Screen, he gets transferred to the corresponding Inner View, where he can get access to multiple actions, through Buttons. (e.g. Download, Preview etc.)
Now the question is, should I provide a "shortcut" for the same functionality, 1 step/layer earlier in the process (case 2)? This could be done by including a smaller version of the same button, in the Multiple Item View. That way, the User can get to access the same functionality with one less click.
I am of the belief that providing strict structures (Only 1 path for a specific actions) generally works better, especially for complex platforms, and that giving the user multiple flows/action paths results in confusion most of the time. However, some developers in the team disagree, and insist on me putting some button(s) one step earlier, in order for the user to avoid the extra click(s).
What is your opinion on that matter? Is there a practise that works better most of the time?