Project Management Swimlane Diagram for E-Commerce Journey

Tech architecture infographic titled "Project Management Swimlane Diagram" using HOW-IT-WORKS archetype adapted as a customer journey swimlane map for an e-commerce company: Awareness → Consideration → Purchase → Fulfillment → Support → Loyalty. Create an executive-deck grade swimlane diagram with horizontal department lanes and vertical journey stages. Labeled boxes for each entity, department, system, and step connected by clear directional arrows showing flow across lanes. Include these swimlanes with boxed components: Customer lane, Marketing lane, E-commerce Storefront lane, CRM lane, Sales / Merchandising lane, Order Management lane, Payment Service lane, Warehouse / Fulfillment lane, Customer Support lane, Analytics lane. In each box show a generic icon, a canonical English name, and a one-line English role description. Example stage boxes: Awareness: "Ad Campaign — Drives traffic from paid and organic channels", "Landing Page — Captures visitor interest and click intent", "Web Analytics — Tracks sessions, source, and conversion events". Consideration: "Product Catalog — Shows items, pricing, and availability", "Recommendation Engine — Suggests relevant products", "CRM Lead Profile — Stores customer attributes and engagement history". Purchase: "Shopping Cart — Holds selected items before checkout", "Checkout API — Validates cart, address, and shipping options", "Payment Gateway — Authorizes card or wallet payment", "Order Management System — Creates confirmed order record". Fulfillment: "Warehouse Queue — Receives pick and pack request", "Inventory Service — Reserves stock for the order", "Shipping Provider — Delivers parcel and tracking updates". Support: "Help Desk — Handles returns, refunds, and issue tickets", "Notification Service — Sends email and SMS updates". Loyalty: "Loyalty Program — Awards points and repeat purchase incentives", "CRM Campaign Automation — Triggers retention journeys", "BI Dashboard — Measures repeat rate, CAC, and LTV". Add arrows with short English labels such as "Ad click", "Session event", "Product view", "Add to cart", "Checkout request", "HTTPS payment token", "Auth approved", "Order created", "Pick list", "Tracking update", "Refund request", "Retention email", "Repeat purchase". Show technically accurate flow where appropriate: customer browser sends HTTPS requests to storefront, storefront calls Checkout API, Payment Gateway returns authorization result, Order Management writes order confirmation, warehouse receives fulfillment request, support updates CRM and notifications. Add small illustrative metrics in English near selected boxes, such as "CTR 3.2%", "Conversion 2.8%", "AOV $84", "Pick time 12 min", "Return rate 4.1%", clearly marked as example values. Include a numbered legend 1-7 in English walking through the lifecycle: 1. Customer discovers campaign and visits storefront. 2. Customer browses catalog and engagement data is captured. 3. Customer adds items to cart and begins checkout. 4. Payment is authorized and order is created. 5. Inventory is reserved and warehouse fulfills shipment. 6. Customer receives delivery and support handles post-purchase issues. 7. Loyalty and CRM systems trigger retention offers and repeat orders. Visual style: consultant-deck professional, minimal monochrome palette, crisp grayscale with charcoal, white, silver, and subtle light-gray accents, strong hierarchy, clean grid, ample whitespace, thin arrow lines, executive presentation mood, precise labels, neutral department titles, no real person names, no real company logos, generic icons for departments, tools, and vendors. editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-company logos. Use generic icons for departments / tools / vendors. Org-chart titles stay neutral (no real person names). Process timings / costs / volumes are illustrative example values.