Strategy & Growth

How to prioritise e-commerce growth when everything feels urgent

More traffic, better product pages, another marketplace, an AI pilot: each can sound urgent. The challenge is deciding which deserves your team’s attention first.

Illustrated e-commerce initiatives including marketing, marketplaces and operations, with a shopping bag highlighted.

In short

Prioritise e-commerce growth by defining the commercial outcome, identifying what currently limits it and comparing a small number of actions. Consider expected contribution, evidence, effort and dependencies together. Commit to what your team can deliver and review, while keeping unproven opportunities in a separate validation queue.

Start with the outcome you need to improve

An e-commerce backlog can contain dozens of reasonable ideas. That does not mean they deserve equal attention.

“Grow online sales” provides too little direction. A more useful objective identifies the result you want to improve and the boundaries within which the team must work.

For example:

  • Increase contribution from the existing assortment without increasing advertising spend.

  • Improve conversion on priority product pages.

  • Reduce stock-related interruptions before expanding into another market.

  • Increase repeat purchases from an established customer base.

Choose a primary outcome for the next planning period. Record the current position, the measure you will use and any limits on budget or capacity.

Revenue, margin and cash are different measures. Agree which one drives the decision so that an initiative is not approved for one reason and judged against another.

Identify what is holding that outcome back

Start with the customer journey and the operation behind it.

Where does the evidence suggest that growth is being lost or delayed?

Limited relevant traffic may point towards acquisition. Visitors reaching product pages without buying may justify investigating the offer, information or buying experience. Strong demand combined with unreliable availability points towards a different priority.

These are starting hypotheses, not automatic diagnoses.

Review the information available across:

  • Traffic quality and acquisition sources.

  • Product-page and checkout behaviour.

  • Product contribution after relevant variable costs.

  • Stock availability, delivery and returns.

  • Repeat purchasing and customer feedback.

  • Time spent resolving recurring operational problems.

Look for a constraint that explains a meaningful part of the gap between the current result and the desired outcome.

Be specific. “Our website needs improving” is difficult to prioritise. “Customers repeatedly ask a compatibility question that our highest-traffic product page does not answer” suggests an action you can investigate.

Separate commitments, improvements and experiments

Not every task belongs in the same prioritisation exercise.

Essential commitments

Some work protects the ability to trade: resolving a broken checkout, addressing an account issue or delivering an existing customer commitment.

Give these tasks explicit capacity. Avoid presenting every routine request as essential simply because someone wants it completed quickly.

Performance improvements

These address an observed weakness in the current business, such as incomplete product information, inefficient advertising or slow order processing.

The case should connect a specific problem to a measurable outcome.

Growth experiments

These test an opportunity that remains uncertain: a new sales channel, a different acquisition approach or an AI-assisted workflow.

Define what the experiment needs to teach you and how much time or money you are prepared to commit.

This separation prevents a speculative opportunity from quietly consuming the resources needed to keep the existing business performing.

Compare actions using the same questions

Bring a shortlist to the discussion, rather than asking the team to score the entire backlog.

For each proposed action, answer:

  • Outcome: Which commercial or operational result should improve?

  • Evidence: What supports the diagnosis, and what remains an assumption?

  • Effort: What will implementation, coordination and ongoing maintenance require?

  • Dependencies: What must happen first?

  • Ownership: Who can deliver the work and evaluate the result?

You do not need a complicated numerical score. A short explanation can be more useful than an apparently precise total built on weak estimates.

The following example is illustrative, not a BND client case.

Imagine a brand whose immediate objective is to improve contribution from its existing online business, with limited team capacity.

Proposed action

Evidence available

Main dependency

Initial decision

Increase paid traffic

Existing conversion problems remain unexplained

Understand where relevant visitors drop out

Investigate before increasing spend

Improve priority product pages

Customer questions reveal missing product information

Product-team input and content capacity

Run a focused improvement test

Launch another marketplace

Customer fit and channel economics are untested

Validate demand, costs and operating requirements

Prepare a business case before launch

Automate stock updates

Manual updates repeatedly delay availability

Confirm reliable source data and integration scope

Assess feasibility and expected workload reduction

This is not a universal ranking. A different objective or stronger evidence could change the order.

The useful result is a decision the team can explain, including what would make it reconsider.

Turn uncertain opportunities into small tests

When an idea looks promising but the evidence is weak, the next priority may be validation.

Before a broad product-page redesign, test changes on a selected group of pages. Before adopting new software, map the recurring work and confirm which steps it could replace. Before entering another marketplace, compare the opportunity with improvements available in existing channels.

Keep each test explicit:

  • The question it should answer.

  • The products, customers or workflow included.

  • The starting position.

  • The time and budget available.

  • The result that would justify further work.

Avoid changing so many things at once that the team cannot interpret the outcome. Record relevant context such as promotions, stock changes or seasonal demand.

For expansion decisions, our marketplace selection guide provides a more detailed framework for comparing channels. For recurring product-data work, our Channable guide shows how to assess the role of tooling.

Commit to a plan your team can deliver

Prioritisation is incomplete until the selected work has capacity.

Agree a small number of active priorities. There is no universal limit, but each additional initiative competes for attention, decisions and follow-up.

Give every priority:

  • One accountable owner.

  • A defined deliverable.

  • The people and budget required.

  • A success measure.

  • A review date.

An actionable priority might read:

“Improve the content on our selected product pages using verified specifications and recurring customer questions. The e-commerce manager owns delivery, with product-team approval. Review conversion alongside traffic mix and availability after an agreed measurement period.”

That is more useful than “optimise the webshop”.

Keep a visible “not now” list, with a reason for deferring each opportunity. It allows the team to preserve good ideas without treating all of them as current commitments.

Review results and change priorities deliberately

A priority list should respond to evidence.

At each agreed review, ask:

  • Was the work delivered as intended?

  • What changed in the relevant measures?

  • What else may have influenced the result?

  • Should we continue, adjust, expand or stop?

Distinguish delivery from impact. Publishing new content completes a task; it does not establish whether the content improved the buying experience.

Also review capacity. If routine work repeatedly displaces agreed improvements, address that constraint rather than carrying the same unfinished priorities into every meeting.

When ongoing growth support can help

Some teams know what they want to achieve but struggle to maintain the connection between decisions, delivery and review.

Priorities compete across marketing, e-commerce, product and operations. External specialists may each deliver useful work while nobody coordinates the overall commercial agenda.

BND’s Growth Partner service combines a prioritised plan, delivery of agreed activities and regular performance reviews with your team. Support can sit alongside existing people and partners, with responsibilities defined around the assignment.

The aim is to turn the next growth decision into work that gets delivered, evaluated and improved.

About the author

Gijs van Male, founder of Brand New Digital

Gijs van Male is the founder of Brand New Digital, focused on e-commerce strategy, growth and commerce operations.

Topics

E-commerce Strategy

Growth Priorities

Share this insight

Which growth priorities deserve your team’s attention?

BND helps connect commercial priorities with agreed execution and regular performance reviews, working alongside your team and existing specialists.

© 2026 Brand New Digital B.V. All rights reserved.

·

Privacy Policy

·

Cookie Policy

·

Terms & Conditions

·

Disclaimer

© 2026 Brand New Digital B.V. All rights reserved.

·

Privacy Policy

Cookie Policy

·

Terms & Conditions

·

Disclaimer

© 2026 Brand New Digital B.V. All rights reserved.

Privacy Policy

Cookie Policy

Terms & Conditions

Disclaimer