Skip to content

error

SUPERSEDED This document has been superseded. See Coda Field List — FounderOS v0.2.3 (Working Formula Fixes) and FounderOS v0.2.3 — Context & Day‑1 Build Checklist (Working Formula Fixes) for the latest schema and formulas. Reference: coda_formula_guide.md.

What Each “Thing” Is

OutcomeTypes A standalone lookup table whose rows (Billable, Pre-Revenue, Learning, Ops) power the dropdowns in Ventures ⟶ Primary Outcome, Projects ⟶ Outcome, and Tasks ⟶ Outcome.
Ventures Your distinct money-engines (Agency, CS50 learning track, SaaS idea, job search, etc.).
Areas Functional buckets (Marketing, Learning, Development) that Projects sit in.
OKRs A table of Objectives + their 1–3 Key Results + progress %, linked conceptually to Ventures/Projects but not required as a hard relation.
Projects Discrete bodies of work (e.g. “Build analytics dashboard,” “Finish CS50 p-set 1,” “Client proposal X”) that live in one Venture + one Area, and inherit or override an Outcome type.
IdeasInbox A rapid-capture table for raw thoughts: “Podcast idea,” “Look into GPT-agent integration,” etc. You later groom rows into Opportunities (or delete/incubate).
Opportunities Your triaged list: scored and enriched versions of Ideas that are candidates to become Projects.
Tasks The atomic action items you time-block and complete. Each Task points to exactly one Project and one Sprint (once scheduled), has its own Outcome, estimate, and context tags.
Sprints Weekly buckets (“2025-W24”) where you group Tasks, set capacity, and check your Billable ≥ 60 % rule.
Resources & Templates Reusable assets (docs, links, checklists). Store them here and link to whatever Venture, Project, or Area they belong under.
+-----------------+ +---------------+ +-------------+ | OutcomeTypes |<──┐ | Ventures | ┌──>| Projects | | (lookup table) | └───| – PrimaryOutcome |–┘ | – Outcome | | – Outcome | | – … | | – … | +-----------------+ +---------------+ +-------------+ ↑ ↓ | +– (reverse lookup: Projects) | +-------------+ +-------------------+ +-------------+ | OKRs | | Areas (Domains) | | Sprints | | (table w/ | | (table) | | (table) | | Objective, | | – Name | | – Sprint ID | | KRs, % ) | | – … | | – Capacity | +-------------+ +-------------------+ +------+------+ ↑ related via Tasks | +----------------+ +-------------------+ | IdeasInbox | | Opportunities | | (table) | | (table) | | – Title | | – Links to Venture| | – Tags (Topic) | | – Scores | +--------+-------+ +--------+----------+ | | | convert to | spawns +──► Projects +──► Tasks | +--------▼----------+ | Tasks | | (table) | | – Project | | – Outcome | | – Role/Context | | – Estimate/Actual | +-------------------+


Workflow Example

Let’s run through capturing and executing a new learning task in your CS50 venture:
Brainstorm / Capture
In IdeasInbox, you jot:
Title
Tags (Topic)
“Finish CS50 P-Set #1”
CS50, Python
There are no rows in this table

Triage into an Opportunity
In your weekly Backlog Grooming, you convert that Idea into an Opportunity. You score it (Impact = 4, Effort = 2) and tag its Venture as CS50 & Core Programming Skills.
Promote to Project
You decide P-Set #1 deserves its own Project row:
Break into Tasks & Schedule
Under that Project, you create 2 Tasks:
During Sprint Planning, you have 20 hr capacity; the Billable floor is 12 hr. You slot these two Learning tasks for 5 hr total into your calendar. Your remaining 15 hr of Billable tasks fill the other blocks.
Execute & Log
As you work, you fill in Actual (hrs) on each Task, switch Status to Doing/Done, and let Coda roll up total Learning vs Billable hrs for the Sprint.
Review & Adjust
When the Sprint starts, the Billable Floor Check warns you if you accidentally dropped below 12 hr of Billable work.
Mid-Sprint, glance at the Venture Dashboard to confirm you’re not over-allocating Learning time relative to runway.
Archive & Learn
Once all Tasks are Done, you mark the Project Completed. You might link a Resource—say, your annotated CS50 notes—to the Project for future reference.



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.