CASTMI : Networking collaboration and outreach for actors and performers in the attention economy

Go Back to My Projects

Skills:

User research, interviewing, personas, wireframing, interface design, interaction design, prototyping, usability testing, UX writing, business strategy.

Table of Contents

Overview

Problem Statement

Scope and Constraints

Goals

Process

What Did I Learn?

TL;DR

• Problem: Content creators had a lot of down time but a hard time building an audience and networking.
• Solution: We developed the technology to write a script and have each line appear separately on screen on a reel. Enabling quick and easy content creation.
• I worked directly with the developer. My usual process was streamlined to make time and be able to be flexible with our time and for future iterations. Unfortunately, we only shipped it as a beta, working prototype published through the Apple Store.
• I conducted a competitive analysis, established some user journeys based on a small sample of 4 users (3 target users and one we would see as a passive user.) and began ideating collaboratively with the developer immediately:
• I drew out the site map and discussed with the developer…
• After a few card sorts, we iterated to a site map we found appropriate.
• We planned our road map on a needs and wants basis but overall got very ahead of ourselves with features that our users wanted.

Overview

We hoped to create MVP that utilized the script sharing to video recording process to enable talent to effortlessly create media and collaborate with others.

Inspired by overextended discussions on improv and gestalt theory, we developed the technology to write and display text and have it sectioned of between reels because we noticed actors preferred to have multiple takes, as it allow for more play and difference.

Our mission is to create a platform to engage performers into creating and collaborating

Problem Statement

The current social media options makes people passive participants, Tiktok user spend on average 95 minutes per day on the platform. The particular challenge we focused on was how this engagement damaging for actors and performers seeking new projects, as they spend a significant amount of time reaching out, self-marketing, and hoping for collaborations with other creators if they didn’t already have a following.

To address this issue, Castmi proposes an innovative solution that empowers creators with built-in writing tools and facilitates open and extensive collaborations, bridging the gap between potential collaborators.

My responsibilities: Business research, User research, wireframes, interface design, and brand design.

Collaboration with a developer, while I was the solo designer. We ran weekly meetings to update each other on progress and new discoveries.

Scope and Constraints

This project had a very limited budget for research, so I had to utilize free screenwriting software as well as other resources. We could only communicate remotely because we were in two different time zones 2 hours apart, working on this project part time. We organized our data and research through Notion and on Figma files.

Goals

1. Simplify the writing process for the user to create as many ideas as possible.
1. Content produces itself, work is minimal, and sub-communities naturally grow.
2. Make the recording process as approachable as possible.
1. Make a points system to display on profile. Gamification or vanity?
1. If its only vanity and not for any other purpose, we can leave it out.
2. Make recording yourself feel effortless. Add bold text for the on-screen scripts and removed the timer. The more confidence and less pressure, the better.
3. Emphasis supporting creators that people want to work with.
1. Create a networking through chat but also actively in the access to instantly collaborate on a script.

Process

A step-by-step run down of what you did and why you did it.

After working through some design iterations, the developer migrated to Firebase database to read the information architecture since main function is to transfer video data. He also wanted to make cloud integration seamless.

Note: We started the project under the name of “Parta”

This was the layout of the login screen before deciding to reduce the complexity and log users in via Apple ID for a few reasons:

• We were designing and developing for iOS only, using Xcode.
• Storing user data was adding to data storage we didn’t want to afford, in both cost and backend capability.

Task Flows

Site Maps

Outcomes & Result

We were able to eventually build a MVP that we were able to test with a few users.

Unfortunately, we ran of time and funds for the project and it will remain on the backburner in its current beta stage limbo.

What did I learn?

Collaboration is the solution.

Throughout this project, I was in direct contact with the developer and selling the importance of small design changes and pressing for him to slow down in order for me to test users on new changes. By being forced to make changes, we found great mediated solutions together.

K.I.S.S. (Keep it simple, silly.)

This lesson is reflective of the product as a whole and how large our scope grew as we kept developing. We began with a big concept but eventually came to the realization all we had to do is provide the minimum as a tool and platform and allow the users to create and use the tools creatively.

Perfection is a myth.

Getting a design done only gets extended because they are so many alternative solutions when one isn't working. Solutions need to be put into practice beyond the sanitation of the researchers’ and developers’ control and let users find their goals and intentions organically.

Start small, grow big.

Getting the developer in early at the designer stages will extend the product iteration designing process because I had to make constant changes because every new change makes a new feature which makes a new usability problem, which makes a new change, et cetera. When deadlines are not limited, budgets are nonexistent; the big picture gets infinitely bigger and without any restrictions the scope is endless.

Finally…

Importance of good user research!!

Without the effective user research, the large part of the hard work was ideating and iterating when things didn’t work. Too much iteration created a feature factory and eventually led to burn out on this project. If I had to do this project again, I would have followed Abraham Lincoln’s quote,

“If I had eight hours to chop down a tree, I’d spend six sharpening my axe.”

Thank you!~~