Set stakeholders in frameworks roles, not people

What is the challenge?

Steps in Frameworks have a Stakeholder field which is a user field. People come and go over time but in a framework, the role of the person ought to remain the same. Typically, it is the contribution of that role which is important to a framework, rather than a specific person.

This also makes it hard for the framework to be generalised as a standard and taken up by specific teams because the person will change from team to team but again, the stakeholder role will remain constant.

What is the impact?

Framework step stakeholders will fall out of synch quickly or not be relevant at all. This renders the field's use limited or of no value.

Describe your idea

Something like approvers would be a better solution. Create stakeholder groups, assign stakeholders to stakeholder groups by workspace and then on each step, the stakeholder group can be added.

Clearly, this would need some thought as to how a line level framework cascades to workspaces but if there is a vision for the future to incorporate frameworks more deeply into Aha! with to-dos, automation, notifications, email capabilities then working from the off with roles should help. Even if there isn't that intention for greater integration, a role is just more applicable than a person to a framework - IMHO.