Automation index
How much of a Museum curator’s job can AI already do?
An inventory and a wall text come earlier. What goes on show, and not damaging the piece, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Museum curator
23%
AI can already do 23% of this job.
#291 / 633
View rankingMuseum curator
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Inventory, catalogue and write wall texts.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Curate, select and negotiate loans.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Install, lighting and preventive conservation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Research, publications and dossiers.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Public, tours and the board.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Not losing a piece or a wrong attribution.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 23% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Inventory, catalogue and write wall texts
- Curate, select and negotiate loans
- Research, publications and dossiers
- Public, tours and the board
- Not losing a piece or a wrong attribution
- conservador de museo
- curator
- comisario de exposicion
Sources for this job· O*NET 25-4012.00· ESCO/ISCO 2621
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641