Studio OS Project Management Tool

Studio OS is a single-user, offline-first application that unifies the operational life of an independent creative professional: client projects and their revision rounds, deliverables with versioned client feedback, time and budget, invoicing and personal cashflow, and a personal layer of to-dos, habits, goals and journaling. It is built as a local-first PWA (data in the browser via IndexedDB, assets in the Origin Private File System) with optional CouchDB sync for true multi-device use.

This report documents the UX process behind the product: who it is for, what they need, how the design was researched and validated, and how the artifacts: personas, journey map, wireframes and prototype, connect to one another.

Download Case Study(1.1mB) →   View Full App →

User needs mapping

Independent creatives operate a whole business alone, yet their tooling is fragmented: a task app, a spreadsheet for money, scattered email/Figma feedback, and sticky notes for ideas. The needs below were distilled from the research in Section 3 and mapped to the underlying goal and the product response.

User research

Exploratory research

Goal: understand how solo creatives actually run their studios before committing to a solution.

Methods:

• Semi-structured interviews (n=6) with freelancers and 1–3 person studios across brand, web and design.
• Diary-style probe: participants logged every tool they touched during one client project.
• Competitive teardown of generic PM tools (Asana, Trello, Notion) and finance tools for freelancers.

Key findings:

• Tickets ≠ how creatives think. Work moves through phases and revision rounds, not flat task lists.
• Money clarity arrives too late. Profitability is discovered after a project, not during it; scope creep is rarely billed.
• Feedback is scattered. Version feedback lives in email, chat and design-tool comments simultaneously.
• Business and personal blur. “Is this project profitable?” and “can I pay rent?” are the same anxiety, answered in different apps.

Ownership matters. Several participants were wary of cloud lock-in and wanted their data portable.

Evaluative research

Goal: validate that the proposed model (phases, rounds, deliverables, unified finance) is usable and matches real workflows.

Method: moderated usability sessions on the working prototype, five core tasks, think-aloud, with a simple severity scale (1 cosmetic – 4 blocker).

Actions taken: margin surfaced in the budget header; goals were period-scoped to year/quarter; a mobile bottom tab bar plus a horizontal project switcher replaced the desktop sidebar on small screens.

Stakeholder mapping

Even a solo tool has a small constellation of stakeholders. Mapped here by their interest in the product and their influence over its success.

Power/interest read: the studio owner sits top-right (high power, high interest) and is the design north star; clients are mid-interest and engaged only at the feedback boundary, which is exactly where the service blueprint focuses.

Personas

Two personas, both 30–40 and running creative practices, bracket the audience: an established studio owner focused on profitability and control, and a freelancer-becoming-studio focused on stability and collaboration.

Persona 1

“I don’t need another to-do app. I need to know if this project is making money before it’s over.”

Persona 2

“Half my work happens on my phone between calls. If I can’t capture it there, it doesn’t exist.”

Journey mapping

End-to-end journey for Daniel running a fixed-fee client project through Studio OS — the product’s spine. Emotion is charted from low (✖) to high (✔).

Lo-fi wireframes

Low-fidelity layouts established structure and hierarchy before any styling, validating the information architecture (nav model, dashboard aggregation, project sections) cheaply.

Today (home) — structure

Lo-fi: left nav, greeting, four KPI cards, agenda, habits, goals, quick capture.

Project detail — structure

Lo-fi: phase pipeline, budget block, and the deliverables → version → feedback module (dashed = newly introduced flow).

Hi-fi wireframes & service blueprint

Hi-fi wireframes (Pop Block design system)

High-fidelity screens apply the “Pop Block” system: bone canvas, navy outlines with hard offset shadows, neon green for active/positive states, gold as a warm tertiary, and an editorial serif for headings. The Today screen below is also a static capture of the working prototype’s home.

Hi-fi: Today (home) — also the prototype’s live home screen.

Hi-fi: Project detail — phase pipeline, billing-aware budget, and the deliverables/versions/feedback module.

Service blueprint — client feedback on a deliverable

The one genuinely multi-actor flow. The blueprint adds the backstage to the journey: what the client sees (frontstage), what the studio owner does, and the systems beneath the line of visibility.

Where it pays off: the blueprint exposes that “client reviews” currently happens outside the app (email/link). That points directly at the next build — a read-only client review link — which the data model already supports.

Collaborative design

The product was built through tight designer–maker collaboration, mirroring how the studio owner already works with clients: propose options, select a direction, then iterate with precise feedback.

• Concept selection. Two design directions (“Acid Minimal” and “Pop Block”) were mocked statically and chosen from — Pop Block, with a refinement (bone sidebar + neon line).
• Structured choice points. Pillar priorities, finance modeling decisions, and personal-feature scope were each decided from a small set of options rather than open-ended.
• Iterative QA rounds. Each build was returned with root-cause feedback and integrated structurally, not patched — the same revision-round discipline the product encodes.

Production-ready increments. Every round delivered a complete, runnable artifact, keeping the prototype continuously testable.

Prototyping

The prototype is a working, self-contained PWA — not a clickable mock. It runs the real data model and interactions:

• Local-first storage: structured data in IndexedDB; uploaded assets in the Origin Private File System, with graceful fallbacks.
• Sync-native schema from line one: UUID keys, soft deletes, and an updatedAt on every record — designed for replication, not retrofitted.
• Optional multi-device sync via a self-hostable CouchDB adapter (last-write-wins on updatedAt, with conflict handling).
• Four areas — Today, Projects, Personal, Finance — with a mobile bottom-tab layout for small screens.

Because the prototype is real, evaluative research ran against actual behavior (persistence, timers, budgets, feedback threads) rather than a facsimile — making findings directly actionable.

Recommended next steps

1. Read-only client review link for deliverable versions (closes the frontstage gap in the blueprint).
2. Asset replication so files follow the user across devices, not just metadata.
3. Auto-sync (interval or on-change) layered over the existing manual sync.
4. Period-scoped goal labels surfacing the active window on the Today dashboard.

Prepared as a UX process report for Studio OS.

The final design delivers a funky yet minimal PM tool. The UX process was pivotal in streamlining the features that were developed,resulting in a smooth and intuitive interface.