Dominic ArvenholtChief Product Officer

Speaking & conversations

Start with the customer task the demonstration did not complete.

01

The person missing from the product demonstration

Proposed 45-minute product case workshop · Business-banking product, operations and design teams

I would introduce the fictional account-opening prototype I approved in 2004, then ask participants whose work the demonstration leaves out. The pilot’s 120 businesses included fifty-six with two-person internal approval mandates, and thirty-eight of those were blocked by the single-approver flow. The workshop would explore pending approval, decline, retry and an assisted route as parts of the product rather than inconvenient exceptions. I would retain my responsibility for favouring the easy path and explain why the correction did not establish that every blocked business subsequently completed opening. Participants would work with an invented journey, without sharing customer applications or actual bank procedures. The proposed discussion would not prescribe a universal approval rule or suggest bypassing relevant checks. It claims no delivered event. Its purpose is to help a team define completion through the customer’s real task, including necessary participants who do not act at the same time.

02

When declining the new option is a valid product outcome

Proposed 35-minute keynote with merchant-service discussion · Payments, commercial and product leadership groups

I would examine the fictional accelerated-settlement proposal at Serravon, where research found different merchant needs and the commercial sponsor preferred paid default inclusion. The sixty-merchant pilot eventually recorded twenty-two choosing acceleration and thirty-eight retaining standard settlement. The proposed session would ask what successful choice means before adoption becomes the dominant measure. Participants would consider how to keep timing, price and conditions visible while preserving a credible standard route. I would distinguish product scope from treasury and operating decisions about what can actually be delivered. The example would contain no live offer, financial recommendation or universal settlement promise. It is a programme concept with no prior audience or appearance claimed. The intended contribution is a more precise discussion of whom an optional service serves, why a customer might reasonably decline it and how commercial ambition can be assessed without making every non-selection look like a product failure.

03

The retirement date is not the whole exit plan

Proposed 50-minute transition case conversation · Banking portfolio, platform and customer-service leaders

I would use the fictional invoicing retirement to examine what a customer needs in order to leave a feature usefully. Of fourteen hundred businesses, 960 could use the standard export while 440 required additional history fields. The discussion would follow the choice of an assisted extension and the later position in which 360 of that group had migrated while eighty remained supported. I would ask participants to consider the platform sponsor’s concern about continuing cost as well as the customer dependency. The session would distinguish a managed exception from an indefinite promise and avoid inventing a legal deadline or a completed saving. Supplied material would be fictional, with no actual customer records requested. This is a proposed event rather than a delivery credit. Its purpose would be to make the remaining work part of the retirement account, so a clear calendar cannot substitute for an exit the affected businesses can actually use.

04

The better prototype that still was not ready to be called resolved

Proposed 40-minute evidence-led product briefing · Product executives, research teams and board-information colleagues

I would present two fictional tests of a business cash-view prototype. Sixty-seven of 240 owners initially interpreted forecast receipts as spendable funds; after a redesign, fourteen of 180 still did so. The session would examine why an improved result can support further work rather than automatic release. I would discuss the decision to separate available balance from forecast information and remove a combined headline despite pressure for a smaller explanatory note. Participants would consider the difference between technical wording and the meaning users take from the whole presentation. The format would provide no banking advice, actual account information or claim of a full launch. It is an unpublished speaking proposal. The intended value is to help leaders keep unresolved understanding visible, assess the evidence with the relevant product and control owners, and resist turning a more favourable comparison into a statement that the underlying problem has disappeared. Participants would identify the next evidence needed before recommending a wider release.

Short speaker biography

Dominic Arvenholt is the fictional CPO of Erlavane Bank in Australia. His thirty-two-year career moves from banking into merchant payments and back. Proposed sessions examine product scope, multi-person approval, optional services and retirement. The demonstration retains an owned design error and claims no delivered event or statutory-director appointment.

Standard speaker biography

Dominic Arvenholt is an invented Australian banking product leader based in Sydney. He leads 168 product colleagues through seven direct reports at the fictional Erlavane Bank, with A$34 million delegated FY 2026–27 function expense. His career began in March 1994, moved into merchant-payment products in April 2007 and returned to banking in July 2014. He became CPO in July 2020. Proposed discussions examine the participants, choices and customer dependencies behind a product promise. The narrative retains an opening-flow mistake and an incomplete retirement rather than inventing finished successes. His exposure to boards is executive, and no actual speaking engagement or statutory service is asserted.

Extended speaker biography

Dominic Arvenholt is a fictional Chief Product Officer whose work examines whether business-banking propositions remain understandable beyond their easiest customer path. Based in Sydney at the invented Erlavane Bank, he leads 168 product colleagues through seven direct reports with A$34 million delegated function expense for FY 2026–27. Bank assets of A$74 billion in FY 2025–26 and current employment of 4300 describe the institution around the role.

He began in business-product analysis in March 1994 after economics study, became a product manager in July 2000 and moved to merchant products at Serravon Payments in April 2007. He returned to Erlavane in July 2014 and became CPO in July 2020. His cases include a single-approver design error, an accelerated-settlement option kept optional, a narrower business bundle and an invoicing transition with customers still supported at review.

The proposed programme uses invented product decisions and no actual customer applications or restricted commercial material. Lending, risk, compliance, treasury, operations, engineering, legal and cybersecurity responsibilities remain separately owned. His board experience is executive presentation, with no statutory appointment claimed. No delivered event or audience history is asserted. A real speaker profile would require verified roles, permission for examples and an accurate distinction between future programme ideas and completed appearances.

An invitation

Contact

I would consider a discussion about product scope, business-customer journeys or a prospective first-board contribution in banking or payments. Employer agreement, preparation, relationships and actual workload would need assessment. This fictional profile supplies no banking product or financial advice. An initial message should describe the product question without attaching customer records, application details or restricted commercial terms.

Open to
  • Board appointments
  • Speaking invitations

office@dominicarvenholt.example