Brendan Davies Product / Operations / Systems

The invisible work,
made visible.

The Desk ↓

The enquiry path, drawn on the glass.

Patterns seen before.

  • Shared inboxQueue ownership
  • UnderwritingRisk and decision state
  • Enterprise SaaSKnowledge and handoff drift
  • StudioScope and evidence

The technology changed. The work still needs a visible state, a next action and someone accountable for it.

01 / The Desk

The Desk

Commercial Operations & Internal Tooling

Internal tools are products.

A worked example, not a former employer system.

One enquiry: assist classifies and drafts → a named owner checks the draft → action → audit record.

Rejected: “Automatically send every generated reply.” Generation is not ownership.

Measurement design: time to first owner touch, queue age and unowned items. Sends without owner approval: target zero.

One enquiry moves through assist, identity, enrichment and route to a named owner — then reply and audit.

Path: Enquiry → Assist → Identify → Enrich → Route → Owner → Reply / Action → Audit

Enquiry Assist Identify Enrich Route Review Owner Reply / Action Audit

Ownership

  1. Assist suggests. Assist is not owner.
  2. Owner remains accountable.
  3. Audit keeps the action and its reason inspectable.

Own what creates advantage or needs direct control. Buy or partner where a specialist carries commodity complexity better. Transfer exposure when a known premium beats uncertain downside.

Build / buy / prompt

Prompt. Extraction, classification, drafting, anomaly suggestions and owner routing. The model suggests; the consequential write remains owned.

Buy. Payment rails, identity-verification vendors, CRM and commodity infrastructure. Use mature external rails where ownership adds unnecessary risk or maintenance.

Build. Workflow orchestration, audit history, routing, ownership, custom policy, deterministic state boundaries and data contracts. Build where the operating model is the product.

Challenge before commit.

Different models are useful because they disagree.

I start with the real problem, constraints and desired outcome. Models can explore alternatives; a critic challenges assumptions and looks for failure modes. I cross-review their answers, then use a synthesis pass to turn useful disagreement into one candidate plan.

Tests, source evidence or human review check that plan where applicable. Providers can change. I remain responsible for the decision and the commit, especially when a change carries consequences.

Assist suggests. Evidence challenges. A person commits.

Blueprint → See the same operating principles applied to a two-sided marketplace.

Agents → memory, permissions and owner gates.

Multiple perspectives. One accountable decision. Frame the problem, constraints and owner. Explorer, critic and alternative perspectives cross-challenge each other. A synthesis records assumptions and failure modes. Tests, evidence and review inform the owner's decision before commit. There is no majority vote or autonomous commit. Problem + desired outcome Constraints + owner ExplorerCriticAlternative Cross-challenge Synthesis Assumptions + failure modes Test / evidence / review Owner decision → commit
Multiple perspectives. One accountable decision.

Close

Looking for someone who can connect the whole system?

Best used where product, operations and delivery are the same conversation. LinkedIn is the direct route.

Privacy: this static site uses no analytics, tracking cookies, forms or third-party fonts.