I don't think you'll get the help you're looking for in a forum.

All we can do is point you in a direction or help you with a specific question.

But to come up with a normalized table schema without a detailed description of the business logic is unlike to be successful. I mentioned a basic example of a data structure in one of my previous posts.

On the other hand I think you're too much focused on the current status. To design a table structure the "big picture" is important. For instance, it doesn't matter that there are "4 transitions and 6 states for each one". All that matters is: there are transitions and states for each one. Transitions can be skipped as well as states within a transition.

The same applies to the process flow. Currently, you don't have the scenario where a product will go into production based on an earlier design. But is there anything written in stone with blood by your management that this will never ever happen? Even if: why not to design it in a way where you can say "No problem, already included in the database design?"

I think a good Business Analyst would be able to help you with your table design much more efficiently than a forum can do.