1. Streamline engineering build time - mastering and implementing the Material Design m3 system for its compatibility with our engineers' existing stack
2. Manage overlapping events - timelines, vendors, and communications were often overlapped
3. Creating new events - allow the planners to create new events within the web app including templated relevant info
4. Manage single events - summary of events that allow management of vendors progress, payments, important links, tasks etc.
5. Vendor repository - the creation of vendor profiles on the application back end, removing the need to create new pitches tailored to every client
6. Build a home for design elements - emphasizing the fun grand visions instead of the tedious manual tasks
7. Assign unique event attributes - planner needed to be able to assign unique vendors, unique payment schedules and unique notes etc.
8. Category progress - review individual vendor categories for feedback and booking progress
9. Configure vendors for events - assign unique event attributes on top of the vendors general profile
10. Seamlessly integrate with the client facing app - components needed to be attached to their counterparts on the client app
11. Intuitive clickable prototypes - help streamline engineering build time and function as sales tool for vendor meetings
Step 1: PRD alignment with product team to establish user goals, table-stakes features, user scenarios, engineering constraints and timelines.
Step 2: Rigorous interview process with acquired planner to understand planning process
Step 3: Realigned with the team to adapt PRD, define user journey, and align on functional wire frames
Step 4: Designed wire frames to represent ~60% completion of product and include soft copy, layout, and notes to review with product team
Step 5: Integrated feedback into wireframes brining them to ~80% completion and introducing brand, draft copy, suggested components and final layout.
Step 6: Lead the team through a total of 17 hours of review, addressing ~180 labeled questions and adjusting to accommodate any engineering constraints
Step 7: Â Hi-fi delivery of full product (events tab, create new event, event page, create new vendor etc.) including executed notes, final components, final brand and icons etc.
Step 8: Work side-by-side with engineering across build to accommodate any necessary modifications and/or clarify any designs
Step 9: Deployed internal tool to testing environment and provided rigorous feedback and bugs, designs, and general usability.
Step 10: Deployed V1.0 and onboarded team to the product
Step 11: Established feedback loop with planner and deployed necessary adjustments based on user feedback
• Achieved a 75% reduction in planner team size by automating low impact/high effort tasks
• Transformed manual vendor pitching into an automated process with reusable proposal templates and customizable vendor options
• Enabled planners to manage event details from a single, centralized event hub
• Executed ~$750k of business through the internal planner tool in the first 3 months
• Created event templates that addressed key planner use cases, outperforming external project management tools and reducing financial overhead
• Consolidated scattered communication channels into a single hub, streamlining email, text, phone, meetings, and third-party apps
• Adopted the M3 native design system, outlining key constraints, and expediting engineering build time
%201.svg)
