@mdubakov - thank you for sharing your thoughts on this approach and for validating some of my assumptions. Problem #1 you pointed out may necessitate we create team-specific entities for those scenarios. I think what we’ll probably move forward with is the current implementation as a "lower common denominator’ PM space, where we keep this entity as agnostic as possible for managing cross-team collaboration/projects. I’m envisioning the potential for specific teams to have their own “Initiative” or “Technical Project” entities which we can relate to agnostic PM entity for transparency.
Excited to hear of the improvements to come in the future. This would provide what seems like an infinite level of access controls.
Absolutely. I’m continuously amazed by Smart Folders, discovering many creative ways to utilize this feature, and hope to recognize some serious benefits with my team. Projects/Tasks folders filtered by Team as and Status, Team folders containing team members, Customer folders containing contacts. It’s such a neat feature that just makes so much sense in my mind and the way I operate in general - structuring work in a way that minimizes wasted time “finding” things.
Thank you and the Fibery team for making magic happen!