Operations

Operations is the cross-module work hub for Foundaro. It aggregates open tasks, recurring reviews, and weekly plans from every active workspace — People, Launch, Continuity, Partnerships, Capital, Exit — into one consolidated view so you can manage execution without context-switching between modules.

The module is built around the idea that founders are running multiple workspaces in parallel at any given time. Tasks created in a People workspace sit next to tasks from a Partnerships workspace. Reviews for a Launch are surfaced alongside Continuity check-ins. Operations makes this parallel execution legible.

Overview

The Operations overview is the default view. It shows the current state of execution across all your workspaces in real time.

Stat bar — Five key metrics at the top:

• Open tasks — Total tasks that are not done, across all modules.
• Blocked — Tasks with a blocker recorded. Blocked tasks deserve immediate attention because they often block other work downstream.
• Due this week — Tasks with a due date falling in the current week.
• Overdue reviews — Recurring reviews whose next-due date has passed.
• Active modules — Count of workspaces contributing tasks to the view.

Weekly planning — The current week's plan, if one has been set. Shows the theme, top priorities, notes, and a list of the open tasks that were flagged for the week. Create or edit the plan using the Weekly Plan button in the header.

Task list — All tasks across all modules, with three filters: module (scope to one workspace type), task status (all, open, blocked, overdue, due this week, done), and owner. Tasks show the source module, due date, and current status. Click the status badge to cycle status directly from the list.

Task load by module — A breakdown showing how many open tasks are attached to each module type. This is useful for spotting where execution weight is concentrated across your workspaces.

Recurring reviews — Reviews you have set up with a cadence. Each shows the last reviewed date, the cadence, the next due date, and whether it is overdue. Mark a review as done to reset the cadence clock.

Tips:

• Set a weekly plan at the start of each week — it takes two minutes and gives you a clear orientation before you open your first workspace.
• Use the blocked filter first when you open Operations; blocked tasks usually need a decision or a dependency cleared before other work can move.
• The task load stat is useful for spotting imbalance — if one module is holding 80% of open tasks, that workspace probably needs dedicated focus time.
• Overdue reviews are easy to ignore but compound quickly; a review cadence that has slipped rarely self-corrects without deliberate action.

Weekly Planning

The weekly plan is a lightweight planning artifact scoped to the current calendar week. Each plan has a theme (one sentence capturing the week's focus), up to five top priorities, freeform notes, and a list of open tasks selected from across your modules.

Creating a plan — Open the Weekly Plan dialog from the header button. Set the theme, add priorities, and select the tasks you intend to work on this week. Save to publish the plan to the overview.

Editing a plan — The plan for the current week can be edited at any time. Use the Edit Plan button on the overview if priorities shift mid-week.

Week boundary — Each plan is scoped to a specific week starting Monday. A new week creates a blank slate; previous plans are not shown in the current view but remain in the system.

Tips:

• The theme should be short enough to remember — one sentence that captures what the week is about, not a list of projects.
• Top priorities should be outcomes, not tasks. "Close the Series A term sheet review" is a priority. "Send email" is a task.
• Add specific tasks to the plan from the open task list so the plan stays connected to actual work rather than becoming aspirational text.

Tasks

Tasks in Operations are created within individual workspaces (People, Launch, Continuity, etc.) and surfaced here for cross-module visibility. You cannot create a task directly in Operations — tasks are created inside the workspace they belong to — but you can view, filter, and update task status from the Operations view.

Task fields displayed:

• Title — The task name as entered in the source workspace.
• Module — Which workspace type the task belongs to (e.g. People, Launch, Partnerships).
• Due date — When the task is due. Tasks past their due date with a status other than done are treated as overdue.
• Status — Open, in progress, blocked, or done. Click the status badge in Operations to update status without navigating to the source workspace.
• Blocker — If status is blocked, the blocker reason is shown. Clear the blocker by updating the task in its source workspace.

Filters:

• Module filter — Scope the task list to a single workspace type.
• Task filter — Show all tasks, or filter to open, blocked, overdue, due this week, or done.
• Owner filter — Show only tasks assigned to a specific owner.

Tips:

• Updating task status from Operations is the fastest way to keep the board current during a daily check-in without opening each workspace.
• If a task is consistently blocked over multiple days, it usually signals a decision that needs to be escalated rather than waited on.
• Use the "done" filter periodically to review what has been completed and confirm progress is being made.

Recurring Reviews

Recurring reviews are lightweight check-in records with a cadence. Use them to schedule and track any operational rhythm that needs to happen on a repeating basis — weekly pipeline reviews, monthly retrospectives, quarterly strategy checks, or compliance reviews.

Review fields:

• Title — What the review is about (e.g. "Monthly partnership health check").
• Module — Which workspace or domain the review applies to.
• Cadence — How often the review should happen: daily, weekly, fortnightly, monthly, quarterly, or annually.
• Last reviewed — The date when the review was last marked as done.
• Next due — Calculated from last reviewed date plus cadence. If next due has passed, the review is overdue.
• Notes — Freeform notes captured when the review was last completed.

Marking a review done — Click the Mark Reviewed button to log the review as complete. This resets the cadence clock and moves the next due date forward.

Tips:

• Create reviews for rhythms that already exist and are important, not for aspirational habits. An abandoned review cadence creates misleading overdue counts.
• Keep cadences realistic — a weekly review that is never completed is worse than a monthly review that happens reliably.
• Add notes each time you mark a review done so there is a record of what was covered and what follow-up actions were identified.

See also: Automations guide — automatically create Operations tasks from Relationships meetings or flag blocked tasks into Reporting.