Chapter 1 recap
The job and the people
The key takeaways from this chapter’s 2 lessons.
Information management is a job, not a job title
- The information management function is a set of activities, not a role. Each party assigns them to named people, often in existing roles.
- The client must assign its own function before it appoints anyone else; it can get help, but it stays accountable.
- Two stages happen once per project (assessment and need, close-out); the six in between repeat for every appointment.
- The usual failure is not ignorance but priority: busy people drop information tasks first. Plan for that.
Parties, teams and appointments
- The appointing party is the client (or whoever manages information for it). A lead appointed party is appointed by the client. An appointed party is appointed by a lead appointed party and produces information.
- Every lead appointed party leads a delivery team, even a team of one. The project team is the client plus all delivery teams.
- Roles follow appointments, not company types: the same architect can be a lead appointed party before novation and an appointed party after.
- Information must be coordinated across delivery teams as well as within them.