🚀 Visma Apps

← All roles

🧭 Product Owner

Owns product direction and delivery.

What it does — 5 skills

Product discoveryTrack user needs, adoption and roadmap gaps.Delivery readinessWatch launch readiness and defects.Feedback synthesisSummarise user feedback into actionable themes.Positioning & competitive intelWatch positioning and competitor moves.Read Google Drive documentsRead 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.