For larger organizations with complex cross dependent teams its critical for users to be able to create groupings and elements(might be timeline representations, or a teams feature functionality that is subject to change) and have them structured and grouped such that they are able to be inserted into many other boards, but retain links to the original so that updates can propagate through. Currently I can’t find a way to do this!
The ease of communication with Miro brings mass amounts of data, but then the downside is the propagation of stale data and the power of Miro is negated as soon as the overhead of maintaining core truths to a project, such as a timeline or a core set of directives or a feature set functionality that is needed to be referenced between different teams boards becomes apparent.
I am slightly baffled that the Miro team has not comprehended this would be a problem space and adequately provided a solution to accommodate this already. It really is critical tooling for larger and complex teams dealing with feature developments.
How can something like this be elevated in priority and made critical path development for Miro development?
