Atomic Artifacts

TL;DR - Atomic Artifacts do one thing well. Make atoms -> produce impact -> compound over time / cycles.

Overview

Atomic Artifacts are creations that are:

• Atom - Do one thing well. Durable, complete, composable, practical.
• Impact - Solve problems systematically. Robust, reproducible, reusable, measurable.
• Compound - Scales vertically (up + down), horizontally, and sideways over time, usecases, and users. Efficient, sustainable, understandable, evolvable.

By focusing on atomic artifacts, we unlock a compounding library of tools we can deploy, combine, evolve, and redeploy to achieve greater impact - solving increasing numbers, magnitude, and shapes of problems.

To implement these I like to ask a few questions about any project / plan / implementation I'm working on:

• Is this atomic?
• Is this impactful?
• Does this compound?

Atomic Artifact Examples

Atomic Artifacts can take any form - physical objects, concepts, implemented systems, written processes, etc.

• Software - Atomic tools and systems. Well defined functions, libraries, apps all fall into this category. Each does its job well and can be composed together to build systems of increasing capability while keeping complexity manageable.
• Writing - Atomic essays. Self-contained essays on one particular subject. Links out to other such essays for additional context. Each essay is an atom, together they represent knowledge.

SECTION

Todos

• Tighten up the language of atomic, effective, efficient vs simple scalable systems.
• Likely need a sectoin or page on atomic systems and simple scalable systems to link to