Private & Confidential · August 2026

Role Scope & Career Development Review

Proposed Role Alignment: Digital Solutions Lead

Daisy Huang Current · Digital Business Analyst Proposed · Digital Solutions Lead
Tenure at Lovisa
18+ months
January 2025 to present
Same position title throughout
Current base salary
$62,780.27
+ 12% superannuation
$70,313.90 total package
Scope today
OMS · PIM · S2S
Primary functional & operational lead
Plus omnichannel reporting

My request is based on the sustained development of my role from a support-focused BA position into a role combining requirements, high-level solution design, independent end-to-end delivery, functional leadership, cross-system integration work, automation and data analysis.

Current role Demonstrated scope Proposed alignment Next step

01 · Role Evolution

From Support BA to Digital Solutions Design and Delivery

The original position description, mapped to the responsibilities I hold in practice today. Hover one to trace the work behind it. Click to bring that work to the top.

Original JDHelp with project management and delivery
Independently lead assigned projects end-to-end
Original JDUnderstand stakeholder requirements
Translate requirements into high-level solution designs
Original JDHelp with UAT
Lead UAT, implementation and post-release support
Original JDHelp with BAU
Functional and operational lead across assigned OMS, PIM and S2S workstreams
Original JDCo-manage Jira / Confluence
Lead integration requirements for projects involving other platform teams
Original JDAPI / webhook knowledge listed as a bonus
Use API, automation and data skills to solve operational problems

Full position description and demonstrated-scope mapping are in the supporting evidence.

02 · Evidence

Selected work & outcomes

Ten workstreams, all delivered inside the current Digital Business Analyst role.

Data, automation and executive reporting

Omnichannel KPI Dashboard & Power BI Automation

My roleBuilt end-to-end: data sourcing, processing automation, KPI definition and visualisation
What I didDesigned and built the omnichannel KPI dashboard from scratch, automated the Power BI data-processing steps behind it, and defined the KPIs tracked by the business.
Why it mattersPresented to the CEO, CIO, Head of E-commerce and Head of Retail Operations at the Omni-channel Steerco.
4–6 hours → under 1 hour data processing time, per reporting cycle
Problem identification + delivery

PIM Price Enhancement

My roleIdentified the problem, proposed the solution, delivered the enhancement
What I didFound a DataProd to PIM integration gap through BAU operations, designed the enhanced price-sync approach, then led it from requirements through development handover, testing and implementation.
Why it mattersProactive problem identification and resolution of $0 price issues, not requirement execution handed to me.
71.43% → 98% data accuracy · ~3 hours of manual work removed each week
Process automation at rollout scale

OMS Store Setup Automation

My roleIdentified the manual bottleneck and scripted the process
What I didScripted OMS store creation for the US and Canada rollout, close to 300 stores, and built it to be reusable for further markets as the rollout extends globally.
Why it mattersBuilt once for a specific rollout, designed so it does not need rebuilding for the next one.
~3 days → under 10 minutes per store setup · ~300 stores across US & CA
Targeted technical solution

Canada Post Automation

My roleDesigned, built and deployed the solution
What I didDeveloped and deployed a Cloud Function for Firebase to automate the Canada Post manifest submission process.
Per-parcel overcharging resolved on outbound SFS shipments
Analysis for operational decisions

CKC Performance Analysis

My roleData sourcing and analysis
What I didSourced previously unavailable fulfilment-time data and built a store-level view covering order volume, order value, pick/pack time, customer collection time, SLA performance and trends.
Why it mattersMade click and collect performance measurable where it previously was not.
Cross-team migration support

MOM Migration: Testing and Data Validation

My roleCross-team technical support, outside my own workstreams
What I didIndependently built an automated data-validation solution to support migration testing, covering a full year of order data across six regions.
Why it mattersReplaced what would have been a manual reconciliation effort for another team.
6 regions · built in one day annual order data validated automatically
Decision support, recommended not to build

Returns Module Evaluation

My roleSolution assessment and recommendation
What I didAssessed integration cost, ongoing maintenance and complexity for a OneStock returns option, and supported the decision to use Shopify native returns instead.
Why it mattersThe recommendation was to not build. That was decided on total cost of ownership rather than on delivering the request.
Solution design + end-to-end delivery

OMS Decommission

My roleEnd-to-end delivery lead and high-level solution design
What I didDefined the future-state flow connecting WMS directly to Shopify, and managed the workstream through requirements, solution design, cross-team dependencies, testing and implementation planning across business, technology and vendor teams.
Why it mattersSolution definition and delivery responsibility on a decommission affecting core order flow.
Evidence-based improvement case

S2S Enhancement

My roleFunctional lead for S2S, and built the case for improvement
What I didIdentified recurring operational issues in the Ship-to-Store flow, gathered supporting data including the online-order proportion, and defined the improvement case and requirements before any build was committed.
Why it mattersFramed the problem with data first, rather than escalating it as a support issue.
~10–15% of S2S orders affected by the recurring issues identified
Continuity through the management transition

