One thing I notice in some of our IT teams are that folks consider LucidSpark as an infinite canvas.
Rather than version controlling and releasing revisions of documents (eg: architectural diagrams etc), people draw different iterations of block diagrams with sticky notes, emojis etc in the same diagram - starting from top left corner to bottom right (which is infinite (as far as I know)).
After several iterations, this whole Lucid documents become a mess leading to nobody knows which is latest/which is obsolete etc. Also it is very difficult to navigate through such a big Lucid document.
How do you handle this issue in your workplace? Are there any better ways to deal with this scenario? Are there any suggestions from Lucid team for dealing with this?
Thanks,
Honey
Honey Sukesan
Senior Software Developer
Best answer by cbailey
Good observation, this is where I’ve seen templatizing and facilitation become strong tools. Particularly in Lucidspark using the breakout boards for generative/exploratory discussions which then turn into final outputs that are placed on the main board. You can structure this by creating spaces (using boxes or containers) that show where you’d want certain content to reside. This can also help with version control where you’re using the main page as the “source of truth.” Structuring content this way gives teams guardrails for where to look for key information.
Alternatively I’ve seen the use of color coding be successful where teams use one color stickies for generative discussion and then turn the final output to another color to show they’re finished. I personally prefer the former solution, but this works well as an alternative.
Though it may sound strange to constrain participants this way, “necessity if the mother of invention,” or in other words...constraints drive innovation :)
This seems like a very good observation and Limiting the number of diagrams iterations in a document would be challenging and if we consider this as an enhancement and getting some reliable solution would help this situation
Good observation, this is where I’ve seen templatizing and facilitation become strong tools. Particularly in Lucidspark using the breakout boards for generative/exploratory discussions which then turn into final outputs that are placed on the main board. You can structure this by creating spaces (using boxes or containers) that show where you’d want certain content to reside. This can also help with version control where you’re using the main page as the “source of truth.” Structuring content this way gives teams guardrails for where to look for key information.
Alternatively I’ve seen the use of color coding be successful where teams use one color stickies for generative discussion and then turn the final output to another color to show they’re finished. I personally prefer the former solution, but this works well as an alternative.
Though it may sound strange to constrain participants this way, “necessity if the mother of invention,” or in other words...constraints drive innovation :)
A Lucid account is required to interact with the Community, and your participation is subject to the
Supplemental Lucid Community Terms.
You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
A Lucid account is required to interact with the Community, and your participation is subject to the
Supplemental Lucid Community Terms.
You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
