Category field guide

Productivity & data operations

The tables, documents, drives, and working databases that keep AI workflows from living only in chat history.

Tools covered
4
Full reviews
0
Field notes
4

My position

How I decide what belongs in this layer

Airtable, Notion, Google Drive, and Google Sheets are the durable operating layer around AI work. They hold records, source material, review state, metrics, and handoff context that should not disappear when a conversation ends.

The risk is building a second undocumented system beside the real business process. I use these tools best when one surface is authoritative, field definitions are explicit, and automation writes remain traceable to the event that created them.

The working set

4 tools, with the evidence level visible.

A field-note label is not a downgrade or a placeholder. It is the honest boundary between useful experience and a completed repeatable review.

Field notesWorkflow operations

Airtable

A flexible operational database for content pipelines, tool tracking, approvals, affiliate records, and automation-friendly workflow state.

Excellent when a spreadsheet has become a workflow; dangerous when every team invents a different source of truth in the same base.Read the profile →
Field notesWorking knowledge

Notion

A flexible document and database workspace for briefs, operating notes, content systems, and team knowledge that needs more structure than chat history.

Strong for shared context and lightweight systems; a workspace can become an attractive attic if ownership and information architecture are absent.Read the profile →
Field notesOperational workflow

Google Drive

The shared file and source-material layer behind documents, media, research, approvals, and API-connected workflows.

Dependable for shared operational files when folder ownership and access boundaries are designed instead of inherited accidentally.Read the profile →
Field notesOperational workflow

Google Sheets

A flexible collaborative table for quick analysis, tracking, formulas, import/export, and automation handoffs before a dedicated system is necessary.

Still one of the fastest ways to make operational state visible; fragile when formulas, free text, and hidden tabs become production infrastructure.Read the profile →

Selection rules

The rules I use before adding another tool.

Durable operational context that humans and automations can both understand.

  1. 01Name the system of record.
  2. 02Define fields before automating them.
  3. 03Control sharing at the folder or base boundary.
  4. 04Keep change and exception history.