Projects
Each project started with a delivery bottleneck, a growth constraint, or a user experience gap. I led cross-functional execution on those constraints.

Bored Cow
↗Project Manager
Problem: The brand needed a responsive storefront that could support growth without creating delivery friction between teams.
Constraints: Multiple stakeholders across creative, development, and operations had competing priorities and dependencies.
Approach: I established a shared delivery cadence, aligned owners by milestone, and ran decision-focused cross-functional checkpoints.
Outcome: I coordinated launch planning and team handoffs through milestone ownership and cross-functional checkpoints.

Zebpay
↗Project Manager
Problem: The project called for a review of the mobile commerce experience across devices and browsers.
Constraints: Cross-browser behavior and responsive quality had to be fixed without slowing delivery velocity.
Approach: I coordinated design-dev QA loops, prioritized responsive fixes, and enforced browser-specific acceptance criteria.
Outcome: I coordinated responsive fixes and design-dev QA across the target device and browser matrix, using browser-specific acceptance criteria.

ERG
↗Project Manager
Problem: The team needed a scalable e-commerce platform delivered within a fixed launch window.
Constraints: Scope expansion risk and tight timeline pressure were affecting multiple workstreams.
Approach: I ran sprint-based planning with strict scope control, weekly risk review, and stakeholder signoff checkpoints.
Outcome: I coordinated launch planning through sprint-based planning, scope control, and stakeholder signoff checkpoints.

Déhanche
↗Project Manager
Problem: The site experience needed a UX refresh to improve engagement while preserving premium brand identity.
Constraints: Brand consistency had to be maintained while modernizing interaction patterns.
Approach: I aligned design and engineering on reusable UI standards, review cycles, and implementation quality gates.
Outcome: I coordinated the UX refresh through reusable UI standards, review cycles, and implementation quality gates.

One Skin
↗Project Manager
Problem: The project called for page-performance work with a focus on the mobile user experience.
Constraints: Performance gains were required without compromising content quality or release timelines.
Approach: I prioritized performance work in roadmap planning and coordinated lazy loading and code-splitting implementation.
Outcome: I coordinated lazy loading and code-splitting implementation as part of performance work in roadmap planning.

Rephuel
↗Project Manager
Problem: The project focused on organic discoverability for the e-commerce channel through technical and content SEO.
Constraints: SEO improvements needed to align with existing content, technical constraints, and release cycles.
Approach: I led SEO implementation planning across technical and content tasks with clear ownership and rollout sequencing.
Outcome: I coordinated technical and content SEO tasks with clear ownership and rollout sequencing across release cycles.
Recommendations
Recommendations from clients and colleagues live on my LinkedIn profile rather than being reproduced here.
Read them on LinkedInPlanning your next launch?
Best fit: teams with an active web initiative, several stakeholders, and a date that needs to hold.
Start a conversation