
Project Summary
Usually the transfer of an object from point A to point B is pretty straightforward. But if it deviates and you’re stuck solving that problem on a time crunch, someone lending a helping hand can be crucial to that project’s success.
Sometimes that project is putting on a concert. Sometimes a situation arises and you have to suddenly switch roles and source some gear to fill an opening slot on a concert bill. If you happen to be unfamiliar with the marketplace in Point B, having quick access to that specific piece of gear you need right now is imperative. Because more than likely you have to fix this situation pronto.
If you’re lucky, you're an enthusiast of gear that lives in Jackson Hole, Wyoming who has a ton of gear sitting on the shelf not being used. Turns out someone else could pay you for access to it instead of it sitting there going unused.
I know from experience within the music industry that there is an opporunity here to help a series of users with the advent of one app and I wanted to know if my solution fills it.
My solution?
A mobile hub that alleviates the myriad of problems that spiral out of the lack of accessibility to musical equipment by way of renting.
Research
Kano Survey & Analysis
Personas
Conceptual Evaluations
The School Of Hard Knocks
Deliverables
Interactive prototype
Personas
Architecture Diagrams
Keynote presentation
My role
I completed this project on my own without a team. All research, analysis and design was done by me.
Users
A touring artist or crew member who needs a quick solution to a specific problem that requires new gear to be acquired ASAP to alleviate their newfound painpoint.
Methods
Competitor audit, user journey mapping, rapid feature ideation, contextual interview, Kano analysis, usability testing. Prototyping, design system.
Tools
Sketch, Figma, Google forms, Keynote, Zoom, Pen/Paper, iPhone
It all started with a little surprise opening gig…
One time, while on tour we suddenly learned the opening act had dropped off for the next night’s show. That happens from time to time. But there was a problem. On top of the show we had to put on that evening, we had to figure out 45 minutes of music for the next night.
The solution proposed was that myself and another member of the team open up the night of music instead. Which was cool! I put it on my Instagram (see above).
But both as the instrument tech and suddenly, the artist, I had to source the additional gear, an electric guitar and an amplifier, to make this gig happen.
But maybe there was someone in town who could have lent a hand? And maybe finding that helping hand could have been eased by a simple acquisition over a mobile app.
After the comparative analysis I created personas for the types of users that would benefit from this solution. I based them off countless conversations I’ve had with my musical peers throughout the years.
To be certain I was removing my bias and experience from this solution as best I could, I had a series of new interviews with other musicians, studio owners, and home enthusiasts. The amalgamation of all of this user data became Dwayne the Touring Musician & Jerry, the Studio Owner.
What user’s said…
“Location would be a critical aspect. Should be tour and travel handy ”
— Kano Survey Participant #4
“Profile info is good for accountability, especially as a femme - I wanna have an idea of who I am talking to/renting from and make sure it feels safe.”
— Kano Survey Participant #11
“Loaner is great. Rent to buy is good for some people”
— Kano Survey Participant #9
“I ain’t driving to Wisconsin”
— Kano Survey Participant #16
The Pitch
To wrap it all up, I created a 5 minute keynote based presentation to talk about what the problem was, how I identified the solution and where I would go from there.
Moving Forward
I ran a usability test on my prototype thanks to Maze and it generated some great insights on how I can make Loaner more functionally usable.
Also, I’ve begun thinking about the philosophical underpinnings of the app itself, for instance, is a “cart” the vessel one loans in? I’m not sure.
I’m continuing to build out features and consult with a team of developers as we bring this MVP to life.