Overview
Independent bands manage routing, lodging, venue contacts, schedules, production, hospitality, and payouts without professional support staff. Having lived that workflow as a touring musician, I used the project to explore a question I knew firsthand:
How might a product free critical tour knowledge trapped in one band member’s head without recreating heavyweight professional tour-management software?
I began by assuming the planner needed better organizing tools. Assumption mapping, competitive research, proto-personas, journey mapping, archival touring artifacts, and implementation gradually exposed a broader problem: the band needed one current source of truth, while less-experienced users also needed help understanding what should exist in that record at all.

Problem
Independent bands run professional logistics on texts, spreadsheets, and one person’s memory
A multi-date tour is an operations problem without an operations staff.
Venue details live in email. Changes happen in group texts. Routing sits in spreadsheets. Lodging may exist only in somebody’s notes. Production requirements are repeated from venue to venue, while show-specific answers change every night.
The most organized member becomes the unofficial tour manager—and eventually the human interface everyone queries for information that already exists somewhere.
A dropped detail costs more than inconvenience
A missing load-in time makes a band late. An unclear payout becomes a settlement dispute. A lodging gap becomes an unexpected expense. Off the road, members coordinate jobs, families, transportation, and other commitments around dates planned months earlier, so uncertainty affects people who may never touch the planning workflow themselves.

Insight
I started by solving for the planner and found a band-wide information problem
I entered with deep domain familiarity, which was useful and dangerous: I already had opinions about how touring works.
Rather than treat those opinions as research findings, I separated what I knew from what I was assuming. I used direct experience, archival artifacts and competitive research to build explicit hypotheses, then modeled relationships to tour information through proto-personas and journey maps.
.png)
I built my research on direct personal experience in the touring music industry and by building personas representing three distinct user roles. My initial assumption was that the core design challenge was helping band leaders plan more efficiently; after examining the full range of users, I found that the deeper problem is one of shared visibility and information access. While one person assumes the burden of logistics, the rest of the band operates with incomplete information and no structured way to stay current.

The band didn’t have an organization problem; it had a distribution problem
The planner wasn't necessarily failing to collect information. Access failed because everyone depended on that person's availability. The product therefore shifted from helping one person organize a tour to giving the whole band one shared operational truth.
Experienced tourers carry an internal checklist of what makes a date ready, while newer musicians don't know which missing detail matters. DaySheet needed to be fast enough for experts and structured enough to carry some of that expertise itself.

Jobs to be done: When tour information changes, a self-managed band needs one current record that shows what is known, what is missing, and what each person needs next—without routing every question through the planner.
Who I designed for

Laci
Parent decision-makers comparing options, needing clarity, trust, and predictable next steps.

Josef
Long-time expert who knows the system deeply but struggles with UI drift and lack of standardization.

Andrew
Buyer researching company online to assess credibility, clarity, and whether product answers their pain points.

Jan
Parent researching cabins, amenities, prices, and driving logistics; juggling seasonal availability and family needs.

Dana
Coordinates setup while keeping an active medical practice running. She repeats information across forms, returns lengthy fax packets, and schedules training around staff and patient demands.

Evan
An experienced musician who absorbed planning because somebody had to. He needs to maintain the tour without becoming the human lookup table for everyone else.

João
An adult looking for fitness or self-protection training; often skeptical and needs assurance before committing.

Priya
Daily user entering procedure data, relying on clarity, consistency, and speed under time pressure.

Claudia
Hospital staff user seeking training, docs, or cert materials; needs stable content and clear navigation.

Jordan
Individual wanting simplicity, clear booking flows, and trustworthy info; browses on mobile and books quickly.

Marcus
Delivers the same foundational lessons through five scheduled sessions per client. Calendar coordination and repeated instruction leave less time for difficult workflows and individual questions.

Riley
An experienced member who depends on the itinerary but doesn't maintain it. Reliable dates and changes matter because touring commitments intersect with work and family obligations.

Ron
The internal user who relies on tried and true workflows, less chaos, and predictable communication.

Scott
Spends too much time rebuilding redundant patterns and troubleshooting bugs caused by inconsistent markup.

Dan
Internal employee updating pages, syncing with devs, and needing stable IA and predictable site governance.

Steve
Internal user who needs consistent branding and a site within platform constraints without operational friction.

