The TECK Framework
A Simple Productivity Tool Architecture

Most productivity frameworks act as if your entire second brain exists inside a single note app or a few file folders. They often ignore better solutions for calendar appointments, quick errands, communication streams, and reading apps. When you force everything into one app, your system turns into a cluttered mess.
To fix this structural gap, I developed the TECK Framework—an architecture that segments all digital activity into four distinct human operational pillars:
T — Tasks (Do & Acquire): Single-step execution items, errands, reminders, and physical next steps.
E — Events (Be & Remember): Hard temporal anchors, appointments, and time blocks.
C — Communication (Hear & Say): External relational data streams, messaging, and emails.
K — Knowledge (Store & Recall): Internal thoughts, creations, reference materials, and general Foray note vaults.
Note: This essay is Part 3 of a 3-part productivity methodology. Together with The Foray System (Taxonomy) and The ISO Approach (Process), these essays outline a complete, essentialist operating system for real life.
In The Foray System and The ISO Approach, we break down a minimalist taxonomy (Annex, Action, Areas, Atlas) and a zero-friction process engine (Input, Structure, Output).
Together, Foray and ISO handle where information lives and how it moves. But even the cleanest notes app and process pipeline can break down if you don't answer a fundamental, real-world question: Where does a note end and the rest of your digital life begin?
The TECK Domain Boundaries
TECK is simply a reference framework that helps you decide which tools do what. As long as you have these bases covered, you can stay on top of your everyday life. Here's how I break mine down. You can see that I heavily rely on Google's tools, but you can use whatever solutions you prefer.
Tasks (T): Do & Acquire
Google Tasks
Checkbox Lists in Google Keep
Events (E): Be & Remember
Google Calendar
Communication (C): Hear & Say
Gmail
Google Messages
Signal
Knowledge (K): Store & Recall
Google Keep
Google Drive
Clarifying the Domains
Tasks (T) vs. Foray’s Action Bucket
A potential point of confusion when using the TECK Framework with The Foray System is how Tasks (T) differs from Action.
Think of Foray’s Action bucket as a project container inside your note vault—it holds multi-step project outlines, pinned chore lists, and operational plans. Tasks (T) in TECK represents the execution line-items that live in a dedicated task app (like Google Tasks or Apple Reminders). Action answers "What is the full picture of this project?" while Tasks answers "What single physical step am I executing right now?" Grocery lists, for me, typically go in Action, and errands/reminders for the day go in Tasks. Home improvement planning details go in Action, but setting a reminder to call your spouse to ask which color paint to grab at the store goes in Tasks.
The Hidden Framework Gap in Popular Systems
Most systems fail not because their note-taking ideas are bad, but because they have operational blind spots or they ask you to overextend a single app. They overload their primary notes app with data that belongs somewhere else:
1. The PARA Problem: Conflating Tasks, Events, and Knowledge
Tiago Forte’s PARA focuses almost entirely on Knowledge (K). It tries to handle Tasks (T) by putting "Projects" at the top of your note folder hierarchy.
The Gap: A note folder is a terrible place to manage daily errands or time-sensitive reminders. When project files, daily checklists, and meeting notes all sit in the same app, folders become cluttered and abandoned. PARA acknowledges everything doesn’t go here, but it doesn’t offer a robust solution.
The TECK Solution: Hard time lives strictly in Events (E) (calendar). Active to-dos and action reminders live in Tasks (T) (task app). Background research lives in Knowledge (K) (notes app).
2. The ACE Overreach: Converting Events into Notes
Nick Milo’s ACE Framework attempts to handle time by encouraging daily journal notes, weekly logs, and timeline documents inside your markdown vault.
The Gap: Managing time through daily markdown notes turns your search engine into a graveyard of empty date-stamped files.
The TECK Solution: If an item does not have a strict date and time attached to it, it can be a Task or a Knowledge item instead of an Event. Calendar events live in native calendar apps (Events), leaving your Knowledge vault clean.
3. The Communication Shortcoming: How do we approach our conversations?
Most productivity systems treat knowledge work like a solitary craft performed inside a vacuum. Frameworks like PARA, Zettelkasten, ACE, Forever Notes, and even The Bullet Journal Method focus almost entirely on the Knowledge vault and often incorporate Tasks or Events, but they leave out one the single largest source of cognitive overload in modern life: Communication.
It's a subtle change, but by formally codifying Communication (C) as an independent operational pillar alongside Tasks, Events, and Knowledge, TECK fills a structural gap that other frameworks ignore. It does this by embracing Inbox Zero and migrating relevant information to useful destinations:
The Gap: Without a communication pillar and workflow, your messaging apps become messy "holding pens" or even entirely separate from the rest of your productivity system. Users star or favorite chat threads, leave messages unread as visual prompts to revisit them, or let unread emails sit indefinitely as an improvised to-do list. These are all subpar and ineffective ways of managing communication.
The TECK Fix: Communication is isolated as its own transient inbound/outbound stream and effective tools are identified (e.g., iMessage, WhatsApp, Gmail, etc.). Messages are never allowed to become permanent residents or loiterers in your inboxes by enforcing basic Inbox Zero principles:
Actionable request > Transformed instantly into a Task (T).
Meeting or time-bound invite > Migrated to an Event (E).
Long-form article or reference material > Routed to read-it-later app or the Knowledge (K) vault via Foray (Annex/Areas/Atlas).
Relational conversation or ephemeral information > Read, reply, and/or archive.
How TECK, Foray, and ISO Work Together
In short, TECK is about identifying the tools you will use within the four domains that organize our everyday lives. TECK is more of a "set it and forget it" solution, while Foray and ISO are ongoing organizational strategies.
But when you layer Foray, ISO, and TECK together, you get a complete, frictionless operating system for real life:
Tasks (T): Quick standalone actions sit in your tasks app like Things 3, Todoist, TickTick, etc. Multi-step projects or lists live in Foray’s Action bucket as dedicated project notes. When an Action note requires physical execution at a specific time, the immediate next physical step gets pushed out of the note vault and into your Tasks. This is about what you do.
Events (E): Google Calendar handles hard temporal anchors, appointments, and time blocks. No calendar notes clogging your note vault. This is about where and how you spend your time.
Communication (C): Document the apps you use that handle real-time messaging; email and messages are triaged to zero daily utilizing the Inbox Zero methodology. Actionable items become Tasks, time sensitive activities or occurrences become Events, and general information or ideas move to Knowledge
Knowledge (K): Your second brain. Unsorted thoughts and information land in Annex, project details and lists live in Action, personal information lives in Areas (Inward Out), and world knowledge lives in Atlas (Outward In).
System Guardrails for the Real World
Productivity shouldn't mean trying to force your entire life into a single app or spending hours maintaining intricate web links.
By defining clear domain boundaries through TECK, you stop asking your note app to be your calendar, your task manager, and your second brain at once. Respect the boundaries of each operational mode: execute your Tasks, anchor your Events, clear your Communication, and cultivate your Knowledge.
To see how to organize your data and knowledge, read Part 1: The Foray System. To see how data moves through these buckets, read Part 2: The ISO Approach.