<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>The deep end. on Atlas of Work</title>
		<link>https://www.atlasofwork.ai/research/</link>
		<description>Recent content in The deep end. on Atlas of Work</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 02 Nov 2026 09:00:00 -0800</lastBuildDate>
		
			<atom:link href="https://www.atlasofwork.ai/research/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Introducing Atlas of Work</title>
				<link>https://www.atlasofwork.ai/research/introducing-atlas-of-work/</link>
				<pubDate>Mon, 02 Nov 2026 09:00:00 -0800</pubDate>
				<guid>https://www.atlasofwork.ai/research/introducing-atlas-of-work/</guid>
				<description>&lt;p&gt;Ask whether AI can do a job, and the most useful answer often starts with another question: which part of the job?&lt;/p&gt;&#xA;&lt;p&gt;A title can hide an extraordinary variety of work. The same person may gather information, interpret an exception, coordinate with a colleague, make a judgment, and document a decision. Those activities depend on each other. They also depend on a setting that a short job description rarely captures.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Work is more than a job title</title>
				<link>https://www.atlasofwork.ai/research/work-is-more-than-a-job-title/</link>
				<pubDate>Mon, 02 Nov 2026 08:00:00 -0800</pubDate>
				<guid>https://www.atlasofwork.ai/research/work-is-more-than-a-job-title/</guid>
				<description>&lt;p&gt;“Accountant,” “engineer,” and “designer” are useful names. They tell us where to start a conversation. They do not tell us everything a person does, what information they need, or how they decide that the work is finished.&lt;/p&gt;&#xA;&lt;p&gt;When we want to understand where AI might help, those details become the subject. We need a description of the work that is specific enough to examine and connected enough to preserve context.&lt;/p&gt;</description>
			</item>
			<item>
				<title>What does an AI benchmark actually tell us?</title>
				<link>https://www.atlasofwork.ai/research/reading-ai-evidence/</link>
				<pubDate>Mon, 02 Nov 2026 07:00:00 -0800</pubDate>
				<guid>https://www.atlasofwork.ai/research/reading-ai-evidence/</guid>
				<description>&lt;p&gt;A benchmark can make a capability claim more concrete. It gives us an assessment to inspect: a task, a setup, a set of outputs, and a way of judging them.&lt;/p&gt;&#xA;&lt;p&gt;The result becomes more useful when those details stay attached to it. In Atlas, we think about evidence as something to follow back to its source, with enough context to understand both what it supports and what it leaves open.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
