Cognitive Artifacts

What Are Cognitive Artifacts?

A map is a cognitive artifact. So is a checklist, a mathematical equation, a database schema, a decision tree, and a well-structured prompt template. What they share is this: each one takes complex knowledge, compresses it into a defined structure, and makes it usable by anyone who understands the format.

The term comes from cognitive science, where it describes any external object that aids or extends human cognition. A calendar extends your memory. A spreadsheet extends your ability to calculate. A diagram extends your ability to reason about relationships. These are not just tools — they are extensions of your mind, distributed across physical and digital objects.

In the context of augmented intelligence, cognitive artifacts take on a specific and critical role: they are the units of exchange between human and machine cognition. When you give an AI a well-structured prompt, you are handing it a cognitive artifact. When the AI returns a structured output — a JSON object, a decision matrix, a formatted analysis — it is handing one back. The quality of the collaboration depends directly on the quality of these artifacts.

This is why freeform text, despite being natural and easy to produce, is often the worst medium for human-AI collaboration. It is the least structured cognitive artifact available — and structure is what makes artifacts powerful.

Architected Data Objects

The three pillars framework introduces Architected Data Objects (ADOs) as the third pillar of augmented intelligence. ADOs are cognitive artifacts with a specific set of properties: they are standardised, efficient, and designed to encapsulate truth into shareable, universally interpretable units.

Think of the difference between a conversation about project status and a project dashboard. The conversation is rich, nuanced, and ephemeral — once it ends, the information degrades with every retelling. The dashboard is structured, persistent, and consistent — anyone who looks at it sees the same information, interpreted through the same format.

Both convey information. But the dashboard is an ADO. It compresses complexity into a defined structure. It can be shared without loss. It can be processed by machines as well as humans. It can be versioned, compared, and audited. The conversation cannot do any of these things.

ADOs are not limited to dashboards. They include:

• Schemas and templates that define the shape of information before it is created.
• Structured outputs from AI — JSON, XML, tables, typed objects — that encode information in machine-readable form.
• Knowledge atoms — the smallest self-contained units of knowledge that can be independently verified, stored, and composed with other units.
• Canonical formats — agreed-upon structures for common types of information (meeting notes, project briefs, technical specifications) that reduce interpretation overhead.

Loose Text vs Structured Knowledge

The default output of most AI interactions is prose — paragraphs of text that read like a knowledgeable person speaking. This prose is easy to consume but difficult to use. It degrades with every step of reuse.

Consider asking AI to analyse a market opportunity. It produces three paragraphs of fluent text about market size, competitive landscape, and growth potential. This feels useful in the moment. But try to use it:

• Can you compare it directly to an analysis of a different market? Not without re-reading and manually extracting the comparable data points.
• Can you feed it into another AI system for further processing? Only as raw text, losing the implicit structure.
• Can you track how the analysis changes over time? Only by comparing paragraphs, which is imprecise and labour-intensive.
• Can another person quickly find the specific data point they need? Only by reading through the prose to locate it.

Now consider the same analysis as a structured artifact: a defined schema with fields for market size (with units and date), competitor list (with market share percentages), growth rate (with confidence interval), key risks (enumerated), and data sources (cited). Every piece of information has a defined location, format, and relationship to other pieces.

The structured version is comparable, composable, machine-readable, versionable, and auditable. It took slightly more effort to create — you had to define the schema and ask the AI to populate it — but the return on that effort compounds with every subsequent use.

This is the fundamental argument for cognitive artifacts in AI work: a small upfront investment in structure yields large returns in reusability, reliability, and collaborative value.

Schemas, Templates, and Formats as Cognitive Artifacts

Schemas are perhaps the most powerful type of cognitive artifact because they are generative — they do not just capture one piece of knowledge, they define the shape of an entire category of knowledge. A schema for "meeting notes" determines what information gets captured from every meeting. A schema for "bug report" determines what context accompanies every issue. The schema itself encodes organisational wisdom about what matters.

When you work with AI, schemas serve a dual purpose. First, they constrain the AI's output into a useful form. Instead of receiving a wall of text, you receive data that fits a defined structure. Second, they force you to think clearly about what you actually need. Defining a schema requires you to decide: what fields matter? What format should each take? What is required versus optional? This thinking is valuable independent of the AI.

Templates are schemas with defaults — partially completed artifacts that encode best practices. A meeting notes template that pre-populates "Decisions," "Action items," and "Open questions" sections ensures these categories are addressed every time. A project brief template that includes "Success criteria" and "Known risks" prevents these from being overlooked.

Formats are the most granular level: the specific conventions for representing individual data points. Dates as ISO 8601. Currency with explicit codes. Names in "family, given" order for sorting. These feel like bureaucratic details, but they are the connective tissue that allows cognitive artifacts to be reliably composed, compared, and processed.

Why Structured Output from AI Is More Valuable

There is a straightforward reason why structured AI output outperforms freeform text: structured output is verifiable.

When AI returns prose, verifying it requires reading every sentence and assessing each claim — a slow, cognitively demanding process that most people skip. When AI returns structured data, you can verify it field by field. You can write automated checks. You can compare it against known values. You can spot missing data by looking for empty fields rather than re-reading paragraphs to notice what was omitted.

Structured output is also composable. Individual artifacts can be combined into larger structures. A collection of structured meeting notes can be aggregated into a project timeline. A set of structured analyses can be compared in a table. A library of structured templates can be assembled into a complete workflow. Prose does not compose — it accumulates.

Finally, structured output creates a feedback loop. When AI fills a schema and gets a field wrong, you can identify exactly which field failed and why. This gives you precise information for improving your prompt, adjusting your schema, or flagging a domain where the AI is unreliable. When prose contains an error, you often cannot isolate the cause because the error is entangled with surrounding text.

This does not mean prose is never appropriate. Natural language remains the best interface for exploration, brainstorming, and communication between humans. But when you need AI output that you will build on, share, store, or act on — structure it. The cognitive artifact you create will serve you far better than the paragraph that was easier to produce.

Building a Practice of Cognitive Artifacts

Working with cognitive artifacts is a practice, not a one-time decision. Here is how to develop it:

1. Start with your most repeated AI interactions. Identify the tasks you do most often with AI. For each one, design a simple output schema. Use it consistently and refine it based on what works.
2. Build a personal template library. Collect the schemas, formats, and prompt templates that work well for you. Store them in your knowledge management system. Over time, this library becomes a powerful productivity tool — each template encodes lessons learned from dozens of past interactions.
3. Share and standardise within teams. Cognitive artifacts become more powerful when shared. When a team agrees on a standard schema for a project brief, every brief produced by any team member is immediately comparable and composable. Standardisation is not bureaucracy — it is collective intelligence infrastructure.
4. Iterate on structure, not just content. When an AI output is not useful, the problem might not be the AI's capability — it might be the artifact's structure. Revise your schemas based on actual use. Add fields you keep needing. Remove fields you never check. The artifact should evolve with your understanding of the domain.