Elena
Collects, checks, and redistributes faxed enrollment materials. Duplicate questions, unnecessary return pages, and incomplete packets create repeated follow-up and manual routing.

Theo
A musician booking an early tour without an experienced road manager's accumulated knowledge. He needs the product to expose what's missing rather than assume that expertise already exists.
Decision
A flexible workspace, a lighter tour manager, or a guided model?
Evan maintains the tour, Riley depends on it, and Theo doesn't yet know what complete looks like. Their journey maps produced four working requirements: shared read access, visible missing information, fast day-of retrieval, and guidance that doesn't slow experienced users.

These remained hypotheses to test. The synthesis pointed toward structure, but too much could recreate the heavyweight touring software independent bands avoid. I considered three approaches:
- Flexible workspace — Let bands configure their own fields, views, statuses, and workflow, like a purpose-built Notion template.
- Simplified tour manager — Provide fixed itinerary, lodging, routing, contact, and expense modules while leaving readiness decisions to users.
- Guided tour model — Structure the product around Tour → Date → Advance, with readiness states determined by the information entered.
Design tension: Experienced tourers needed speed and flexibility, while first-timers needed the interface to reveal what they didn't yet know.
With the guided model, I made structure do the teaching
I chose the guided model. A blank workspace would maximize flexibility but transfer the burden of defining a good touring workflow onto the user. That helps the expert who already has a system and hurts the first-time tourer who needs the most support. DaySheet instead exposes a small set of meaningful states: Needs Info, Ready, and Confirmed.
Build
Product Model
I modeled the product before I designed its screens
The guided concept required an underlying model that explains both what a tour contains and what makes a show ready. I defined Tour → Date → Advance, then grouped requirements such as venue, contacts, schedule, lodging, routing, production, hospitality, and business. Readiness comes from that information rather than a manually chosen label.



Interaction
I turned the model into behaviors, not just pages
Low-fidelity flows concentrated on the riskiest interactions before visual styling:
- finding what matters today;
- recognizing an incomplete date;
- understanding why confirmation is blocked;
- navigating directly to missing information;
- asking another person for information;
- reviewing a meaningful change.
Status describes product state; it is not a user-controlled tag. Missing required information should expose the blocker and the shortest useful next step rather than let somebody declare the date complete anyway.


Interface System
I designed for a parking lot, not a desk
The interface prioritizes what matters now instead of exposing every planning control at once. Text, icons, shape, contrast, and shared component states keep the system legible under distraction, poor light, and unreliable connections.


Read the design system docs
Following the Atomic Design framework, I documented the visual components and token in a standalone page. Behind the scenes, this single source-of-truth represents the building blocks of both the visual language and the front-end code for developer handoff.
Prototype
I prototyped the hypothesis, not the whole product
The first interactive version tested whether users could recognize missing information and recover from blocked confirmation. Successive iterations made the prototype substantially more stateful. A separate test rig can change the current person, date, time, connectivity, theme and completeness of the sample data. That changed the research question from "Can someone click through the proposed interface?" to "Does the underlying model remain understandable when users create, modify and break its state themselves?"



Try the prototype
The final prototype is deliberately narrower than a production application but deeper than a click-through demonstration. The user can switch roles, move through the tour, change the simulated date or time, or follow the suggested tasks to stress-test different states.
Delivery
I served the prototype from Github
Lorem ipsum

My expertise was also my bias, so I governed it like a stakeholder
I kept assumptions visible, designing the evaluation to attack the product model rather than reward the decisions I had already made. Each iteration turned another assumption into a condition the prototype could challenge. I treated domain expertise as an input, not evidence.

Validation
The evaluation tests whether the structure teaches
Before the final iteration, I ran a structured simulated usability evaluation across seven end-to-end tasks. I concentrated testing effort around the assumptions that could meaningfully fail:
- Can users understand readiness without a planner explaining it?
- Can missing information become collaborative work instead of another text message?
- Can different people work from one record without receiving identical access?
- Can changes remain trustworthy after the original information has moved?
- Can Today function as an active operational surface rather than a static itinerary?
Ten tester personas represented different touring experience, roles, devices and accessibility conditions. The method was useful for exhaustive coverage, boundary testing, accessibility review and consistent bug reproduction.


