Phoebe Ellerwick

Phoebe Ellerwick · Chief Product Officer · Australia

Each wider product remit brought another part of ordinary use into view.

Jul 2021 — Present

Chief Product Officer

Belvarel Retail

Sector
Own-brand housewares and household product retail
Ownership
Private retailer; founder-family interests 55% and institutional investors 45%
Company scale
A$1.85 billion company revenue in FY 2025–26
Employees
4200 company employees at October 2026
Geography
Sydney headquarters; 180 Australian stores with operations including Melbourne, Brisbane and Perth
Reporting to
Chief Executive Officer
Team
138 product colleagues through six direct reports at October 2026
Financial scope
A$28.4 million delegated FY 2026–27 product-function expense; buying commitments, store operations and quality assurance separately accountable

Mandate

Define household product choices using observed space, task and routine, with the limits of the proposition stated clearly.

Outcomes

  • Selected 18 storage formats around 3 lid footprints after studying 60 households, then retained 36 unmet situations from the 120-household pilot.
  • Supported A$4.6 million storage-development work without presenting pilot acceptance as national demand.
  • Revised the 2025 replenishment proposition around timing choice and pause after 180 households expressed three different ordering preferences.

Decisions in context

The CPO role brought the product argument into the executive account of the retailer. I wanted the range story to retain the household conditions that made the proposition useful, including the conditions it had not yet served. The storage decision required separating common lid footprints from the different formats needed around them. The replenishment trial required another distinction between repeated use and a shared ordering interval. Both decisions complicated a simple commercial story, but that was preferable to letting the story erase the observation. My delegated expense funds the product function and its work; it is not the company's buying authority or retail operating budget. Executive board presentations began in July 2021 and do not constitute statutory service. The outcomes recorded here concern defined development choices and bounded pilot responses, leaving sales, safety, operational and subsequent customer results to the evidence and owners responsible for them.

Reason for the move

Promoted from portfolio leadership to the enterprise product remit; current appointment.

Jul 2015 — Jun 2021

Vice-president of product portfolios

Belvarel Retail

Sector
Household product portfolios and own-brand ranges
Ownership
Privately held Australian retailer
Company scale
A$1.32 billion company revenue in FY 2019–20
Employees
3300 company employees in FY 2019–20
Geography
Sydney-led range organisation supporting 142 Australian stores
Reporting to
Chief Operating Officer
Team
86 product colleagues through five direct reports in FY 2019–20
Financial scope
A$17.6 million annual product-function expense in FY 2019–20; purchasing commitments and retail execution retained their own approvals

Mandate

Assess which differences should remain in a household range and explain the fit conditions behind its common identity.

Outcomes

  • Separated 24 frames served by an existing cover pattern from 12 requiring different patterns in 2018.
  • Supported A$3.2 million for a 12-pattern development programme instead of extending a universal-fit claim.
  • Required the product proposition to describe pattern-to-frame relationships without claiming completed releases or lifetime benefits.

Decisions in context

Portfolio leadership made me responsible for the relationships among product choices, not merely the development of one item. A common identity could help people recognise a range while concealing differences that determined whether an item fitted. The furniture-cover decision exposed that tension. Twenty-four frames shared a workable pattern, while twelve needed different work. I accepted a fuller development programme and a less sweeping description rather than use universal language to make the range appear finished. The result was a funded scope with clear boundaries, not evidence that every new pattern had already reached a customer. This period also required closer coordination with buying and store colleagues whose work was affected by range complexity. I learned to give their concern a place in the decision without allowing operational convenience alone to settle what the product could honestly promise about use.

Reason for the move

Promoted to CPO as the portfolio remit expanded into the enterprise product agenda.

Apr 2008 — Jun 2015

Product Development Director

Belvarel Retail

Sector
Own-brand homewares product development
Ownership
Private Australian retail business
Company scale
A$620 million company revenue in FY 2013–14
Employees
1700 company employees in FY 2013–14
Geography
Sydney-based product development supporting 76 Australian stores
Reporting to
Executive responsible for merchandising and product
Team
48 development colleagues through four direct reports in FY 2013–14
Financial scope
A$7.2 million annual development-function expense in FY 2013–14; no independent authority over all buying or store expenditure

Mandate

Develop product propositions that made observed household differences consequential in the choices offered by the retailer.

Outcomes

  • Used a 72-household study to distinguish smaller-pourable and bulk refill preferences in 2012.
  • Supported A$1.6 million development of two formats while retaining the range-management cost of that choice.
  • Reported the 90-household pilot as 52 smaller-format and 38 bulk selections without importing national share or environmental claims.

Decisions in context

