Parcel Content Verification Service

Transforming a service that existed on paper into one that actually worked in the real world.
Role: Project Manager
Service & Process Redesign
Customer Journey Transformation
3-System Integration
Improved Service Efficiency & Reduced Customer Friction

Context

Environment

The initiative focused on an existing service that was formally available but not operationally viable — parcel content verification.

Customers expected to inspect parcels before payment, but systems and operations did not support this behavior.

This created a disconnect between:

  • customer expectations
  • service promise
  • operational execution

With the growth of e-commerce, the gap became more visible, leading to increased dissatisfaction from both recipients and corporate clients.

The Core Problem

The issue was not the absence of a feature, but a breakdown in system and service alignment:

  • no system visibility for verification requests
  • operators unable or unwilling to perform the service
  • payment required even after inspection
  • parcels marked as “delivered” regardless of outcome

As a result:

  • increased customer frustration
  • longer service times due to конфликты
  • operational stress for staff
  • loss of trust from corporate clients

The challenge wasn’t creating a new feature—it was making an existing service actually work.

Constraints

  • Legacy system logic governing delivery status
  • Integration across 3 core systems (operator, billing, pricing)
  • Large-scale operational environment (thousands of locations)
  • Multiple system versions in parallel use
  • Strict compliance and internal dependencies

The operator system posed a key constraint:

  • deeply embedded in daily operations
  • difficult to modify
  • used by thousands of employees

Stakeholders

The initiative required alignment across:

  • Business units (B2B and B2C)
  • Product teams
  • IT and architecture teams
  • Operations leadership
  • Frontline postal operators

Each group had different priorities, making alignment critical to delivery.

My Role & Ownership

What I Owned

I led the initiative end-to-end from discovery through implementation:

  • Conducted UX research and customer interviews
  • Defined customer journey (as-is and to-be)
  • Redesigned the service model and operating process
  • Designed the future-state service model
  • Provided UX/UI direction for system changes
  • Aligned business, operations, and technology teams around a shared implementation approach
What I Influenced
  • System interaction logic
  • Service design decisions
  • Implementation prioritization
What I Did Not Control
  • Legacy system constraints
  • Technical limitations
  • Organizational readiness for масштабирование

Approach / Framework

1
User Research & Problem Discovery

Led customer interviews to identify key pain points across senders and recipients.

2
Current State Mapping

Mapped existing journeys and processes to identify gaps between service intent and execution.

3
Service Redesign

Defined target customer journey and redesigned processes to align expectations with operational reality.

4
System Architecture Alignment

Defined updated service logic across systems, including status handling and visibility.

5
Integration Planning

Led coordination of implementation across three systems, ensuring consistency and compliance.

Execution Highlights

Making the Service Match the Promise

Aligned customer expectations, operational workflows, and system behavior so the service could finally work as intended.

Redesigning Core System Logic

Redefined delivery status rules to support parcel inspection before payment, eliminating unnecessary returns and operational friction.

Designing for Real Operations

Ensured the solution fit real frontline workflows rather than creating additional operational complexity.

Metrics & Results

Pilot Results:
Reduced customer complaints
Faster service at postal counters
Improved customer trust
Increased service adoption
Growth in service usage

System-Level Impact

Service Became Operationally Viable

Transformed the service from a formal offering into a functioning, executable process.

Customer Journey Transformed

Enabled customers to make acceptance decisions before payment.

Operational Friction Reduced

Reduced conflicts between customers and operators, improving service flow.

Business Value Restored

Re-enabled a high-margin service as a scalable and usable offering.

Lessons / Insights

Great Services Need Great Systems

A customer experience can only succeed when service design, operational processes, and system behavior work together.

System Logic Drives Customer Experience

Rigid system behavior can directly create customer friction.

Customer Control Builds Trust

Enabling decision-making before payment improves satisfaction and retention.

Adoption Completes Delivery

A project isn’t successful when implementation ends. It’s successful when people adopt the new way of working.

Improving an Existing Service?

If you’re redesigning customer journeys, modernizing operations, or solving complex service challenges, I’d be happy to help turn fragmented processes into solutions that work in the real world.