How I would run delivery for the Operations Unit as GOOSE goals become unit OKRs, costs tighten and AI moves into daily work, built from Lido's public reports, plus a working desk that tracks OKRs, the critical path, RAID, live governance and AI pilots.
Delivery owner for the Operations Unit. Function heads own the content of each goal; this role owns the timeline, the dependencies, the status and the follow-through, and leads the AI rollout inside Operations.
2026 targets were reset in May, spend is tracking below plan, reporting went quarterly, and the 2027 goals and budget cycle is due around year end. Every initiative now needs a metric, an owner and a cost line.
Ops Desk: a live Lido scorecard against plan assumptions, OKRs to initiatives, a computed critical path, RAID, live Snapshot and forum watch, an AI automation intake and a weekly brief that lists what changed.
| Takeaway | What it means for this role |
|---|---|
| Operations already runs the strategy machinery | GOOSE-3, the 2026 grant request and the 2025 final report are published under the Lido Labs Foundation Operations Team. OKR ownership moving to the unit puts the cascade from goals to tracked work on this desk. |
| Cost discipline is the frame | The August update cites dropped hiring plans and deferred spend; break-even at today's cost base needs ETH near $2,500. Projects get judged on capital, time and traction, the test GOOSE-3 set for every initiative. |
| Public reporting is a delivery output | Quarterly financials, H1 and annual GOOSE reports and tokenholder calls all draw on the same milestones. One register of milestones and metric definitions keeps every report consistent. |
| AI adoption has an in-house platform | Wisp, the confidential agent harness owned through Lido Alliance BORG, was first built by contributors for their own privacy needs. Ops workflows with sensitive data are a natural first internal use. |
GOOSE-3 set five goals for 2026 in November 2025. The H1 report (August 2026) scored them in public. That scorecard is the starting point for any Operations OKR set.
| GOOSE-3 goal | 2026 target | H1 2026 position |
|---|---|---|
| Expand the staking ecosystem | 1M ETH in stVaults; stETH ETF access | stVaults at 5,768 ETH; US stETH ETF still in review. Market share 23.93% to 21.18%. |
| Lido Core upgrade | CMv2, SRv3 and ValMart released in 2026 | CMv2, SRv3 and CSMv3 shipped in July. ValMart moved to 2027. |
| Scale new revenue: Lido Earn | $8M ARR by year end | $0.54M ARR at 30 June, with fees partly switched off to drive growth. |
| Vertical expansion and real-world business | Small, success-gated bets | Wisp launched in August; Lido Lend unveiled in October for this quarter. |
| LDO alignment | Automated buybacks (NEST) | Live in August with a revenue threshold and an annual cap. |
Three Cayman foundations serve the DAO: Lido Labs, Lido Ecosystem and Lido Alliance. Contributors work as independent contractors.
2025 spend $39.1M excluding token rewards. 2026 projected near $37.7M, against a $41M baseline request.
Monthly community calls, quarterly tokenholder updates, quarterly financials from 2026, H1 and annual GOOSE reports.
Inferred from public reports and past Lido postings. The H1 report books G&A as Shared Services: legal, finance, DAO operations and shared infrastructure.
| Function | Recurring work (from public postings and reports) | Where a delivery owner helps |
|---|---|---|
| Finance | Budgeting, forecasting, stablecoin and fiat disbursement, reconciliation, quarterly packs for directors and the DAO | Close calendar, report deadlines, cost-line tracking per initiative |
| Legal and compliance | Foundation governance, director and supervisor changes, sanctions and procurement controls | Filing calendar, contract and vendor review queue |
| People | Contractor onboarding and offboarding, compensation, org design, change programmes | Restructure sequencing, access checklists, comms timing |
| IT and security | Device and access policy, SaaS and vendor lifecycle, multisig hygiene under the Ops Multisigs Policy | SaaS consolidation, AI tool approval, access reviews |
| DAO operations | Proposal pipeline, Snapshot and onchain votes, Easy Track motions, reporting threads | Governance dates as dependencies in every plan |
| Strategy and reporting | GOOSE, the grant request, H1 and annual reports | One milestone and metric register feeding all of them |
Peers are converging on the model Lido already runs: a service entity asks the DAO for a budget tied to milestones, then reports against them.
| Protocol | How strategy and budget run | Lesson for Lido Operations |
|---|---|---|
| Aave | "Aave Will Win" (Feb 2026): Labs requests an annual budget plus a milestone tranche; product revenue goes to the DAO | Milestone tranches make delivery dates a funding question |
| Uniswap | UNIfication (Dec 2025): fee switch and burn, Foundation teams fold into Labs, growth budget via a services agreement | Consolidation needs a clear change plan per team |
| Ethena | Foundation-supported committees with a fixed forum then vote cycle | Fixed governance cycles are plannable dependencies |
| EigenLayer | Eigen Labs cut 25% to focus on EigenCloud; Foundation runs incentives through a committee | Focus cuts land better with the portfolio already ranked |
| Lido | GOOSE goals, an annual grant request, H1 and annual reports, quarterly financials since 2026 | The deepest public reporting of the group; the cost-to-revenue gap is the exposure |
Small inconsistencies across Lido's own pages, each with both sources. Each comes from a milestone or metric being restated in a new document. A single register, updated once and quoted everywhere, closes this class of gap.
| Topic | Source A | Source B | Fix |
|---|---|---|---|
| ValMart release | GOOSE-3 (Nov 2025): "ValMart's 2026 release" | H1 report (Aug 2026): "early 2027"; August tokenholder recap: "Q2 2027" | One dated milestone with a change log |
| 2025 spend vs prior year | February recap: "25% below the initial grant request and 10% below 2024", later "41% below" | Final report (Mar 2026): $39.1M, "8% lower than in 2024", total down "13%" | Fixed metric definitions: with or without token rewards |
| NEST parameters | February recap: ETH above $3,000, revenue above $40M, $10M cap | Launch overview (Aug 2026): $40M revenue threshold, $10M cap, no ETH price condition | Note on the older page when parameters change |
| Careers link | lido.fi/careers returns 404 | The live page is lido.fi/opportunities | A redirect |
| JD scope | How I would do it | Detailed in |
|---|---|---|
| End-to-end project management of a cross-functional portfolio | One register: every initiative has an objective, owner, planned start, duration, dependencies, due date and cost line. Status is computed from the schedule, and an owner override keeps the computed reason visible. | §05, demo |
| Drive execution of the new strategic narrative | Cascade each GOOSE goal into unit OKRs with function heads, then into initiatives. Function heads write the content; I hold the timeline, the interfaces between workstreams and the weekly status. | §05 |
| Stakeholder coordination, unblocking dependencies | A dependency map with the critical path, a decisions log with owners and dates, and governance votes tracked as external dependencies. | §05, demo |
| Process optimisation and change management | Rank cost and process changes by saving, risk and effort; sequence them with People and Legal; one comms plan per change, sent before the change lands. | §07 |
| AI transformation in the Operations Unit | Score every recurring workflow, pick the pattern (automate, agent drafts and a human approves, assist, keep human), run four-week shadow pilots with an owner, controls and a measured baseline. | §06, demo |
| Nice to have: scaling OKRs, change frameworks | OKRs with baseline, target and current so cost-down targets score correctly; quarterly reset aligned to the GOOSE reporting dates; ADKAR-style checkpoints for each change. | §05, §07 |
Four layers, one source of truth. Each layer feeds the one above, and the public reports read from the top.
Set by leadership, voted by the DAO. Annual.
Per function, with baseline, target and current. Quarterly.
Owner, dates, dependencies, cost line. Updated weekly.
Scored, linked to the initiative at risk, reviewed weekly.
| Cadence | What happens | Output |
|---|---|---|
| Weekly | Owners update progress and blockers; the schedule recomputes; open decisions go to the right person | Weekly brief: red and amber with reasons, critical path for the next 14 days, decisions needed, what changed |
| Monthly | Ops review with function heads: OKR movement, cost lines against plan, resourcing | Re-plan of slipped items; escalations to leadership |
| Quarterly | OKR scoring and reset, timed to the quarterly financials and tokenholder update | Numbers for the public update, from the register |
| H1 and annual | GOOSE report and the next goals and budget request | Milestone history and metric definitions ready before drafting starts |
Start from the work, then pick the tool. Each recurring workflow gets scored on volume, how rule-bound and structured it is, data sensitivity, error cost and reversibility.
| Pattern | When | Ops examples and controls |
|---|---|---|
| Automate end to end | Structured, rule-bound, low sensitivity, easy to undo | Governance and forum digest for ops leads; contract notice-date reminders. Run log, weekly sample review, kill switch. |
| Agent drafts, human approves | Structured inputs, moderate error cost | Invoice coding to cost centre; budget vs actual commentary; meeting notes to tracker items. A named approver signs off; track the edit rate. |
| Assist only | Unstructured inputs or access-sensitive steps | Onboarding access checklists; policy drafting. Copilot use with a shared prompt library. |
| Keep human | High sensitivity and high error cost | Payroll and fee changes; admin access reviews; signer actions. AI limited to reminders and checklists. |
Sensitive ops data (contributor records, finance, legal) calls for confidential inference. Wisp is Lido's own option; piloting on it also gives Wisp an internal customer and usage data.
An approved-tools list and data classes before the first pilot, agreed with IT, Security and Legal. Pilots wait on the policy; the intake runs in parallel.
Baseline hours and error rate per workflow, four-week shadow run, four weeks live. Hours returned and adoption go into the unit OKRs.
Meet every function head. Collect every live initiative, owner, date and dependency into one register. Agree status rules and the weekly brief format with the Deputy COO. Map the 2027 goals and budget timeline backwards from the DAO vote.
Draft unit OKRs with function heads from the GOOSE goals. Run the AI workflow intake across Operations and agree the approved-tools policy. Start two shadow pilots, one automate and one draft-and-approve.
Monthly ops review running, first quarterly OKR score published internally, pilot results written up with hours returned and error rates, cost initiatives ranked for the next budget request.
A working app. The Lido scorecard and governance watch run on live public data from six sources with a data-health panel; the Operations portfolio is an illustrative Q4 2026 example you can replace or clear. 46 logic tests run in the browser. Edits stay in the browser and export to JSON. Open Ops Desk ↗
| Tab | What it does |
|---|---|
| Overview | Objective progress from key results (cost-down targets score correctly), red, amber and green counts, needs-attention list with reasons. |
| Lido scorecard | Live revenue run-rate against the $40M NEST threshold, ETH against the planning price and break-even, stETH APR against the 2.93% plan, staked ETH and treasury, each with its source and change since a dated baseline. GOOSE-3 goals with H1 position, and every published date for each milestone. |
| Portfolio | Editable initiatives with objective, owner, dates, dependencies and status override; filters and CSV. |
| Critical path | Forward and backward pass over dependencies; a late vendor inventory visibly pushes the expense plan and the H2 report. |
| RAID log | Risks, assumptions, issues and decisions scored and linked to the initiative they threaten. |
| Governance watch | Live Lido Snapshot votes and research forum threads, ops-relevant ones flagged and linked to initiatives; one click adds a vote to RAID. |
| AI intake | Workflow scoring, operating pattern, controls and a copyable pilot charter. |
| Weekly brief | Markdown brief generated from the data; "mark as sent" saves a baseline so the next brief lists changes. Optional five-line AI summary with the viewer's own key. |
Public sources only, read on 18 October 2026 (public job posting, 2026). The Operations Unit scope is inferred from Lido's reports and past public postings. The demo is my own prototype built for this application and holds no Lido internal data.
Strategy: GOOSE-3 · 2026 grant request · GOOSE-2025 final report
Reporting: H1 2026 report · reporting thread
Updates: Feb 2026 · May 2026 · Aug 2026 · NEST overview
Governance: Ops Multisigs Policy 3.0 · Wisp ownership · Snapshot
Peers: Uniswap UNIfication · Ethena risk committee · Eigen incentives
Independent homework for the Lido Strategic Project Manager, Operations role · 2026 · edwardtay.com