Collaborate with others to determine design specifications or details.
Detailed work activity
Collaborate with others to determine design specifications or details. is a detailed work activity in O*NET — a concrete unit of work shared across 13 occupations and seen in 21 occupation-specific tasks. It rolls up into the broader work activity Communicate with others about specifications or project details. in Communicating with Supervisors, Peers, or Subordinates .
Detailed work activities are the most granular shared layer in O*NET's work-activity hierarchy (Generalized → Intermediate → Detailed → occupation-specific task). The figures below describe how this activity shows up across the economy and what independent studies measure about AI and this kind of work — not a prediction that the work will be automated.
AI exposure
Of the 21 tasks under this activity that the OpenAI / Eloundou “GPTs are GPTs” study rated, 19 (90%) are flagged as directly exposed to language models (E1) or exposed via model-powered tools (E2).
The Anthropic Economic Index observes real AI use on 7 of these tasks, with a mean mapped-usage share of 0.128% per task.
Exposure estimates overlap with model capabilities — whether a model could speed the task up — not whether the work will be done by software. Observed AI use is augmentation and assistance today, not jobs replaced.
Member tasks
Occupation-specific tasks O*NET maps to this detailed work activity, most important first.
- Collaborate with system architects, software architects, design analysts, and others to understand business or industry requirements. · Database Architects · importance 4.5 · exposure with tools
- Solicit, obtain, and integrate feedback from design and technical staff into original game design. · Video Game Designers · importance 4.4 · exposure with tools
- Consult with users, administrators, and engineers to identify business and technical requirements for proposed system modifications or technology purchases. · Telecommunications Engineering Specialists · importance 4.3 · exposure with tools
- Communicate with staff or clients to understand specific system requirements. · Computer Systems Engineers/Architects · importance 4.2 · exposure with tools
- Participate in product design reviews to provide input on functional requirements, product designs, schedules, or potential problems. · Software Quality Assurance Analysts and Testers · importance 4.0 · exposure with tools
- Guide design discussions between development teams. · Video Game Designers · importance 4.0 · exposure with tools
- Collaborate with engineers or software developers to select appropriate design solutions or ensure the compatibility of system components. · Computer Systems Engineers/Architects · importance 3.8 · direct LLM exposure
- Confer with end users to define or implement clinical system requirements such as data release formats, delivery schedules, and testing protocols. · Clinical Data Managers · importance 3.8 · exposure with tools
- Confer with systems analysts, engineers, programmers and others to design systems and to obtain information on project limitations and capabilities, performance requirements and interfaces. · Software Developers · importance 3.8 · direct LLM exposure
- Confer with staff, users, and management to establish requirements for new systems or modifications. · Computer User Support Specialists · importance 3.7 · exposure with tools
- Communicate with customers, sales staff, or marketing staff to determine customer needs. · Computer Network Architects · importance 3.6 · exposure with tools
- Collaborate with artists to achieve appropriate visual style. · Video Game Designers · importance 3.6 · exposure with tools
- Consult with multiple stakeholders to define requirements and implement online features. · Video Game Designers · importance 3.6 · exposure with tools
- Consult with management to ensure agreement on system principles. · Computer Systems Analysts · importance 3.6 · no direct exposure
- Assist users in formulating Geographic Information Systems (GIS) requirements or understanding the implications of alternatives. · Geographic Information Systems Technologists and Technicians · importance 3.4 · exposure with tools
- Consult with users, management, vendors, and technicians to determine computing needs and system requirements. · Computer and Information Research Scientists · importance 3.4 · exposure with tools
- Confer with clients regarding the nature of the information processing or computation needs a computer program is to address. · Computer Systems Analysts · importance 3.1 · exposure with tools
- Define product requirements, based on market research analysis, in collaboration with user interface design and engineering staff. · Search Marketing Strategists · importance 2.9 · exposure with tools
- Confer with vendors to evaluate new equipment or reagents or to discuss the customization of product lines to meet user requirements. · Molecular and Cellular Biologists · importance 2.6 · exposure with tools
- Collaborate with web development professionals, such as front-end or back-end developers, to complete the full scope of Web development projects. · Web and Digital Interface Designers · direct LLM exposure
- Consult with lighting director or production staff to determine lighting requirements. · Lighting Technicians · no direct exposure
Occupations that perform this
- Database Architects
- Video Game Designers
- Telecommunications Engineering Specialists
- Computer Systems Engineers/Architects
- Software Quality Assurance Analysts and Testers
- Clinical Data Managers
- Software Developers
- Computer User Support Specialists
- Computer Systems Analysts
- Computer and Information Research Scientists
- Search Marketing Strategists
- Molecular and Cellular Biologists
- Lighting Technicians
Sources for this page
Every figure above traces to a named public dataset and the exact release below — not hand-written opinion. See the full methodology for what each measure does and does not mean.
- O*NET 30.3 U.S. Department of Labor / National Center for O*NET Development
- Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27) Anthropic
- “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130 OpenAI / academic
Data compiled June 2, 2026. Figures are estimates, not advice.
Cite this page
Singulariki. "Collaborate with others to determine design specifications or details.." Singulariki: a source-backed encyclopedia of work. Built from O*NET 30.3; Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27); “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130. Accessed June 7, 2026. https://singulariki.com/detailed-activities/collaborate-with-others-to-determine-design-specifications-or-details
Singulariki. (2026). Collaborate with others to determine design specifications or details.. Singulariki: a source-backed encyclopedia of work. Retrieved June 7, 2026, from https://singulariki.com/detailed-activities/collaborate-with-others-to-determine-design-specifications-or-details
@misc{singulariki-collaborate-with-others-to-determine-design-specifications-or-details,
title = {Collaborate with others to determine design specifications or details.},
author = {{Singulariki}},
year = {2026},
note = {O*NET 30.3; Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27); “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130. Accessed June 7, 2026},
url = {https://singulariki.com/detailed-activities/collaborate-with-others-to-determine-design-specifications-or-details}
} Citations name the underlying public dataset releases — they reflect what this page is built from, not just the URL.