​@Abby S ​@Emma Ting 1. What are your biggest pains with exporting to PowerPoint and Word? Making sure that the export meets Section 508 accessibility compliance requirements, and similar requirements. There are different requirements in Colorado vs. the USA.
2. What are your expectations from an integration with PowerPoint and Word? Synching ability

I just tried to 'export' my work to PowerPoint, which is cumbersome in itself because so many clicks and logins are required just to get the add-in working. This is not a good user experience. The term 'export to PowerPoint' is also confusing, as I would expect to export a file in PowerPoint format, rather than just embedding a 'live connection' from PowerPoint to LucidChart. The problem with this is that I always end up with all the Lucid icons and GUI elements on my PowerPoint slide. How can I possibly give a clear presentation when all that unwanted stuff is always showing up on the slide? It's ugly and useless, and it has no value to me. Ideally, I would like to be able to use the created graphic or org chart in PowerPoint and edit it. However, I could not find a way to hide those elements, which makes this functionality useless for me.

I enjoyed walking through that maze :)

For me, the biggest pain is losing formatting or alignment when exporting diagrams. My expectation is that it should have the ability to retain text boxes, shapes, and lines as editable elements in PowerPoint/Word.

Thank you ​@aparrish, ​@MaKe68, and ​@Ria S for taking the time to leave your feedback here!

Thank you for your feedback ​@MaKe68 ! I’ve left you a private message about providing further feedback if you’re able. Thanks again! 

I am the author of professional technical publications and I used Visio for a very long time. I created custom tools and custom templates/shapes to create clear and nice looking publications. The backend tool is Framemaker, but the documentation is first created and proofed in MS Word, and sometime reviewed in MS Powerpoint. The main requirement for technical publications is to transfer data as scalable vector graphics to keep it this way to print shop and Acrobat viewing, which can preserve the vector format and allow zoom to view details. 

Our management made a move to Lucid charts as corporate IT strategy, and it destroyed this flow for me and other colleagues. Lucid is still way inferior for technical publication work.  

The cut/paste from Visio is transferring vector metafile to Word document, and it is easy and quick. One can also select a part of a larger diagram and insert it in the document, still in vector format.

Lucid allows to export data as Visio file and also as SVG. The Visio output is good as it can be edited further, but why do I need Lucid if I can do much more in Visio directly?

I explored SVG path as alternative. It is very cumbersome, with some generated links, downloads, etc., etc. So while it can generate vector graphics, it is very inconvenient. In fact, there are members of my team contributing documentation, and they use to take a screen snippet from the browser and paste it into document, that results in the need of replacing these illustrations manually, when the sources are already lost or their location is unknown. So this way it does not fit into workflow, 

What is needed is an ability to select a region of the diagram, and seamlessly save it in an SVG file on the local computer, ideally in one click. This way it can be inserted in MS Word document as a file reference, and later same may be imported in Framemaker. The keyword is really “one click”, without many menu windows, navigation through taskbar, etc. It may be a function of right click on the mouse.

The *.SVG transfer is not perfect, because it is really not editable in the same level of abstraction as in original drawing, so I guess another nice feature would be to include a way to insert a link (?) somewhere which allows to open the original diagram directly. For instance, it could be an *.htm file with the same name as SVG file, created simultaneously with SVG and stored together.