top of page

Enabling Web-Based Asset Association to Reduce Onboarding Friction

Timeline: MVP: Q4 2024 – 1:1 and 1:N association support
Advanced Features (Journey Mapping & Alerts): Planned for Q1 2025
Role: Product Manager – Customer Onboarding Experience & Smart Kit Enablement
Scope: Simplifying device onboarding by removing mobile dependency

 Why (Problem)

  • High onboarding friction due to reliance on mobile app (APK) for scanning and associating tapes.

  • Smart Kits, used in pre-sale evaluations and proof-of-concept (POC) deployments, needed a lighter, faster association method without involving mobile logistics.

  • Internal teams faced coordination overhead with customers during activation, affecting adoption speed and first-time success.

🚀 What (Solution)

  • Removed mobile-only dependency by building browser-based asset scanning directly into the Web Application.

  • Delivered a simplified association flow that supported:

    • Admins (Facility Managers) – for facility + permission control

    • Operators (End-users) – for rapid device onboarding

  • Captured feature vision for long-term needs like journey mapping and alerting, while focusing MVP scope on speed and usability.

🔧 How (Execution)

🔍 Business/Product:

  • Conducted interviews with account owners and deployment teams to map the onboarding process and pain points.

  • Aligned on the goal of reducing time-to-activate while supporting multi-user workflows and facility-based access control.

🎨 Design:

  • Collaborated with UI/UX to define user journeys for both admins and operators.

  • Identified flow gaps and permissions logic that differed from mobile behavior.

👨‍💻 Engineering:

  • Authored detailed product specs, including edge cases and QA acceptance criteria.

  • Prioritized core capabilities (1:1 and 1:N association) while postponing advanced journey logic.

  • Participated in sprint grooming, internal demos, and coordinated release management.

🔁 Stakeholder & Timeline Management:

  • Maintained feedback loop with customer success and support teams for real-world feedback.

  • Trained internal teams to support the feature post-launch.

  • Negotiated with engineering leadership to defend scope amid tech debt and competing priorities.

bottom of page