Coordinate project activities with other personnel or departments
Little of this can be handed to software today.
The reporting and paperwork around management automate well. Directing, developing and evaluating people does not, and people do not accept it when it is attempted on them.
| How automatable | Barely automatable |
|---|---|
| Kind of work | Managing, training and developing people |
| Jobs that do it | 10 occupations |
| Tool categories that apply | Enterprise platforms |
| O*NET activity | Guiding, Directing, and Motivating Subordinates (4.A.4.b.4) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 10 occupations that perform it.
- Coordinate sales or other promotional strategies with merchandising, operations, or inventory control staff to ensure product catalogs are current, accurate, and organized for best findability against user intent.
- Coordinate implementation of computer system plan with establishment personnel and outside vendors.
- Direct daily operations of departments, coordinating project activities with other departments.
- Coordinate network or design activities with designers of associated networks.
- Implement system renovation projects in collaboration with technical staff, engineering consultants, installers, and vendors.
- Work as part of a project team to coordinate database development and determine project scope and limitations.
- Collaborate with computer manufacturers and other users to develop new programming methods.
- Meet with clients to discuss topics such as technical specifications, customized solutions, or operational problems.
- Collaborate with engineers or software developers to select appropriate design solutions or ensure the compatibility of system components.
- Coordinate activities of workers engaged in cataloging and filing materials.
- Coordinate with developers to optimize Web site architecture, server configuration, or page construction for search engine consumption and optimal visibility.
- Work with personnel and facilities management staff to install, remove, or relocate user connectivity equipment and devices.
What we would actually use
Nothing in our landscape addresses this work. That is the honest answer rather than a padded list: this activity needs a person present, or a machine rather than a software agent.
Buy nothing. The reporting and paperwork around management run on whatever you already use for documents, and the part that is actually managing people does not automate at any price.
Chosen for the cheapest thing that does the job, not the best funded. Nothing on this site is sponsored, and the full landscape is there when you want to disagree with us.
The rest of the category
Context, not alternatives to weigh up. We name the layer rather than promise a named product does your specific task.
Enterprise platforms
Matched from the kind of work, not from vendor marketing. Check any of them can reach the system your records actually live in — that connection, not the model, is where these projects stall.
How people actually do it
No workflow names this activity yet, but these automate the same kind of work, with the prompts to paste and what to keep for yourself.
Who does this work
10 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
- Computer and Information Research Scientists
- Computer Network Architects
- Computer Programmers
- Computer Systems Engineers/Architects
- Database Architects
- Geographic Information Systems Technologists and Technicians
- Historians
- Information Security Analysts
- Search Marketing Strategists
- Telecommunications Engineering Specialists
Work that goes with it
O*NET groups these under “Direct organizational operations, activities, or procedures”. In practice they tend to be done by the same person, in the same sitting.
Method. The activity, its taxonomy placement and the occupations that perform it come straight from the public-domain O*NET 30.3 database. The automatability band is ours: we map each of O*NET’s 41 generalized work activities to how much of its output current software can produce, assuming a person still reviews and owns the result. It is a coarse three-way judgment on purpose. A precise-looking percentage here would be invented.