Communicate service support needs
How communicate service support needs are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Communicate service support needs 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 child occupations seeded, this scalar is derived from the APQC process description and lens. The work involves defining procedures for 'IT services and solutions' and conveying needs to governing authorities under the 'Create and manage support services/solutions' lens. This is pure knowledge-based IT governance and administrative work, executed via digital documentation and communication.
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: A new or updated IT service requires formalization of its support procedures for end-users.
- Identify the technical and operational support requirements for the IT service.
- Draft the specific processes and procedures needed to assist end-users.
- Review the proposed support workflows with relevant IT and operational stakeholders.
- Compile the support procedures and resource requirements into a formal proposal.
- Present the support needs and procedures to the IT governing authority.
- Secure formal approval and mandate for the defined support procedures.
Outcome: Support procedures are fully documented, communicated, and approved by the appropriate governing authority.