I am exploring ways to recreate our fairly complex symbology library from ArcMap in ArcGIS Pro (2.2).
Currently, we symbolize by unique values on an attribute; symbols are the same but in different colors (e.g. Active is green, Abandoned is gray, Proposed is blue). Attribute-driven symbology seems like a reasonable candidate for these layers. While I can find some resources about how to enable and use attribute-drive symbology, I'm having a much harder time finding actual use-case examples to read about.
What are advantages of using attribute-driven symbology over the familiar unique value symbolization? Conversely, is there anything that we might lose by transitioning? (For example, using Arcade expressions will reduce the numbers of analysts/developers who have the skills to maintain and update symbols.) I'd appreciate a discussion of the pros and cons to help us make a more informed decision.