Let me explain the problem briefly: I'm working on user flows for a customer support system. The system is structured to have several (horizontal) modules, namely messaging, contracts policies, invoicing, etc. (Vertically) these modules can be conditioned based on the contract type. For example, for insurance contracts there'll be slight difference in invoicing module with the additions of "claims"; or messages module may show only messages related to specific contract instead of all messages.
Now, I want to compare two approaches for user flows: a) the "contextual" one where users first select the contract/contract type and then interact with modules and b) the "all-in-one-bucket" where users start their flow, and along the way choose "specialization", i.e. select contract/contract type, and based on that UI forms get updated (for example, choosing insurance contract will show a new section with "claims").
I am wondering whether folks know about good examples of these two approaches in existing products and what terminology one would use to describe them?
(for the terminology, I'm looking at borrowing the Strategy pattern from software design.)