When Growth Exposes Cracks: Why Traditional UX Strategies Fail at Scale in Events

Weddings and celebrations businesses live and breathe experience. Every design decision, from RSVP flows to vendor matchmaking interfaces, directly impacts emotion and conversion. Yet, what works at a boutique scale buckles once your company expands beyond a few hundred users—or a dozen events per month.

I’ve led UX teams through this stretch at three different rapidly growing events companies. At first, we tried classic user-centered design methods: personas, journey maps, and endless interviews. They delivered insights but stumbled when the team doubled or tripled, and new features piled up. Deliverables lagged. Priorities scattered. Feedback loops slowed.

Growth exposed a critical gap: We lacked a shared, practical framework to anchor decision-making across expanding teams. Enter the jobs-to-be-done (JTBD) framework. It’s been a north star for us, especially in the chaotic growth stage where priorities clash and delegation becomes essential.

But JTBD isn’t a silver bullet. It requires adapting at scale—otherwise, it’s just another theory that sounds good but doesn’t solve real-world complexity.

JTBD at Scale: Beyond Theoretical Appeal

At its core, JTBD frames user needs as “jobs” they want done—not just features or demographic profiles. For wedding and events UX teams, this means reframing design around the core functional, social, and emotional jobs couples or planners hire your product to complete.

In theory, this sounds perfect. But when your team grows from 3 to 12 designers and you’re juggling multiple event verticals—weddings, corporate celebrations, and social gatherings—the challenge is how to operationalize JTBD so it:

• Enables clear delegation without dilution
• Scales across different user segments and event types
• Aligns cross-functional teams (marketing, vendors, sales) around shared goals

A 2024 Forrester report found over 60% of UX teams in events-related verticals struggle with cross-team alignment during scaling. JTBD can help, but only if your management approach embraces it beyond just a research tool.

Breaking JTBD into Management Components for Growth

1. Define Core Jobs at the Team Level — Then Delegate Specialists

When I started at an events SaaS scaling from $5M to $20M ARR, we first codified 3-5 core “jobs” across our wedding and celebrations platforms. For example:

These jobs became the backbone of our quarterly goals. Each was assigned to a design lead specializing in that job domain. This avoided a common pitfall where all designers chase “everything” and results are scattered.

Delegation to jobs owners also enabled laser-focused usability testing and feature prioritization—no more debates about “whose feature is more important” at growth velocity.

2. Standardize JTBD Research Inputs Using Tools Like Zigpoll

At scale, decentralized teams need consistent user feedback. We set up monthly pulses using Zigpoll and Typeform surveys embedded within the product to capture which “job” users were trying to complete, frustration points, and unmet needs.

This continuous JTBD-focused data flow replaced quarterly deep-dive interviews that were too slow and resource-heavy. It also helped remote or junior designers quickly understand shifting priorities without relying only on anecdotal feedback.

The downside? Automated surveys can miss nuance. We supplemented them with bi-weekly in-person or video contextual inquiries, rotating team members to keep grounding in real user contexts.

3. Map Jobs to Business Outcomes and Design KPIs

Scaling UX teams often lose sight of impact as processes proliferate. To keep JTBD operational, we linked each job to measurable UX KPIs and business outcomes:

• RSVP job → reduce form abandonment by 15%
• Vendor sourcing job → increase vendor booking conversion by 10%
• Inspiration job → boost session duration on inspiration pages by 20%

These metrics were reviewed in weekly design stand-ups and monthly cross-functional reviews. This created accountability and visibility—critical in high-growth where priorities shift.

One team I worked with improved RSVP completion from 2% to 11% conversion in six months by focusing design sprints explicitly on job-related friction points uncovered via survey data.

4. Tailor JTBD to Event-Specific Contexts and Segments

Events UX can’t be one-size-fits-all. Jobs vary dramatically by event type (wedding vs. corporate), scale (intimate vs. large), and user role (planner vs. couple).

Instead of generic job statements, we created segmented job profiles that guided localized design experiments. For example, “secure trusted vendors” for a wedding couple involves different workflows and trust signals than for a corporate planner booking 100+ vendors.

This segmentation helped distribute workload among specialized pods, each owning a vertical or event type, while aligning on the overarching JTBD framework.

5. Evaluate JTBD Adoption and Risks Regularly

JTBD frameworks can fail if teams treat them as static documents rather than living tools. Regular check-ins on JTBD adoption are essential:

• Are teams still using jobs as lenses for decisions?
• Do product roadmaps reflect shifts in jobs priorities?
• Are cross-team conflicts reduced through shared JTBD language?

A risk we saw: over-formalizing JTBD led to bureaucracy and slowed iteration. Balance is key—enough structure to unify, but flexibility to pivot.

Measuring JTBD Effectiveness in Scaling UX Teams

Quantifying JTBD impact requires layering qualitative and quantitative insights.

Tracking these metrics over quarters informs whether JTBD is driving tangible progress or just causing overhead.

Scaling JTBD: Practical Tips for Growing UX Managers

• Start small, iterate: Don’t try to map every single job across every user segment at once. Begin with critical jobs impacting business outcomes, then expand.
• Document jobs clearly and accessibly: Use visual maps and simple language in shared tools like Confluence or Notion to avoid silos.
• Rotate job ownership to build team capability: Delegation means some designers will lead on job discovery while others focus on execution.
• Embed JTBD in cross-functional rituals: Include marketing, sales, and vendor teams in JTBD reviews to align around customer jobs, reducing siloed priorities.
• Combine JTBD with agile UX processes: Sprint planning should prioritize jobs with the highest impact, and reviews must reassess jobs based on real-world feedback.

When JTBD Won’t Work For Your Events UX Team

JTBD is not a silver bullet for every scenario:

• If your events business is highly transactional with little variation in user needs (e.g., simple ticketing), JTBD may add unnecessary complexity.
• In hyper-rapid innovation environments where experimentation outruns research cycles, rigid JTBD frameworks may slow teams.
• Teams without buy-in from leadership or cross-functional partners will struggle to maintain JTBD momentum beyond initial enthusiasm.

In those cases, consider lightweight JTBD-inspired heuristics, or rely more heavily on direct user feedback tools like Zigpoll and Hotjar for quick pulses.

Final Thoughts: JTBD as a Management Framework, Not Just a UX Tool

JTBD’s real power at scale lies in transforming how managers lead UX teams—shifting from feature lists and personas to a shared understanding of customer jobs rooted in measurable business outcomes. This shift requires intentional delegation, continuous data-driven feedback, tailored event-specific segmentation, and a disciplined culture of review.

For growth-stage weddings and celebrations companies, this approach anchored our expanding teams amid competing priorities, multiple event types, and evolving customer expectations. It turned JTBD from a design theory into a tactical framework guiding what to build, who owns it, and how to measure success as we scaled.

If you’re wrestling with scattered UX efforts and slipping impact during growth, adapting JTBD with a management mindset could be the strategic framework your team needs to stay focused and move fast—without breaking under scale.