Roles and the Responsibility Matrix
32 min
On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks which organisation has failed when an information management task on a project goes undone, and how anyone could prove it in writing. A hypothetical council building a community hub, whose consultant's delegated scope stops at appointment, carries the argument through the four parties and the single information management function of ISO 19650, the principle at clause 7.1 of Part 1 that roles are not job titles, a reading of a project team appointment by appointment, the two matrices that share one name, a populated assignment matrix built from the clause text of ISO 19650-2, and a four-move written defence of a contested allocation. Chapters 0:00 Opening: the information model nobody was appointed to accept2:48 Four parties and one function: parties, teams, delegation and accountability7:13 Roles are not job titles: clause 7.1 of Part 1 and a typical roles guide11:36 Reading the team against the standard: the appointment map and three defects15:52 One name, two matrices: Annex A and the responsibility matrix for information deliverables19:48 Populating the empty matrix: the two rules, the Ferrybank allocation and the arguable row26:19 Defending the boundary: the four moves, false defences and a forward look30:07 CloseAfter listening, you should be able to: Distinguish the appointing party, lead appointed party, appointed party and third party from the project, delivery and task teams, name an organisation's role once for each appointment it holds, and explain why responsibility can be delegated under clauses 5.1.1 and 5.3.1 of ISO 19650-2 while accountability cannot.Apply clause 7.1 of ISO 19650-1 to separate job titles from functions, and identify the three faults in a roles document that uses job titles as party columns or attributes named roles to the standard.Map a project team by its appointments rather than its organisation chart, find a title that spans two roles, a title that misdescribes the wor...