Define basic functional requirements
How define basic functional requirements are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Define basic functional 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, I relied on the APQC lens ('Generate and define new product/service ideas') and the process description ('Determining the operations of functions... in the marketing environment'). Defining functional requirements is purely analytical knowledge work involving information gathering, synthesis, and documentation, 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: A new product concept or market opportunity is approved for initial scoping and definition.
- Review approved product concept and target market data
- Identify core customer use cases and intended operating environments
- Translate user needs into specific functional capabilities
- Align proposed capabilities with business and marketing constraints
- Document and baseline the basic functional requirements for stakeholder sign-off
Outcome: A formalized set of basic functional requirements is baselined and ready for detailed technical design.