Collaborate with others to resolve information technology issues.

Collaborate with others to resolve information technology issues. is a detailed work activity in O*NET — a concrete unit of work shared across 13 occupations and seen in 23 occupation-specific tasks. It rolls up into the broader work activity Coordinate with others to resolve problems. in Coordinating the Work and Activities of Others .

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 23 tasks under this activity that the OpenAI / Eloundou “GPTs are GPTs” study rated, 22 (96%) 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 11 of these tasks, with a mean mapped-usage share of 0.020% 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.

• Monitor systems for intrusions or denial of service attacks, and report security breaches to appropriate personnel. · Web Administrators · importance 4.8 · exposure with tools
• Collaborate with others in the organization to ensure successful implementation of chosen problem solutions. · Operations Research Analysts · importance 4.4 · exposure with tools
• Confer with project personnel to identify and resolve problems. · Information Technology Project Managers · importance 4.4 · exposure with tools
• Collaborate with senior managers and decision makers to identify and solve a variety of problems and to clarify management objectives. · Operations Research Analysts · importance 4.3 · exposure with tools
• Collaborate with development teams to discuss, analyze, or resolve usability issues. · Web Administrators · importance 4.2 · direct LLM exposure
• Consult with managerial, engineering, and technical personnel to clarify program intent, identify problems, and suggest changes. · Computer Programmers · importance 4.0 · direct LLM exposure
• Confer with users to discuss issues such as computer data access needs, security violations, and programming changes. · Information Security Analysts · importance 3.9 · direct LLM exposure
• Read technical manuals, confer with users, or conduct computer diagnostics to investigate and resolve problems or to provide technical assistance and support. · Computer User Support Specialists · importance 3.9 · direct LLM exposure
• Monitor security system performance logs to identify problems and notify security specialists when problems occur. · Web Developers · importance 3.7 · exposure with tools
• Communicate with vendors to gather information about products, alert them to future needs, resolve problems, or address system maintenance issues. · Computer Network Architects · importance 3.7 · exposure with tools
• Confer with users to analyze, configure, or troubleshoot applications. · Geographic Information Systems Technologists and Technicians · importance 3.7 · exposure with tools
• Meet with managers, vendors, and others to solicit cooperation and resolve problems. · Computer and Information Research Scientists · importance 3.6 · no direct exposure
• Confer with management or development teams to prioritize needs, resolve conflicts, develop content criteria, or choose solutions. · Web Developers · importance 3.6 · exposure with tools
• Communicate with network personnel or Web site hosting agencies to address hardware or software issues affecting Web sites. · Web Developers · importance 3.6 · direct LLM exposure
• Confer with network users about solutions to existing system problems. · Network and Computer Systems Administrators · importance 3.6 · exposure with tools
• Consult with and assist computer operators or system analysts to define and resolve problems in running computer programs. · Computer Programmers · importance 3.5 · direct LLM exposure
• Refer major hardware or software problems or defective products to vendors or technicians for service. · Computer User Support Specialists · importance 3.4 · direct LLM exposure
• Collaborate with field staff or customers to evaluate or diagnose problems and recommend possible solutions. · Software Quality Assurance Analysts and Testers · importance 3.3 · exposure with tools
• Confer with data processing or project managers to obtain information on limitations or capabilities for data processing projects. · Software Developers · importance 3.3 · exposure with tools
• Communicate with network personnel or Web site hosting agencies to address hardware or software issues affecting Web sites. · Web and Digital Interface Designers · direct LLM exposure
• Confer with management or development teams to prioritize needs, resolve conflicts, develop content criteria, or choose solutions. · Web and Digital Interface Designers · exposure with tools
• Confer with project personnel to identify and resolve problems. · Project Management Specialists · exposure with tools
• Identify problems uncovered by testing or customer feedback, and correct problems or refer problems to appropriate personnel for correction. · Web and Digital Interface Designers · direct LLM exposure

Occupations that perform this

• Web Administrators
• Operations Research Analysts
• Computer Programmers
• Information Security Analysts
• Computer User Support Specialists
• Web Developers
• Computer Network Architects
• Computer and Information Research Scientists
• Network and Computer Systems Administrators
• Software Quality Assurance Analysts and Testers
• Software Developers
• Project Management Specialists
• Web and Digital Interface Designers

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.

@misc{singulariki-collaborate-with-others-to-resolve-information-technology-issues,
  title  = {Collaborate with others to resolve information technology issues.},
  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-resolve-information-technology-issues}
}