The move to Belvarel placed product development closer to the choice a customer encountered in a shop. I had to understand not only how an object worked, but how alternatives were explained and why one household might choose differently from another. The refill project gave that question a concrete form. A bulk-only range would have simplified the retailer's account, but the research included people who wanted a smaller pouring and storage task. Retaining two formats meant accepting more work around the range, with buying and supply colleagues contributing to the decision. I did not treat the household counts as a national demand model. The useful result was a proposition grounded in the situations we had observed and a pilot that could examine those choices. This role prepared me to ask which differences a portfolio should preserve, while keeping the commercial consequences distinct from the product team's own expense and authority.

Reason for the move

Promoted to product-portfolio leadership after expanding the development remit across household categories.

Jul 2001 — Mar 2008

Product Manager

Cervellan Homewares

Sector
Homewares product management and use instructions
Ownership
Privately owned household-products business
Company scale
A$140 million company revenue in 2007
Employees
620 company employees in 2007
Geography
Australia-based homewares development and supply relationships
Reporting to
Head of product management
Team
24 product colleagues through three direct reports in 2007
Financial scope
A$1.8 million annual product expense in 2007; quality, engineering and supply commitments separately authorised

Mandate

Shape homewares propositions and the explanations through which people would choose, assemble and use them.

Outcomes

  • Accepted responsibility for perspective-only stool instructions misread by 18 of 48 participants in 2006.
  • Supported A$280000 for revised orientation, sequence and part labels after Owen Calverden challenged the original account.
  • Retained 6 assisted cases in a separate 40-person retest rather than declaring the revision universally successful.

Decisions in context

Product management gave me authority over explanations that would travel beyond the development team. The assembly drawing I approved showed how that authority could conceal an assumption. I understood the brace orientation because I already knew the object; eighteen participants did not read the perspective the same way. Owen's challenge forced me to examine the confusing step instead of defending the illustration's appearance. The revision took additional time and expense, and the later exercise still contained people who needed help. I wanted those limits visible when the result was discussed. This appointment did not make me the owner of product-safety approval, and the observed assembly work should not be read as such an approval. The episode belongs in the chronology because it changed my approach to product explanation before I moved into the larger retail remit. It also shows a correction I had to make to my own judgement.

Reason for the move

Joined Belvarel to lead product development in a broader own-brand retail setting.

Feb 1994 — Jun 2001

Product Analyst

Cervellan Homewares

Sector
Analysis of household products and use situations
Ownership
Private homewares business
Company scale
A$42 million company revenue in 2000
Employees
260 company employees in 2000
Geography
Australia; product-analysis work supporting homewares colleagues
Reporting to
Product analysis manager
Team
Individual contributor in a twelve-person product-analysis group
Financial scope
No independent spending delegation or line-management responsibility

Mandate

Help connect product drawings and descriptions with the questions raised by the object’s intended household use.

Outcomes

  • Developed an understanding of how surrounding space changes the usefulness of a dimension or format.
  • Supported product comparisons and instruction discussions under senior colleagues without release authority.
  • Progressed towards product management after learning how the same object could be interpreted differently by its designer and user.

Decisions in context

I started in February 1994 after completing industrial design the previous December. The analysis group gave me a practical setting in which to test the relationship between a drawing and the life around the object. A container could be well proportioned in isolation and awkward inside a cupboard. An instruction could be technically recognisable to a designer while leaving a new reader unsure what to do next. My role was to help colleagues organise those questions, with management responsible for spending and commitments. The company's later retail scale should not be projected backwards onto this first appointment. I was an individual contributor among twelve people, learning how to make an observation useful in a product discussion. That learning did not make my later judgement infallible; the assembly mistake remained possible. It did give me a reason to take the user's interpretation seriously when the evidence eventually challenged my own.

Reason for the move

Promoted into product management after developing practical homewares-analysis experience.

What I am looking for next

I would like a future contribution to concern the way a consumer business makes promises about ordinary use. A board may need to understand which household differences sit behind a product range, what a pilot can support and where an attractive universal description outruns the evidence. I could bring experience of those decisions, including the instructions I approved and subsequently changed. I would want the institution's buying, operating, quality and financial perspectives alongside that contribution rather than assume the product view resolves every issue.

A first appointment would require preparation beyond my executive presentations. I have no statutory seat in this fictional record. Twenty-four annual days would be a starting estimate subject to employer agreement and the actual responsibilities, including induction and unusual demands. Relevant supplier, retail and personal connections would need disclosure. I would seek a setting that values an informed question about household use, while expecting me to learn its own context. The next chapter should broaden the judgement tested in this career, not turn a product-development history into an unsupported claim of readiness to chair any committee.