Interview topic 2: developing a brief
The "brief" defines and directs the project, outlining the difference that the project is expected to make. It might specify, in more or less detail: aims, indicators and measures of success, limitations, risks, deadlines, resources, budgets, users, partners - whatever is necessary to give the project the definition and direction that it needs.
- In some cases projects are commissioned with a brief that is clear, complete and uncontested.
- Sometimes, during a project, the brief is found to be problematic and in need of revisions. This additional work might be easily undertaken. At other times the brief might be contested by the various project participants. This could lead to conflict and disruption. It might add productively to the development of the project.
- In other cases we undertake a project knowing that the brief will need to be developed as we proceed.
- And sometimes we are personally responsible for developing a brief from scratch to initiate a new project.
Have you worked on projects where the brief is incomplete, unclear and/or contested? Or have you developed a brief to initiate a new project? How did this proceed? In what ways was it negative and positive? At what point (if at all) did you settle on a well defined brief? What strategies, tools and techniques did you use to get a better defined brief?
Will your experience of developing a brief be of use in other aspects of what you do?