Board oversight and governance.

What it does — 5 skills

✓ Analyze / read / write board material — Pre-read board materials ahead of every board meeting, and analyse or draft board documents. Learnings from doing this many times: board decks and pre-reads live in Google Drive — find the latest by company name plus "board deck" / "board pack", and verify the document actually belongs to that company before you summarise it (don't grab the most-recently-edited file globally — that's how you end up summarising the wrong company's deck). Turn the pack into decision-ready points: what changed since last meeting, what's materially at risk, and what actually needs a board decision — not a page-by-page recap. Always pair the narrative with the underlying numbers from the data lake so the board reads a claim and its evidence together.✓ Analyze / read / write management reports — Read, analyse and produce monthly management reports. Learned the hard way, and the most important lesson first: a management report is a GOOGLE DRIVE DOCUMENT / PRESENTATION — the one the Managing Director writes their commentary in — NOT just data-lake numbers. So the real skill is (1) FIND the right report in Google Drive: search by company name + "management report", and verify the document actually belongs to that company and month before reading it — don't grab the most-recently-edited file globally (a classic wrong-doc mistake). (2) READ THE ACTUAL DOCUMENT (open the doc/slides, digest the text and any charts) to capture the MD's narrative — what happened, why, what's at risk, and what actions are planned — because that written analysis is the whole point and appears nowhere in the raw numbers. (3) Use the data lake only to CROSS-CHECK the figures, minding its traps: ARR-type metrics live under source "product" (not "financial"), a company-KPI-period is the SUM of component rows (never dedupe — that reads ARR as ~554K instead of ~56M), and the latest month is PROVISIONAL so trust actuals only through the last closed month. Then report BOTH the MD's narrative and the verified numbers — the story and its evidence together.✓ Data lake — Query the financial data warehouse (the "data lake") for ARR, margins, KPIs and trends. Hard-won learnings baked in: the true grain is (unit, source, KPI, year, period, Gr1, R12, reporting-year, date-key) — always SUM the components, never pick one row. NUMERIC values come back as big.js objects, not plain numbers, so a naive value-handler silently yields null — coerce with String(). Never diagnose a shocking swing as "duplicate double-counting": double-counting inflates, while a collapse toward zero is almost always an un-summed component or the provisional latest month. Verify against pfdw before trusting anything surprising. How to run it (the `lake` CLI, plus the analysis tools built on top): • lake explore --company Acubiz — list the KPIs, sources and periods available for a company • lake series ARR --company Acubiz --source product --chart — the ARR time-series (correctly SUMmed), ready to plot • lake growth ARR --company Acubiz — period-over-period and YoY growth • lake forecast ARR --company Acubiz — projection that prefers the forecast value for the provisional month • lake validate --company Acubiz — flag genuine double-loads and mark the provisional latest month • benchmark ARR — compare one KPI across the whole portfolio • portfolio — the fleet-wide KPI snapshot; waterfall / scenario / explain for bridges, what-ifs and drill-downs • lake manual — the deep guide (grain, provisional months, big.js NUMERIC) baked into the tool itself✓ Read Google Drive documents — Read and digest Drive documents — reports, decks, memos, contracts — with the `drive` CLI (read-only, as the connected account). Work agilely: pull snippets, not whole files, and confirm a hit is the right company/topic before quoting it. How to run it (the `drive` CLI): • drive search "Q3 board deck" — find files by name or content • drive find --name "management report" --type docs --since 30d — precise power-search combining filters (--name / --content / --type slides|docs|sheets|pdf / --in <folder> / --owner / --since 7d) • drive grep "ARR churn" --type docs --context 2 — return matching SNIPPETS across files (cheap; not whole files) • drive digest <fileIdOrUrl> — a triage card (structure + preview) before you commit to a full read • drive read <fileIdOrUrl> — print full content (Docs/Sheets/Slides exported as text) • drive map [folder] / drive index [folder] — folder tree / flat cached catalog for navigation • drive sheet tabs <id> ; drive sheet read <id> --tab <name> — Google Sheets as data • slides analyze <deck> — read a deck slide-by-slide (text + md5-cached vision of every image); slides text <deck> for fast text-only Typical flow: search/find the file → digest to confirm it is the right one → grep the specific point, or read / slides for the full content. Summarise into what the reader needs: the decision, the change, the number — with a link back to the source.✓ Risk watch — Surface material risks and strategic concerns proactively.