I learned to ask what the easy demonstration had left for the customer to solve.

I began in business-product analysis at Erlavane Bank in March 1994, after completing economics at the fictional Kelvethan College in December 1993. The first work was close to the questions raised by business customers: which account did they need, who could act for the business and what happened when the standard journey did not fit? I worked within a ten-person analytical group with no direct reports or spending delegation. I learned to listen for the exception behind a seemingly simple request.

Becoming a product manager in July 2000 gave me responsibility for choosing which of those questions the product would answer. By FY 2005–06 I led twenty-four colleagues through three direct reports with A$2.4 million annual function expense. I did not make lending decisions or set every condition governing an account. The role required collaboration with operations, engineering, risk and legal colleagues, especially where a smooth customer journey depended on responsibilities the product team could not remove by design.

I learned that too late in a 2004 opening prototype. I had favoured a short single-approver path. Of 120 pilot businesses, fifty-six required two internal approvers under their own mandates, and thirty-eight of those were blocked by the flow. Owen Bellarven challenged the apparent simplicity. A$420000 supported rework around a pending second approval, decline, retry and an assisted route. We did not bypass bank checks or claim that every business needed two approvers. I had mistaken the easiest path through the screen for the product’s complete job.

In April 2007 I left the bank to lead merchant products at Serravon Payments. That move made choice more tangible. A proposed accelerated-settlement service appealed to some merchants but not all, while the commercial team preferred it as a paid default. Research with three hundred merchants found 120 interested in acceleration and 180 for whom standard settlement was adequate. We chose an explicit option with its conditions visible. In a sixty-merchant pilot, twenty-two selected it and thirty-eight stayed with the standard service. The product’s usefulness did not require universal adoption.

I returned to Erlavane as director of business products in July 2014. Ending a legacy invoicing feature then tested a different responsibility. Of fourteen hundred business users, 960 could use the standard export while 440 needed additional history fields. I supported an assisted extension instead of one uniform ninety-day exit. At the later review, 360 of the extended group had migrated and eighty remained supported. I could not honestly describe the closure as complete, but the transition now reflected the customers’ actual dependency.

Since July 2020 I have served as CPO. I lead 168 product colleagues through seven direct reports with A$34 million delegated FY 2026–27 expense. The bank’s A$74 billion assets and 4300 employees are separate institutional scale. Lending, risk, compliance, treasury, operations, engineering, legal and cybersecurity retain their own owners. The CPO role brought responsibility for presenting product decisions to the board from July 2020. The fictional chronology includes no statutory seat, and my earlier director title described employment responsibility.

Recent work has challenged both product breadth and apparent clarity. We reduced a proposed forty-feature business bundle to a coherent account, payments and cash-flow export core, leaving credit as a separate option subject to its own assessment. Another prototype showed that sixty-seven of 240 business owners interpreted forecast receipts as spendable funds. Separating the display reduced that misunderstanding in a new 180-person test, but fourteen still misread it. We kept revising rather than use the better result as evidence that the problem had disappeared.

I want product leadership to retain those unfinished or narrower outcomes. The team’s task is not always to add a feature, maximise uptake or announce a completed launch. Sometimes it is to preserve a choice, carry the cost of an exit or recognise that a customer still misunderstands the promise. I would bring that perspective to a possible first board contribution with preparation and a realistic assessment of fit. Every person and event here is invented. The record illustrates a product career whose authority comes from explaining the decisions and consequences, including the ones that made the final proposition smaller than the original pitch.