The ISO Approach
A Clear, Flexible Process Pipeline

In The Foray System, we break down a minimalist, four-bucket taxonomy (Annex, Action, Areas, Atlas) designed to solve our digital orientation problem. If Foray is the scaffolding (where information lives), then you need a process engine to run alongside it.
Enter the ISO Approach: Input, Structure, Output.
Just as Foray offers an alternative to structural frameworks like PARA and ACE, ISO offers a simpler alternative approach to complex process pipelines like Tiago Forte’s CODE (Capture, Organize, Distill, Express) and David Allen’s GTD (Capture, Clarify, Organize, Reflect, Engage).
ISO presents a calm, zero-friction process engine built for real life. It acknowledges a simple truth: normal people don't need to spend hours manually editing, bolding, and summarizing old notes just to get things done.
Note: This essay is Part 2 of a 3-part productivity methodology. Together with The Foray System (Taxonomy) and The TECK Framework (Domains), these essays outline a complete, essentialist operating system for real life.
The Problem with Traditional Process Pipelines
Most process models introduce a heavy "processing tax":
CODE's "Distillation" Homework: Relies heavily on Progressive Summarization. You capture a note, organize it, and later go back to bold key sentences, highlight phrases, and write executive summaries. Doing distillation homework on auto repair notes or coffee recipes feels unnecessary and overwhelming. You eventually stop doing it because it's too much friction for most of us in our daily lives.
GTD's Administrative Machine: Demands hours every week clearing open loops, sorting tasks into location contexts (Calls, Errands, Work, etc.), and reviewing multi-tiered horizons. If you skip a week, the system loses steam, and the backlog maintenance is even more work.
ACE's Interlinking Tax: Focuses on fluid headspaces but demands that you constantly build Maps of Content (MOCs) and manually interlink notes. Capturing turns into an obligation to maintain a digital garden. The idea is absolutely brilliant. But even though you can pay a premium for premade vaults, the average person will not see a real payout for weeks, months, or even years without ample effort upfront.
Forever Notes' Manual Webbing: Streamlines knowledge inside Apple Notes but requires custom shortcuts and manual inter-note link maintenance. It trades app complexity for manual labor. Similar to other solutions, the backlog maintenance becomes overwhelming.
Bullet Journal's Paper Bottleneck: Nails rapid logging, but paper isn't easily searchable, migration often requires retyping notes, and digital ports turn chaotic without pipeline guardrails. BuJo probably reflects the average person's needs the most accurately out of the existing solutions, but analog tools have many obvious drawbacks.
Taking the Best, Stripping the Bloat
ISO takes the best capture and process mechanics, strips away administrative bloat, and combines them:
From BuJo: The rapid-logging mindset—instant, frictionless capture.
From GTD: Raw ideas land in a trusted inbox first; actionable items lead to physical execution.
From CODE: Information moves through a pipeline toward a purpose rather than sitting in a stagnant pile.
From ACE & Forever Notes: Using accessible tools to map reference knowledge without forced, manual link-maintenance.
The 3 Stages of ISO
As a flexible, minimally structured knowledge pipeline, The ISO Approach is a simple three step process that includes only the necessary steps.
1. Input (Frictionless Ingestion)
Concept: Raw capture. Your intake valve.
Rule: Rapid capture without overthinking or worrying about formatting. Whether it’s a quick voice note, an article link, or a part number, capture it in seconds.
Connection to Foray: Inputs land directly in Annex (your working scratchpad).
2. Structure (Context & Guardrails)
Concept: Structure isn't about doing required distillation homework or pasting manual links; Structure is about adding context, establishing boundaries, and placing items into systems.
Organization Rule: When processing your Annex inbox, ask three quick placement questions:
Is this a checklist, physical next move, or sequential steps? Migrate to Action.
Is this about me, my personal standards, routines, identity, or original creations? Migrate to Areas (Inward Out).
Is this about the world, external references, facts, or general knowledge? Migrate to Atlas (Outward In).
Context: Structure takes as little as 2 seconds per item. It gives raw text visual guardrails for instant retrieval without required ongoing formatting maintenance.
3. Output (Execution & Interactivity)
Concept: The ultimate destination. Information serves a practical purpose.
Rule: Output manifests in two ways:
Physical Execution: Checking off a task in Action, running an errand, completing a workout, developing an original work, etc.
Active Retrieval & Synthesis: Referencing technical data in Atlas or reviewing habits or creative writing in Areas.
The ISO Approach Pipeline summary: Input (Frictionless Ingestion) ─> Structure (Context & Guardrails) ─> Output (Execution & Synthesis)
Note: If you like parts of other techniques like CODE, you can incorporate some of those principles into your context development or output workflow as well. Maybe we won’t “Distill” important details in your shopping list, but if you are trying to dive into your upcoming voting strategy, perhaps progressive summarization could be a huge benefit or perhaps even the end goal. Structure is fluid and adaptable, allowing you the freedom to do so as you need while requiring less of you for ongoing maintenance. I personally use tags on all of my notes for even further context. If I don't add those tags in the capture phase, I'll do it when I Structure my notes. What the Output looks like simply depends on your desired outcome. ISO is about having less rules and more possibilities.
Comparing the Process Pipelines
CODE
Pipeline Approach: Capture > Organize > Distill > Express
Major Bottleneck/Friction Point: Progressive Summarization (bolding/summarizing) takes too much time in a normal busy life.
The ISO Alternative: Skip manual distillation in most cases. Structure inputs by directional intent (Action vs Areas vs Atlas) and distill only when necessary.
GTD
Pipeline Approach: Capture > Clarify > Organize > Reflect > Engage
Major Bottleneck/Friction Point: Location contexts (Calls, Work, Errands) and multi-tiered reviews create high admin maintenance.
The ISO Alternative: Streamline into Action. Simplify and focus on immediate, physical next steps and clear checklists.
ACE
Pipeline Approach: Atlas & Calendar & Efforts
Major Bottleneck/Friction Point: Requires ongoing manual creation of MOCs and markdown interlinking.
The ISO Alternative: Keep Atlas as a simple reference bucket. Link only when helpful, not as a requirement.
Forever Notes
Pipeline Approach: Home Hubs & Linked Journals & Tags
Major Bottleneck/Friction Point: Manual wiki-linking and complex daily journal shortcuts.
The ISO Alternative: Eliminate manual link maintenance. Let simple folder or tag guardrails organize notes and link between them if your app allows it and you find it useful. | |
Bullet Journal
Pipeline Approach: Rapid Logging > Collections > Migration
Major Bottleneck/Friction Point: Paper doesn't search well, and digital ports lack structural guardrails.
The ISO Alternative: Adopt rapid logging in Annex, then route notes into digital Foray buckets.
Process for the Real World
Think of Foray as the taxonomy (the house) and ISO as the workflow (how you live in it):
Input: You scan the important details of a manual or type an errand note. They land in Foray’s Annex.
Structure: When you have a minute, move the errand note to Action as a checklist, and move the scan into Atlas (Outward In).
Output: You complete the errand today, or you open Atlas next month in the garage and find the manual in two seconds.
Now that you have the taxonomy (Foray) and the process (ISO), read Part 3: The TECK Framework to see how to identify what tools you might need to cover all of your PKM and organizational bases.