A newbie analyst, as a rule, spends an awful lot of resources to manage basic tasks: gathering necessary information, documenting it consistently, supplying the team with the decent amount of work for upcoming iteration and managing stakeholders relationship.
As the expertise grows, the analyst starts doing all the necessary things automatically and it leaves time and resources for processes improvement, sometimes beyond own role.
The information, which the analyst owns in his role is essential not only for analysis but for requirements building too. Some parts like context, functional architecture or specific low-level details play a dramatic role in developing team motivation and help improving work efficiency and be proud of the results.
In the talk, the speaker sums up own experience in part increasing team awareness beyond knowledge necessary for everyday work needs.