Product Operations

The machinery behind a growing product org: a charter and operating model, tool stack and templates, intake, review and planning rhythms, trustworthy product data and the specialist work of scaling product ops.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Operations, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Product Operations

Building the systems, templates, tooling and data access that let product managers work consistently across a growing product organisation.

  1. Product operations charter and remit
  2. Product manager time audit and pain-point survey
  3. Product tool stack inventory and cost map
  4. Product ownership map of every surface
  5. One-page product operating model
  6. Product ops request intake and queue
  7. Product documentation home and folder structure
  8. Product glossary and naming conventions
  9. Product ops baseline measures
  10. Weekly product ops intake triage
  11. Monthly product review pack production
  12. Quarterly planning cycle run
  13. Product tool licence and access hygiene
  14. Product template library upkeep
  15. Product data quality and dashboard checks
  16. Product decision log upkeep
  17. Research participant panel and consent records
  18. Cross-team release calendar upkeep
  19. Monthly process and tooling changelog for PMs
  20. Quarterly process retrospective with product managers
  21. Product data model and SQL basics for product ops
  22. Change management for process rollouts
  23. Facilitating planning and prioritisation workshops
  24. Work tracker administration skills
  25. Studying how other companies run product ops
  26. Writing process documentation people use
  27. No-code automation between product tools
  28. Roadmap and planning tool consolidation
  29. Standard product artefact template set
  30. Field request routing from sales and support
  31. Product manager meeting load audit
  32. Automated status reporting from the work tracker
  33. Product metric dictionary
  34. Product tooling security and data retention review
  35. Retiring stale processes and duplicate documents
  36. Annual product planning season preparation
  37. Product organisation offsite
  38. New product tool rollout day
  39. Product ops first-year review
  40. Product org reorganisation transition
  41. Hiring the first dedicated product ops person
  42. Product ops as a side role for a product manager
  43. New product manager onboarding programme
  44. Merging product orgs after an acquisition
  45. Product rituals across time zones
  46. Federated product ops across business units
  47. Product ops maturity assessment and three-year plan
  48. PM capacity and coverage model
  49. Guidelines for AI assistants in product workflows
  50. Product ops team structure and career ladder

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Product operations charter and remit

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Nothing sinks product ops faster than nobody agreeing what it is for, so the role drifts into note-taking, tool admin and whatever the loudest product manager asks.

First tasks

  • Write down the three biggest problems product managers raised last quarter
  • Draft an in-scope and out-of-scope list for product ops on one page
  • Review the draft charter with the head of product and two product managers
  • Publish the signed-off charter in the product documentation space

Product manager time audit and pain-point survey

Before building any process, find out where product managers' weeks actually go. A two-week time sample plus a short survey usually shows the same pattern: hours lost chasing data, rebuilding status decks and hunting for the latest version of a document, and those findings become the first product ops backlog.

First tasks

  • Draft a ten-question survey on time sinks, tools and missing information
  • Ask five product managers to log their time in half-day blocks for two weeks
  • Ask the agent to group free-text survey answers into themes with counts
  • Rank the top five pain points by hours lost and share the summary

Product tool stack inventory and cost map

Growing product orgs collect tools by accident: two roadmapping apps, three survey tools and a whiteboard licence nobody remembers buying. A single inventory with owner, cost, renewal date, active users and what each tool is the source of truth for is the starting point for every later consolidation and access decision.

First tasks

  • Ask finance for a list of software spend coded to the product department
  • Survey PMs and designers for tools paid on team or personal cards
  • Pull active user counts from each tool's admin console
  • Mark overlapping tools and flag renewals due in the next six months

Make it yours.

Install Product Operations, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.