The image above outlines the tech stack map I created for this project. Please note: specific service names and data flows have been removed to protect PrettyLittleThing’s company privacy.

The Challenge

PrettyLittleThing's rapid digital growth had outpaced internal documentation. Teams relied on legacy knowledge and outdated resources, creating bottlenecks in onboarding, cross-functional planning and strategic decision-making around tech debt and dependencies.

The Solution

Built a comprehensive, centralised documentation hub mapping PLT's complex integration landscape to reduce team friction and enable scalable growth across Product, Digital, Logistics, and Customer domains.

Research & Discovery

• Conducted cross-functional stakeholder interviews with Tech Leads, Product Managers, Engineering, and Ops teams

• Identified critical knowledge gaps and aligned documentation priorities with business needs

• Mapped complex system relationships and data flows across multiple domains

Documentation Architecture

• Designed intuitive information architecture structured by service domains and user personas (PMs, Devs, Ops)

• Created standardised documentation format and tagging system for improved traceability and maintainability

• Applied UX writing principles to present complex technical concepts clearly and accessibly

Key Deliverables

System Integration Mapping

• 160+ system integrations mapped across internal and external services

• 50+ detailed service entries documenting purpose, ownership, data flows, and interdependencies

• Visual architecture diagrams and flowcharts for at-a-glance understanding

Centralised Knowledge Hub

• Searchable Confluence workspace with intuitive navigation and filtering

• Onboarding guides for new team members across Product and Engineering

• Scoping frameworks for cross-team discovery, impact analysis, and roadmap planning

Impact & Results

Operational Efficiency

• Accelerated onboarding for 120+ team members across PLT and Boohoo Group, reducing ramp-up time across departments

• Reduced developer dependency for early-stage planning and discovery work

• Improved cross-team collaboration enabling confident feature and fix planning

Strategic Enablement

• Informed critical decisions including Magento deprecation roadmap by exposing dependencies and gaps

• Created scalable framework for documenting future services and squad expansions

• Established knowledge management standards that reduced tribal knowledge dependency