Leadership Transition: Technical Continuity

My roleKey knowledge contact for systems and integrations
What I didFollowing the departure of the Senior Digital Manager, and with no formal handover, supported issue investigation, clarified existing integration flows and dependencies across Turbo360, WMS, DataProd, Futura, Shopify, OMS and PIM, and contributed solution input for incoming requirements.
Why it mattersDigital initiatives continued to progress where technical and system knowledge was required. Another senior team member took primary responsibility for team coordination.

Full project detail, business-thinking examples and additional BAU scope are in the supporting evidence.

The point

The nature of the role has changed, not simply the volume of work. These responsibilities and this body of work sit a level above the position I was hired into.

03 · Why This Role

Why Digital Solutions Lead?

I chose Digital Solutions Lead because my role is no longer only business analysis. The value I provide sits across business requirements, solution definition and delivery. I am not proposing a software engineering or solution architect role. It is a technical-functional delivery role.

Business & Product

  • Requirements
  • Prioritisation
  • Business process
  • Stakeholder management

Solution

  • High-level solution design
  • Feasibility assessment
  • Cross-system dependencies
  • Integration requirements

Delivery

  • End-to-end project delivery
  • Requirements handover to development
  • UAT
  • Implementation & post-release support

Technical & Data

  • Automation
  • API understanding
  • Firebase / Python
  • Data analysis and reporting
Digital Solutions Lead
Technical-functional individual contributor

What this role is not

Not Senior Business Analyst
My scope extends past requirements analysis into solution design and ownership of delivery outcomes.
Not Developer
Development remains with the Development team. I build targeted automation only where there is a clear business need.
Not Solution Architect
I work at high-level solution design for assigned initiatives, not enterprise architecture ownership.
Not Digital Manager
No people-management or team-coordination accountability. This complements the team manager rather than duplicating it.
04 · Business Value

What I am carrying now

To be clear on framing: the recent management change is not the reason for this request. The review discussion began before it. But the transition has made the level of system and integration knowledge I already provide more visible.

Independent delivery

Continue to manage assigned OMS, PIM and omnichannel workstreams independently, from requirements through to post-release support.

System & integration knowledge

Support Digital projects involving Turbo360 and dependencies across WMS, DataProd, Futura, Shopify and other connected systems.

Technical-functional continuity

Support solution assessment and cross-system investigation while the team structure settles. This is the work covered in the transition card above.

Forward look AI Opportunity Map Eight practical AI use cases for our retail and digital environment, prioritised by effort and expected value, with a delivery approach and governance guardrails. Prepared as a proposal for the AI transformation. Open the proposal
05 · Market Context

How the market benchmarks this scope

For reference only. This shows how the Melbourne market benchmarks the role I was hired into, alongside the role scope I am now performing. I am not proposing a figure. That would be for Lovisa’s own benchmarking to determine.

Total remuneration package, including 12% superannuation
Melbourne market, 2026. Base-salary equivalents are in the table below.
Current
Digital Business Analyst · contract
$70,314
Market reference · BA
Melbourne IT BA (1–3 yrs) · 25th percentile
~$87,360
Market reference · BA
Melbourne IT BA (1–3 yrs) · median
~$100,800
Market reference · the scope in question
Digital Solutions Lead · Melbourne range
$100k–$120k
Package (AUD)
$60k
$70k
$80k
$90k
$100k
$110k
$120k

How to read this

These are external market references, not a proposal. The BA benchmarks describe the role I was hired into. The Digital Solutions Lead range describes the scope I am now performing. Any internal alignment would be subject to Lovisa’s own benchmarking and banding.

Why both references are shown

Showing only the BA benchmark would understate the scope. Showing only the Digital Solutions Lead range would ignore where I started. The gap between the two is the substance of this review.

Market benchmark comparison of base salary and total package
Benchmark Base salary Package (incl. 12% super)
Current compensation (contract) $62,780.27 $70,313.90
Melbourne IT BA (1–3 yrs) · 25th percentile ~$78,000 ~$87,360
Melbourne IT BA (1–3 yrs) · market median ~$90,000 ~$100,800
Digital Solutions Lead · Melbourne range $89,000–$107,000 $100,000–$120,000

Market references: Glassdoor (June 2026) and SEEK Salary Insights (2026). All package figures include 12% superannuation.

06 · Request

What I am asking for

1

Clarity on the next step

I believe the work and the level of responsibility I have taken on support this promotion. I would also like to understand whether the business sees a path to formally recognise this scope, and whether you would like me to continue developing and contributing at this level.

What process would be required · who reviews it · what timeline is realistic
2

Role review

Review my role for reclassification against the scope I am already performing, with formal benchmarking to follow whatever process applies internally.

Digital Business Analyst Digital Solutions Lead