BotCurrent↗
← Back to examples

Vendor report

Flag functional overload after roadmap changes

Roadmap changes can overcommit a product function even when each project’s individual allocation appears reasonable.

Read original source
Suggested result

A proposed function-level utilization table with input references, denominators and unresolved allocation gaps.

What you need: Source-named agent: Notion Custom Agents (Morning Brew Cappy). Suggested inputs: Project allocation copy; Capacity assumptions; Aggregation rules. Anonymized or role-level exports. A separate calculated review artifact. Workflow costs and current compatibility remain unverified.

Proposed: the planning owner confirms capacity definitions and reviews flagged teams. Staff allocation, deadlines, hiring decisions and communications require authorized human decisions.

Vendor report. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Project allocation copy

    Owner

    Portfolio owner

    Minimum scope

    Function, period and approved demand units

    Quality check

    Exclude duplicate or superseded entries.

  2. Name

    Capacity assumptions

    Owner

    Planning lead

    Minimum scope

    Team-level available units by period

    Quality check

    State leave, holidays and shared capacity treatment.

  3. Name

    Aggregation rules

    Owner

    Planning lead

    Minimum scope

    Units, denominators and overload threshold

    Quality check

    Do not mix percentages with hours.

Access and setup — proposed or unknown

Proposed minimum

  1. Anonymized or role-level exports.

  2. A separate calculated review artifact.

Compatibility unknowns

  1. Unknown: current schema, trigger behavior and source calculation method.

External actions requiring approval

  1. Roadmap edits, staffing changes, notifications and publication of team workload.

Detailed steps and output format

At a glance

Suggested result
A proposed function-level utilization table with input references, denominators and unresolved allocation gaps.Suggested; untested.
Tool
Notion Custom Agents (Morning Brew Cappy)Source-named; check current access.
Suggested inputs
Project allocation copy; Capacity assumptions; Aggregation rulesProposed; access notes below.
Human review
Proposed: the planning owner confirms capacity definitions and reviews flagged teams. Staff allocation, deadlines, hiring decisions and communications require authorized human…
Read full note

Proposed: the planning owner confirms capacity definitions and reviews flagged teams. Staff allocation, deadlines, hiring decisions and communications require authorized human decisions.

Suggested boundaries; source approvals below.
Setup notes
Anonymized or role-level exports. A separate calculated review artifact.Guide notes; proposed setup untested.
Cost
Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth
Source-linked example · suggestions untestedDepth does not establish successful execution.
Check source evidence and limits ↓

Function and scope

Operations, Analytics · Ongoing responsibility

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Roadmap changes can overcommit a product function even when each project’s individual allocation appears reasonable.

Suggested task · untested

Proposed: aggregate approved project allocations over a shared planning period and expose overload or missing assumptions for a planning owner.

What you could produce

A proposed function-level utilization table with input references, denominators and unresolved allocation gaps.

Where these suggestions come from
  • Core problem: Our suggestion; no result reported by the source
  • Agent job: Our suggestion; no result reported by the source
  • Expected output: Our suggestion; no result reported by the source
  • Relevant job roles: Our suggestion; no result reported by the source
  • Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A roadmap may contain demand in several places while capacity assumptions live elsewhere. Rebuilding the totals after every change makes inconsistent periods easy to miss.

  2. A refreshable review could expose conflicting assumptions before planning decisions are made, while leaving priorities and staffing choices with people.

Why an agent / simpler alternative

Useful judgment

Clarifying inconsistent allocation descriptions and identifying rows that cannot be combined safely. Arithmetic should use explicit, reproducible rules.

Simpler alternative

Prefer formulas or a dashboard for stable structured allocations; add an agent only when contextual review earns its complexity.

Unsuitable when

Inputs require individual performance scoring or the system would automatically change assignments, deadlines or employment outcomes.

Expected deliverable and review checks

Proposed artifact

Function-period roll-up with traceable calculations.

Critical checks

  1. Demand and capacity use the same period and unit.

  2. Shared allocations appear once.

  3. Unknown capacity is not silently treated as zero or full availability.

Missing output evidence

Unknown: no customer calculation workbook or runnable configuration inspected.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Four fictional functions, one duplicate allocation, mixed planning periods and one missing denominator; compare offline output with hand-checked totals.

Acceptance checks

  1. Remove only the identified duplicate.

  2. Keep periods separate.

  3. Flag missing capacity.

Stop conditions

  1. Any personnel judgment, silent assumption or live reassignment.

Tasks: Planning & operations

Useful for: Product managerProject managerOperations manager

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Notion Custom Agents (Morning Brew Cappy)Independent testing: No
Failure handling, costs and limits

Failure signals and proposed responses

  1. Signal

    An overload vanishes after a date-format change.

    Why it matters

    Period grouping may have lost demand.

    Proposed response

    Reconcile source rows to grouped totals.

  2. Signal

    A function has no recorded capacity.

    Why it matters

    A percentage would be misleading.

    Proposed response

    Return an unresolved denominator instead.

Effort and cost — unknown

Setup work

  1. Agree units, periods and inclusion rules.

Ongoing review

  1. Reconcile changed allocations and capacity assumptions.

Unknowns

  1. Unknown: integration cost and benefit over formulas.

Limits

  1. Utilization reflects supplied assumptions, not measured productivity.

  2. No automatic rebalancing or outcome improvement is claimed.

Full source evidence

Vendor report · Tool workflows

Original task title: Flag functional overload after roadmap changes

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://www.notion.com/customers/morning-brew ↗

Attributed to: Notion, reporting Morning Brew and product leader Emily Diamond

Vendor report
Original action type
tool_action
What the source reports
Morning Brew reports that Cappy reads roadmap project allocations, computes utilization by product function and flags overload, running on project changes or on request.
Source outcome limits
A reported planning aid, not proof of true available capacity or improved delivery. It does not establish a staffing recommendation; claimed speed and overload figures are omitted.
Evidence attribution caveat
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Source approval description
People retain decisions about redistributing work. Exact execution permissions and approval of writes are not specified.
Named tools
Notion Roadmap; Notion Custom Agents; Cappy.
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: agree the capacity period, leave and holiday treatment, units and team-level privacy boundaries for Canadian teams; avoid employee performance scoring.
Recommended approval boundaries
Proposed: the planning owner confirms capacity definitions and reviews flagged teams. Staff allocation, deadlines, hiring decisions and communications require authorized human decisions.