18 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You spend mornings reading and collecting past reports, user logs, design docs and recorded interviews, then tag and store them in Microsoft SharePoint or Access. That keeps sources organized for later analysis.
Afternoons are analysis and synthesis: run quantitative checks in Microsoft Excel or IBM SPSS Statistics, code qualitative notes, draft timelines or storyboards in PowerPoint, and save drafts in Word or Acrobat. You also meet designers to explain historical patterns and plan user tests.
Start with Microsoft SharePoint to store, share, and version historical collections and research files—teams rely on it. Learn Excel next for cleaning and plotting data, and PowerPoint for timelines and presentations.
Then get comfortable with Word and Adobe Acrobat for reports. If you’ll do stats, learn IBM SPSS Statistics. Microsoft Access helps when you need a structured local database of sources.
You apply source criticism by checking who produced the data, when, and why—document that in your metadata fields in SharePoint or Access. Rate reliability: firsthand logs or validated usability tests score higher than vague recollections.
Cross-check claims against multiple sources, note contradictions in your report (Word/Acrobat), and flag uncertain items for designers so product choices reflect evidence strength, not guesswork.
Yes, but use AI as a drafting tool only. Feed AI precise source snippets, dates, and document IDs from SharePoint; never ask it to invent facts. Always verify each AI-generated claim against original files and cite the exact source.
Keep a revision log and save verified drafts in Word/Acrobat. If confidential material is involved, follow your company’s data policy—don’t upload private files to public AI services.
According to the U.S. Bureau of Labor Statistics (BLS) for this SOC (19-3093.00), about 3,450 are employed. The median pay is $76,750 per year; the lowest tenth is $42,730 and the top tenth is $131,810. Those are BLS numbers.
Pay varies by sector: museums or non-profits often sit near the low end, tech or consulting firms pay toward the high end. Experience with SPSS, SharePoint, and large archival projects raises value.
A historian writes long interpretive narratives and books; an archivist organizes, preserves, and catalogs original materials. A UX researcher focuses on how historical evidence explains user behavior and product decisions.
You still catalog and evaluate sources like an archivist and interpret trends like a historian, but your deliverables are short research reports, timelines (PowerPoint/Word), and design recommendations rather than academic monographs.