Processes

Collect IT customer requirements

How collect it customer requirements are reshaped as AGI capability advances.

ProcessesCollect IT customer requirements
Collect IT customer requirements — illustrated

The bottom line

Roughly 90% of the work in Collect IT customer requirements 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 evaluation relies entirely on the process lens and description. The PCF lens 'Develop and manage IT customer relationships' firmly aligns with IT management priors (~0.90). The work itself—identifying IT gaps and analyzing expected business performance versus current outcomes—is purely information-based knowledge work executed via communication, documentation, and data analysis.

grounded in the economy graph · digital scalar 0.90 · 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 business unit requests a new technological capability or an IT planning cycle identifies a gap in current business performance.

  1. Engage business stakeholders to define expected performance levels
  2. Evaluate current business outcomes against technological capabilities
  3. Identify existing or potential IT performance gaps
  4. Elicit specific functional and non-functional IT requirements
  5. Document and validate requirements with business sponsors
  6. Prioritize documented requirements for IT portfolio planning

Outcome: Clear, validated IT requirements are documented and prioritized to address the identified business performance gaps.

Measured by

Requirement Documentation Cycle TimeBusiness Stakeholder SatisfactionPercentage Of Requirements ValidatedRequirement Traceability Rate