The evaluation surfaced dozens of issues, but I separated them into three categories, preventing the study from becoming an undifferentiated bug backlog:
- P0: Fix before another round — problems that masked the intended interaction or created accessibility failures.
- P1: Iterate and retest — design-model questions such as requests, confirmation semantics and post-midnight behavior.
- P2: Keep as future product research — deeper touring cases such as multiple full shows in one day, multi-night lodging, timezones, customizable required sets and richer settlement workflows.


Impact
The most useful outcome was evidence that changed the product
The study produced evidence strong enough to distinguish what was already working from what needed redesign. The live Today experience, derived readiness and blocked-confirm recovery survived the evaluation. The collaboration model did not. That failure was more useful than a uniformly positive usability score because it exposed a flawed assumption early enough to change the architecture.

Did the design answer the needs I started with?
The longer-term measure I would now use is not simply ask rate. People will always need to coordinate. A better north-star behavior is:
Out-of-band ask rate: how often does somebody still have to leave DaySheet—through text, phone, email or memory—to resolve an operational question?
The product succeeds when necessary coordination remains attached to the shared record.


What changed for them

Laci
The site clarified programs and offered a transparent flow for onboarding. Messaging is now timely and consistent.

Josef
UI improvements did not require downtime nor slow or interfere with established, familiar user experience.

Andrew
Company web presence looks both mature and current. Clearer IA made product info easy to understand.

Jan
New listing layouts show key differences clearly, even links to nearby amenities. Cabin search can filter by preferences.

Dana
A coordinated onboarding path reduced repeated paperwork and clarified each next step. Self-paced videos and training let her prepare staff around the practice schedule and become operational sooner.

Evan
Can scan which dates still need attention without manually auditing every record.

João
Onboard sequences and ready content reduced anxiety by setting expectations with guided flows and clear next steps.

Priya
Even with a new look-and-feel, everything was in its familiar place with no difficult renderings or legibility.

Claudia
Training, docs, cert materials now live in stable locations. No more relearning how a site decided to rebuild itself.

Jordan
Simplified steps and cleaner UI removed avoidable friction. Calendars and real-time status made booking state easier to understand.

Marcus
Reusable lessons, quizzes, and sandbox exercises moved foundational instruction into self-service. Marcus could focus live support on questions, exceptions, and complex client workflows.

Riley
Can retrieve current tour details without routing the question through the planner.

Ron
The automated workflow eliminated repetitive outreach, improved reliability, and produced social media content faster.

Scott
Delegating front-end code ownership and reusing components from a single source of truth eliminated redundant effort.

Dan
By delegating ownership, devs no longer bottleneck updates or releases for even small content updates.

Steve
The CMS model made content edits easy and improved SEO. Less manual work is needed to book a guest.

Elena
Consolidated intake and clearer fax-back requirements reduced duplicate requests and unnecessary pages. More complete submissions moved through the organization with less manual follow-up.

Theo
Can see which information a show still requires instead of relying on experience they do not yet have.
Reflection
A familiar logistics problem became a lesson about expertise
DaySheet began with a problem I knew firsthand and became a broader lesson about designing systems around tacit knowledge. Products often assume users already understand the process the software supports. That becomes risky when inexperience itself is part of the failure mode.
An experienced tour manager sees an incomplete show and mentally recognizes what is dangerous. A first-time tourer sees blank fields. The durable principle became: When inexperience creates risk, do not merely document the expert’s checklist. Encode useful parts of it into the product. For DaySheet, that meant deriving readiness, exposing missing information, explaining specialized language, blocking false completion, preserving meaningful changes and making coordination part of the record.
What I'd do differently next time...
If I continued the concept, I would widen the evidence before widening the product:
- Recruit outside my music network. Different touring models may operate under very different assumptions.
- Stress-test the object model. Fly dates, split bills, festivals, and irregular routing would reveal where Tour → Date → Advance needs to bend.
- Test financial workflows earlier. Money introduces permissions, privacy, trust, and settlement questions that may matter more than itinerary management.
- Instrument the ask rate. The product succeeds when information stops traveling through one person.
- Validate demand separately from usability. A usable concept isn't automatically viable; the next phase should determine whether the problem is frequent and painful enough to change existing workflows.

