A mobile diagnostic tool that helps professional artists identify exactly where their studio is bleeding time and energy, before they book a consultation.
This prototype demonstrates how 5 questions and an AI photo analysis can help clients discover what needs fixing in their process before an initial conversation happens.
Concept, UX/UI, Figma Prototype (Solo)
Figma, AI Vision Analysis
Working mobile prototype
Creative studios lose significant time not to bad work but to bad process. Fragmented tools, unclear handoffs, and workflows that grew around workarounds nobody questions anymore.
Studio teams of 2 to 8 people: designers, producers, and assistants working across multiple concurrent projects with no shared operating system.
Product Designer leading end-to-end workflow diagnosis and system redesign.
Designed a structured digital operating system across Notion, Miro, and Figma. Clear information architecture, defined handoff points, and a client-facing intake tool that replaced ad hoc onboarding.
35% reduction in project cycle time. Teams stopped losing work to process friction and started spending that time on the actual work.
After a year of redesigning artist studios, I needed a way to give potential clients immediate insight into what was broken — and to show them I already understood their situation before they booked a call.
A mobile first diagnostic tool combining five questions with AI powered photo analysis of the physical studio space. Results in under five minutes. Two paths forward: schedule a consultation or download the full report.
The Studio Framework grew out of a year spent working directly inside professional artist studios, mapping how people actually move through their space, where they lose materials, where instructions break down between artist and assistant, where deadlines slip because nothing is written down anywhere.
The trigger for this tool was a photograph. A client sent me a picture of her studio before our first session. That single image told me more about what needed fixing than anything she had said in conversation. I could see where things were going, how the space was organized against how she actually worked. From that point, getting a photo wasn’t a nice-to-have, it was essential.
But asking every potential client to send me a photo cold, without context, wasn’t a real intake process. I needed a structured entry point: something that gave them immediate value, surfaced their pain points in their own words, and brought me the visual evidence I needed, all before we’d spoken once.
The flow is linear by design. One screen at a time, one decision at a time. The entire experience is built around one principle: make it so easy to continue that stopping feels like the strange choice.
The visual system came directly from The Studio Framework website. Pastel gray tones, generous white space, a neutral palette. Artists are visually opinionated — a tool with too much personality risks feeling like it belongs to someone else’s sensibility. The yellow button is the single point of contrast. It carries all the conversion weight precisely because nothing else competes with it.
Visual hierarchy as conversion strategy — one button gets the yellow, one stays quiet.
Question validation and photo retry logic are the most important things missing. A user who uploads an unusable photo currently has no recovery path. First thing to fix in the production build.
The scheduler in the prototype is static. Connecting it to an actual calendar and automating the report delivery email turns this from a design artifact into a working business tool.
One session was enough to catch the photo screen problem. It was not enough to validate the question set, the results framing, or whether the CTA hierarchy reads the way it was designed to.
The five questions are scaffolding. What makes this different from a contact form is the AI analysis of the studio image. In the next version, the photo result should be its own diagnostic layer — not bundled with the questionnaire output.