Start with the customer journey
Digital-product optimisation works best when customer experience, product decisions and technology constraints are investigated together. A visible problem on a screen is only the symptom. The cause may sit in design, product rules, data, platform behaviour, integration, operational process or the way teams have prioritised the work.
The starting point is the customer journey. Identify the tasks that matter most to customers and the organisation, then look for friction, delay, confusion and abandonment. The question is not merely “What should this screen look like?” but “What is the customer trying to achieve, what gets in the way, and why?”
Use several forms of evidence
Useful evidence can come from customer interviews, observed behaviour, support contacts, analytics, sales information and feedback from frontline teams. Each source has limitations, so the strongest view often comes from combining them.
Expert evaluation is useful as well, but it should complement rather than replace customer evidence. An experienced reviewer can identify usability patterns and likely friction quickly; customer and commercial data help establish which problems actually matter most.
Consider the technology in context
Technology should then be examined in context. Some experience problems come from a platform constraint, slow integration, brittle data flow or a legacy rule that is expensive to change. Others can be improved without replacing the stack.
The useful question is therefore not “Do we need a new platform?” but “Which constraints genuinely limit the customer and commercial outcome, and what is the least disruptive way to remove them?” That framing helps separate incremental optimisation from architecture work that genuinely needs larger investment.
A mobile-commerce example
In one mobile-commerce optimisation engagement, Milcane reviewed an existing product using customer interviews, expert evaluation and analysis of sales and customer data across online and physical channels.
The assessment engaged both development and business teams. It identified a combination of usability, technical and product-management issues contributing to customer abandonment and weaker mobile sales. The remediation therefore could not be owned by design alone or engineering alone.
The case shows why diagnosis needs to cross organisational boundaries: customer friction was being created by a combination of product rules, interface decisions, technical constraints and operational processes. Improving the journey required those causes to be addressed together.
Build an evidence-backed improvement backlog
A practical optimisation backlog should connect each proposed change to evidence and an outcome. That makes it easier to distinguish a high-friction customer problem from a cosmetic preference, and to separate fast improvements from work with deeper technical dependencies.
For each item, ask: what problem does this solve, what evidence supports it, what systems or teams does it touch, what is the expected outcome, and how will we know whether it helped?
This also creates a healthier relationship between UX and the technology stack. Teams can improve the experience where the current platform allows it while collecting evidence about the constraints that repeatedly prevent improvement. A platform change then becomes a business and product decision supported by evidence, not a reflex.
Remediation is cross-functional work
Cross-functional remediation needs ownership. Product leadership can prioritise the customer and commercial outcomes. Design or UX expertise can define and test better interactions. Engineering can expose technical constraints and options. Project or delivery leadership can sequence the work, manage dependencies and keep the improvement programme moving.
The work should also include operational teams where the journey crosses support, fulfilment, sales or service processes. A polished interface cannot compensate for a broken hand-off behind it.
Optimise iteratively
Optimisation should be iterative. Smaller changes can be released and measured while larger work is being designed. New customer evidence may change the order of priorities. Technical investigation may reveal that a constraint is easier—or harder—to remove than expected.
That is a reason to maintain a clear improvement hypothesis and decision cadence rather than locking a long roadmap too early.
Connect UX, product, technology and delivery
The broader lesson extends beyond mobile commerce. Digital, eCommerce and connected products all benefit from treating experience, product and technology as one system. Customer evidence tells the team where value is being lost; product judgement decides what matters; technology analysis explains constraints; delivery discipline turns the decisions into workable change.
Milcane brings those disciplines together through Project Management, Product Management and technology delivery experience. The objective is not a redesign for its own sake. It is a clearer, more usable and commercially sensible product, achieved through evidence-led decisions and practical delivery. See Project & Product capability and Connected Products capability.
Matthew Tati
Matthew leads Milcane and has more than 20 years of experience shaping and improving digital products. His work includes customer research, product direction, UX and technology diagnosis, and leading cross-functional remediation across business and technical teams.