Allow for trial and error in the beginning
Ardoq is a flexible tool, but since the diagrams are automatically generated we have had to make trade-offs in terms of what each diagram is best suited for visualizing. For instance, what is most important to visualize in a sequence diagram? Point-to-point integrations or message flow?
This is perhaps the most difficult part about working in Ardoq, and in our experience, there is no getting around a trial and error phase, during which you might try modeling the same scenarios in different ways and seeing how this impacts the visualizations. Doing this can help you to decide how to prioritize how you want to use Ardoq.