Product details
Platforms
iOS (future Android release)
Web - Desktop, Mobile
User Types
Studios, Networks, Product Companies (SNPCs)
Supporting Businesses & Vendors (SBs)
Freelancers (Talent)
Feature set
Security
Single Sign On
Two Factor Authentication
Production Management
Create & Edit a Production
Production Dashboard
Add & Manage Admin Users
Manage Admin Permission Tiers
Staff a Production
Org Chart Creation, Customization, & Export
AI-Powered Staffing Suggestions
File Upload & Management
Group Messaging within Productions
Collapsible, Anchored Sidebar
User Calendar
Collapsible Messaging Windows
Social
Social Feed (including local discovery, Featured tab)
Social Posting & Commenting
Photo & Video Upload
Messaging
Account Creation
New User Onboarding (distinct flows for SNPC, SB, or Talent)
User Dashboard (distinct for SNPC, SB, or Talent; separate from Production Dashboard)
Company & User Profile
Create a Profile (distinct for SNPC, SB, or Talent)
Upload & Edit Media
IMDB Integration
User Calendar & Availability Management
Networking
Add Connections
Follow Profiles
Write a Review
Write or Request a Referral
Message Requests (Approve/Deny)
Search & Filtering
Location-Based Search & Discovery
Search Filtering
Account Management
Premium Subscription Tier
Payment Processing (separate ApplePay & web payment flows)
Push Notifications

UI completed by separate designer
We commenced initial legwork on ShoBizzy through a full-day client product & design workshop, from which we distilled user personas, a feature wishlist, and began the process of scoping and prioritizing those features using a MoSCoW method. From there, we spent additional sessions with the ShoBizzy team further honing the feature set through Effort/Impact Matrices. Each feature was individually weighed and prioritized on a matrix consisting along two axes: 1) level of impact on users (how critical is this feature to the product’s value proposition for each user type?) and 2) engineering and design lift (based on consults with engineering on frameworks, integrations, and dev time). Features that were desirable, but not feasible due to constraining factors such as budget and/or launch target were tabled for a later V2 release or beyond. Selected features were additionally filtered based on which platforms they would be accessible on at launch (i.e. SNPC users could create org charts on desktop web, but not mobile web), with the intent that all features would eventually be extended across all platforms where possible. Based on the feature set, I worked with ShoBizzy to map each user flow by user type and worked in sprints to then complete the UX phase, beginning with high fidelity wireframes, interactive prototyping, and user testing completed on both the agency and client sides. During the UX process, an additional designer was eventually brought on to aid with completion of the wireframes and to assist with handoff to a separate designer working on UI and engineering handoff.
User personas (Studios, Networks, Production Companies)
User persona (Supporting Businesses & Vendors)
User persona (Freelancer)
Feature prioritization



Feature environment mapping

In order to fully iterate and finalize a user flow across each platform of the app, a number of relationships first needed to be defined as they impacted areas of the app related to networking, production management, and the act of assigning admin roles. Consulting with engineering, I assembled Entity Relationship Diagrams (ERDs) and minor user flow maps to ensure an accurate hierarchy of user and admin permissions. Once these details were sorted out, we were then able to assemble full user flow diagrams for each user type and for each subcategory of admin types.
Example of user flow on mobile app

Example of minor user flows representing different use cases of admin invitations


Please note that designs below are intended as examples and are not exhaustive. I created all UX components shown below, apart from native iOS components sourced from open source community files










Example of fidelity of full app prototype interactivity (mobile UX)
As mentioned, UI on ShoBizzy was handled by a separate designer. Here are a few side-by-side examples of how UX designs translated to the UI phase before entering engineering. More examples of the final UI can be found on the ShoBizzy website or in the App Store, both linked in the Overview section of this page.







UI completed by separate designer