Assessment stakeholder

Assessment must always be driven by a problem, and problems only exist when a stakeholder makes them visible.

A stakeholder can be either a technical or non-technical team member. For example, the engineers from the development team should identify the concerns that are to be checked during the daily assessment. At the same time, a manager might want face a broader problem that should be approached through a strategic assessment.

Not all stakeholders are involved at the same time, but at one point or another, each of them will have a stake.

A stakeholder does not necessarily have to know the details of performing analyses. These technicalities are meant to be taken care of by the facilitator. But, it is the stakeholder that must initiate the process. The stakeholder owns the problem and knows how to interpret the assessment results. Furthermore, even if she is not an assessment expert, she should know what is answerable through an analysis, and should be acquainted with the problems and resources required by performing analyses.

In summary, a stakeholder must know how to:

  • trigger an assessment project,
  • digest the results, and
  • distill them into decisions.