# Project Risk Notes

Date: 2026-06-12
Owner: PMO

## Executive Summary

The Beaver internal demo project is on track for a management review next week, but several risks require attention. The core product loop is demoable: login, files, chat-to-task, task detail, evidence, revision, acceptance, skills, cron, status, and logs. The main risks are demo stability, connector maturity, and clarity of business story.

## Risks

### R1: Demo scope is too broad

- Impact: High
- Probability: Medium
- Signal: The product has many pages: chat, files, tasks, skills, marketplace, agents, MCP, cron, connectors, status, logs.
- Concern: If the demo becomes a feature tour, leadership may not understand the main business value.
- Suggested response: Use one storyline and only show pages that support it.

### R2: Connector demo may be unstable

- Impact: Medium
- Probability: Medium
- Signal: Outlook and external connector paths exist, but live external dependency can fail.
- Concern: A connector failure could distract from the core Agent workspace story.
- Suggested response: Treat connectors as optional. Demo configuration and explain target workflow if live connector is not stable.

### R3: Skill learning flow may be too long for live presentation

- Impact: Medium
- Probability: High
- Signal: Skill candidate, draft, safety, replay evaluation, review, and publish are powerful but require time.
- Concern: Waiting for background learning may break the demo rhythm.
- Suggested response: Show Skills page, explain lifecycle, and use pre-created examples.

### R4: Leadership may ask for ROI

- Impact: High
- Probability: High
- Signal: Management audience cares about adoption, risk, and next investment.
- Concern: Technical progress alone will not answer "why continue?"
- Suggested response: Position first pilots around repeated knowledge work, measurable accepted tasks, revision rounds, and time saved.

### R5: Model output quality can vary

- Impact: Medium
- Probability: Medium
- Signal: Live model generation may be verbose, miss details, or produce uneven structure.
- Concern: Output quality variance may look like product instability.
- Suggested response: Use revision as part of the story: Beaver supports feedback, continuation, and acceptance.

## Management Decisions Needed

1. Confirm the first 2-3 internal pilot workflows.
2. Decide whether the next milestone optimizes for demo polish or pilot readiness.
3. Pick one connector to harden first, preferably the one with the clearest business value.
4. Define what evidence is required before a task can be considered accepted.
