How Project Management Works in Saberra

Most teams do not fail at project management because they lack a tool. They fail because every tool demands a discipline nobody has time to practice: statuses go stale, budgets drift from reality, and the plan stops being true. Saberra takes the opposite approach - the system keeps itself current, because it is wired into the same institutional memory that already captures your meetings and emails.

One pool of work, three questions

Every piece of work in the hub answers three questions:

• Owner - who is doing it (a real Profile, not a name in a text box)
• Project - what outcome it serves
• Lane - which business function it belongs to

Because every task carries all three, you never maintain separate lists. You view the same pool through different lenses: one project's full picture, one person's plate, one business function across every project.

Lanes

A Lane is a business function, not a project. The set is fixed:

1. Project Management & Operations
2. Legal & Compliance
3. Finance & Accounting
4. Sales
5. Marketing & Brand
6. Capital & Investor Relations
7. Land & Facilities
8. Hospitality & Service

A lane is a filter, not a folder. A legal task under a construction project keeps Lane = Legal & Compliance, so it appears in the construction project AND in the Legal lane view. Ask Sera for "everything in the Legal lane" and you get the true cross-project picture.

Structure: projects, tasks, subtasks, dependencies

• Projects are named outcomes - each carries a status, lane, target date, and its budget totals.
• Tasks point at their project and can nest under a parent task (turn on Notion's Sub-items display to see the expandable tree).
• Blocked By / Blocking links tasks into a real dependency chain. A blocked task carries a plain-language Blocker Note saying what it waits on.
• Gated By ties a task to a decision record - work that must not proceed until something is formally decided.
• Step Order is the sequencing number: the ordered "do this next" list. It is deliberately sparse - only consciously sequenced work carries one.

How work gets into the system

Three ways, in order of how often they happen:

1. Automatically. Sera extracts tasks (with owner, project, lane, and dependency hints) from the meetings and emails your hub already captures. This is the main path - the system stays current because your communication feeds it.
2. By asking Sera. "Create a task for the well pump repair under the Infrastructure project, Ky owns it." Sera proposes, you confirm, it writes - and it will surface an existing record instead of creating a duplicate.
3. Directly in Notion. Everything is a normal Notion database. People who like working in Notion can filter, group, and edit there; the views (By Lane, By Person, Start Cadence, Budget Watch) are stock views over the same data.

Working it through Sera

Ask in plain language - the answers come from the live records, never from memory:

• "What is blocked right now, and who unblocks it?"
• "What is on Maria's plate this week?"
• "What should I work on next?" (the Step Order sequence)
• "Move the fence repair to the Land & Facilities lane."
• "Draw the timeline for the Infrastructure project." (a Gantt-style chart of the dated tasks, rendered in the conversation)

Every Monday the hub can send a weekly project status email: each project's status, budget position, open and blocked work - built from the records, skipped entirely when there is nothing to report.

The principle

Sera proposes, humans decide. Records carry their evidence, money figures are never estimated, and nothing gets silently invented or silently dropped. The discipline is in the system so it does not have to be in your habits.

Key points

One pool of work, viewed through lenses: every task carries an Owner (who), a Project (what outcome), and a Lane (which business function). Lanes are a fixed set of eight business functions and act as filters, not folders - a legal task under a construction project shows in both the project and the Legal lane. Tasks nest under parent tasks, can block each other (Blocked By / Blocking), and can be gated on a decision. The Step Order number drives the "do this next" sequence. Ask Sera anything: "what is blocked?", "what is on my plate?", "budget status of X" - answers come from the live records. New work arrives automatically from meetings and emails; you can also ask Sera to create tasks and projects, and it will refuse to create duplicates.