There's rarely any progression outside of awkardly forced crafting processes and any sense of flow is thrown out when you have three ways to pipe items around on top of vanilla hoppers and water channels.
Worth noting is that strong tiering and enforced progression is
stupidly difficult and often unpopular to maintain. To do so, it is absolutely essential that you maintain a
total lock on what can and cannot produce your critical gating materials/power/et cetera, and on the recipes and/or other parameters of the mod.
The former is extremely difficult to pull off because it essentially means closing the mod inward; you cannot have tiering if you can go, for example, from endgame RailCraft straight to your mod, or if your tungsten ingots are ore-dictionary interchangeable with those which can simply be mined out of the ground from other mods. Even if you attempt to try this, like I do, it makes a lot of players unhappy or at least confused, and can easily be destroyed by unwanted interactions from other mods. For example, if magic bees gained the ability to produce jet fuel, or magic crops gained a bedrock dust crop, the entirety of RotaryCraft would become so horrifically unbalanced that I myself would refuse to use it on a server. You can of course always try to solve things diplomatically like I try to do, asking other developers to not interfere with your mod's progression, but that is no guarantee that they will do so; about half of the ones I talk to either simply do not care or feel it is the height of self-importance to ask for things like "no uncapped EU-RoC converters". And if another mod does crap all over your progression and the developer makes it clear that they will make no efforts to change, what can you do? As soon as you start interfering with other mods, even something as minor as removing a recipe (like, for example, 8 of these hypothetical bedrock essence to 1 bedrock dust), you will be vilified, and your mod's usage in packs will suffer severely. If their interference is less easily "broken", you are essentially SOL; all you can do is either discard all concern with what people think of you and reflect/ASM the hell out of someone else's mod or sit back and watch as you get branded as the most OP mod ever made. Either way is a losing game and will see your user base plummet as users flee and most packs pull your mod.
The latter...oh god, where do I start?
Locking down your recipes and other progression is a
surefire way to make yourself one of the most divisive and polarizing developers in the entire community. Those well-acquainted with your mod will probably not mind, but pack makers and server owners will take it as a direct (and often personal) assault on their "domain of control", something they will make extremely (and often loudly) clear to you and likely everyone they think listens to them. Like above, you will rapidly gain a reputation as a developer who thinks they are above the rest of the community and who is so engrossed with their own self-interest that they are to be avoided at all costs, and that your mod forces everything else to be balanced around it. You will be
flooded with indignant, often livid, server owners and pack developers, 95% of whom have never used your mod and are entirely unaware of the progression, demanding that you allow them to "replace bedrock with compressed cobble, 'cause bedrock's too easy" or "disable [crucial techtree] machine X, it's OP". If you refuse, they hate you. If you concede, they screw up their server's economy or pack's balance....and hate you.
On top of all that, a lot of other mod developers, only familiar with their own mod's traditional resource-gating systems, will also see your refusal to add configs to modify core behavior/disable items as a case study in what
not to do, and many will make that abundantly clear to you.
Long story short, you
can make a mod with a rigid progression system, and it
can work out very well, but very few developers can or care to put up with the mountains of feces they will have slung at them, day in and day out, as a result.