Key concepts
In Parallel works because it uses a small set of concepts consistently. Once these click, everything else — meetings, reports, decisions, tasks — feels obvious.
Execution Scopes
An Execution Scope is the unit of accountability in In Parallel. Everything lives inside a scope: the plan, the meetings, the goals, the decisions.
A scope represents one area you're accountable for. Common scope types:
Type | What it covers |
Team | Weekly execution for a standing team — priorities, tasks, ongoing decisions |
Project | A time-bound initiative with a defined outcome and delivery sequence |
Program | Multiple workstreams with shared priorities, risks, and dependencies |
Operations | A recurring operational area — incidents, processes, rhythm governance |
Account | A customer or partner relationship — commitments, delivery, alignment |
Transformation | A strategic change initiative — decisions, ownership, progress against intent |
Scopes exist to keep the system legible: no "one giant plan for everything", explicit ownership, and meetings connected to the right work.
Is your scope the right size?
A scope is right when… | A scope is too broad when… |
One person is accountable for outcomes | Priorities can't be ranked because everything matters |
Decisions happen regularly, usually via a recurring meeting | Updates feel noisy or contradictory |
Priorities can be ranked without debate | Multiple unrelated cadences are mixed together |
If a scope feels noisy, split by ownership or cadence.
The Living Execution Plan
Each scope has one Living Execution Plan — the current truth surface for everything happening in that scope.
A plan typically includes:
Goals and commitments
Ranked priorities
Tasks and milestones
Risks and dependencies
Explicit ownership
Recent changes
What makes it "living": the plan updates from meetings (where decisions are made), connected system changes (where progress shows up), and your review and confirmation (so trust stays high). This is why In Parallel isn't a document you rewrite — it's a system that keeps execution reality coherent as reality moves.
Execution signals
In Parallel treats meetings as execution events. When the Transcriber joins a connected recurring meeting, it captures execution signals — the meaningful information that changes the plan:
Decisions made
Actions assigned with ownership
Risks surfaced
Commitments given
Ownership changes
These aren't stored as meeting notes. They're interpreted as signals that drive the post-meeting report and plan updates.
Execution Memory
In Parallel doesn't just process meeting signals — it accumulates them into a persistent, structured record called Execution Memory. This is the foundation the AI draws on when surfacing pre-reads, detecting drift, and proposing plan updates.
Seven categories of information are tracked:
Category | What it captures |
Goals and intent | What you're trying to achieve, and why |
Decisions | What was resolved, by whom, and what changed |
Risks and obstacles | Threats and blockers surfaced across meetings |
Commitments | Actions and obligations made by team members |
Ownership changes | When responsibility moves from one person to another |
Learnings | Insights and retrospective observations |
Skills in the room | Expertise and context participants bring |
Each Routine Cycle adds to this record. The longer In Parallel runs on a scope, the richer the context it can draw on — and the less manual effort each meeting requires.
Routines and Routine Cycles
When you connect a recurring meeting to a scope, In Parallel creates a Routine — a structured series that tracks context from each session.
Each meeting occurrence is a Routine Cycle. Context compounds across cycles: the pre-read for cycle 5 draws on what happened in cycles 1–4. This compounding is what separates In Parallel from a meeting notes tool — the system builds a continuously improving picture of your execution reality.
How these concepts fit together
The simplest mental model:
Scope — what we're accountable for
Plan — what execution reality looks like right now
Meeting — where execution reality changes
Report — what we captured and what we're proposing
Execution Memory — the accumulating record that makes context compound across every Routine Cycle
When you use the system consistently, clarity compounds — meetings start from shared reality, decisions stay visible, and the plan stays trustworthy without manual effort.
Related