# Fibery Product Workspace **URL:** \ **Category:** Fibery Showcase\ **Created:** [November 2, 2020, 12:34pm UTC](https://community.fibery.io/t/fibery-product-workspace/1120 "2020-11-02T12:34:49Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [November 9, 2020, 5:18am UTC](https://community.fibery.io/t/fibery-product-workspace/1120/4 "2020-11-09T05:18:18Z")
This is interesting, I think the Product Team usecase is a great one and I feel like you guys will get great uptake on it, Fibery is very well suited for these types of teams - I am one of them! I wanted to ask about one aspect of this: **You guys have many relations to both parent and children, is there a reason you didn’t use LookUps?** For example, “Story” has a relation to Product Area, Product, and Feature. I would have thought it would be enough to have the relation to Feature, and use lookups to see up the hierarchy through Product and Product Area. All these extra relations means the Entity view gets clogged with additional fields, which are at a premium until we get [Polymorphic](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-entire-app-from-which-to-choose-and-not-just-type/425). Thanks in advance for any response you guys can provide! --- _[View the full topic](https://community.fibery.io/t/fibery-product-workspace/1120)._