Objectives and key results
Needs attention
Lido scorecard
Live public metrics set against the 2026 planning assumptions, the GOOSE-3 goals with their H1 position, and every published date for each milestone. Each number links to its source; the baseline is a frozen snapshot from 17 Oct 2026 UTC.
GOOSE-3 goals, H1 2026 position
Milestone register every published date, oldest first
Data health
| Source | Status | Time | Used for |
|---|
All sources are public and keyless and are read straight from this browser. The NEST line is indicative: it annualises DefiLlama's trailing 30-day revenue, while the contract uses its own measurement window. Treasury is the DefiLlama-tracked non-LDO balance; Lido's own reports include more.
Portfolio
Every initiative maps to an objective. Status colour is computed from the schedule; an owner can override it and the computed reason stays visible.
| Initiative | Owner | Objective | Progress | Forecast | Due | Status and reason |
|---|
Critical path
Forward pass from planned starts and dependencies, backward pass from the portfolio end. A late predecessor pushes everything behind it; started items forecast from today using the work left.
| Initiative | Forecast start | Forecast finish | Float | Slip | Depends on |
|---|
RAID log
Risks, assumptions, issues and decisions, scored probability times impact and linked to the initiative they threaten. Overdue reviews surface in the brief.
| Item | Type | Score | Owner | Threatens | Review | Status |
|---|
Governance watch
Live from Lido's Snapshot space and research forum. Ops-relevant items (budget, expenses, audits, entities, contributors) are flagged and linked to portfolio initiatives by keyword, so a vote that moves the budget shows up as a dependency.
Snapshot votes lido-snapshot.eth
Research forum research.lido.fi, latest
AI automation intake
Score each ops workflow on volume, how rule-bound and structured it is, and what a mistake costs. The desk picks an operating pattern, lists the controls and writes a pilot charter. Sensitive, costly, hard-to-undo work stays with a person.
| Workflow | Owner | h/month | Fit | Risk | Pattern | h returned |
|---|
Weekly brief
Generated from the portfolio, RAID log and governance watch. "Mark as sent" saves a baseline, so next week's brief lists what changed: status moves, forecast slips, progress jumps.
Optional: AI exec summary
Turns the brief into a five-line update for leadership. Uses your own OpenRouter key, sent from this browser straight to openrouter.ai and kept only in memory. The model is told to use only facts in the brief.
What this is
A working desk for the delivery side of a strategy rollout: objectives and key results, the initiatives behind them, the schedule that decides which ones are late, the risks and decisions in flight, the governance calendar an Operations unit at a DAO-governed protocol must plan around, and a structured way to pick AI automation pilots.
Built by Edward Tay for an application to Lido's Strategic Project Manager, Operations role. It is not Lido software and holds no Lido internal data. The example portfolio is invented; Governance watch reads public Snapshot and forum data live.
How the numbers work
- Key result progress: share of the distance from baseline to target, so cost-down targets work too.
- Schedule: critical path method. Planned start and finish-to-start dependencies set the earliest start; started items forecast from the as-of date with the unfinished share of their duration.
- Status: red when blocked or forecast past due, amber with under 3 days of buffer or 20+ points behind elapsed time, green otherwise. Owner overrides keep the computed reason.
- Lido scorecard: stETH APR (Lido API, 7-day average), staked ETH and holders (Lido API), protocol revenue and treasury (DefiLlama), ETH and LDO prices (CoinGecko). Compared with the 2026 grant request assumptions and a dated baseline.
- AI intake: fit = rules + structure; risk = sensitivity + error cost + irreversibility. High sensitivity with high error cost always stays human.
Data and privacy
Everything you type stays in this browser (localStorage). Export writes a JSON file you can import later or share. Network calls go to hub.snapshot.org and research.lido.fi (through this site's cache when needed), eth-api.lido.fi, api.llama.fi and api.coingecko.com for public data, and to openrouter.ai only when you press Draft summary with your own key.