Dashboards are often very helpful tools for analysts to explore large datasets, test hypotheses and view trends or patterns. They can also help us automate and reproduce repetitive tasks, save time that can be reallocated to more meaningful work and help manage frequent ad hoc time-limited requests/demands more easily. Quite often, however, when they are created to be unleashed across an entire organisation, they require more thought. Considered below are a few possible challenges that may arise when creating dashboard content:

• Dashboards don't automatically enable your end-user to ask good questions (end-users may not be skilled in knowing what to ask), 

• Dashboards don't automatically deliver solutions to problems (end-users may not know what action to take based on findings),

• End-users fail to find value in products and cease to use them.

Solutions? Two of the best opportunities for analysts (I think) are ensuring that you are working closely with the end-user and understand their needs (not always possible, in which case be clear about limits and deficiencies when delivering something that has been produced in response to a rigid or prescribed scope); and make yourself available to teach-end users how to navigate, understand and leverage your product to meet their needs. 

For strengths and opportunities, recommend a skim of the article Is Your Company Too Dumb To Be Data-Driven?