In addition to the functions, as shown, the next obvious step is to put names in the frames for each node. A node in the tree denotes groups and sub-groups within the project organisation, names at a group or sub-group level could identify the persons responsible for leading that group within the team.
Each element (node) of the Organisational Breakdown Structure is assigned a unique code. Furthermore, by using a hierarchical coding structure, members of the organisation can be logically associated with Groups and Sub-Groups within the wider Project Team.
Ultimately, there is no reason why an Organisational Breakdown Structure cannot be developed to a level of detail where all individuals within the project are represented. It's a good way to show team members where they reside within the Project Team. A project organisation chart!?
The closer to the top of the OBS, the more likely the nodes will reflect organisations and not individuals, though it's a good idea to identify the responsible lead person within each organisation.
The most important role Project Team members lower down the structure have; is one of supporting and enabling those above them in the Organisational Breakdown Structure to deliver their tasks effectively and efficiently in line with the objectives of the Project.
FEEDING THE NEED!
This requirement of FEEDING THE NEED of those "above" you in the Project Team is relevant to all levels of the OBS, all the way to the Project Manager, Project Director, and also the Stakeholder Organisation.
Unfortunately, all too often projects are structured and organised in the less efficient, authoritarian and less motivated traditional structure associated with a corporate organisation chart.