Identify needs from stakeholders
How identify needs from stakeholders are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Identify needs from stakeholders is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: With no seeded child occupations, the scalar is derived from the lens and process description. Although the top-level 'Manage environmental health and safety (EHS)' category often involves hybrid physical environments, the specific process of 'Gathering information from stakeholders prior to conducting analytics' is pure information-gathering and requirement-scoping. This is remotely-doable knowledge work, placing it firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: An upcoming analytics project or reporting cycle prompts the data team to engage with business stakeholders.
- Identify and map relevant stakeholders for the upcoming analytics initiative
- Schedule and conduct discovery sessions or distribute requirement surveys
- Document specific business questions, required data points, and expected analytical outcomes
- Review gathered requirements for technical feasibility and strategic alignment
- Obtain formal sign-off on the defined needs from key stakeholders
Outcome: Stakeholder requirements and business questions are fully documented, prioritized, and approved to guide the analytics initiative.