IXD 105 · UX Concept · Mobile Prototype

SharedStandard

Shared standards for shared spaces.

SharedStandard is a mobile concept for making shared chore expectations explicit. Roommates define what a chore includes, choose its timing, and review the agreement together.

Start the Figma prototype at onboarding

My contribution

I conducted 5 of the team’s 7 interview sessions and 2 contextual inquiries.

I developed the concept and design guide and contributed significant wireframe and prototype work within our three-person team.

Four SharedStandard screens fitted inside phone mockups: Home, chore selection, definition of done, and confirmation.

The problem was not chores. It was ambiguity.

SharedStandard was designed for young adult roommates living in shared housing, where conflict around chores often comes from unspoken expectations rather than a lack of care. In shared spaces like kitchens and bathrooms, people regularly assume they are on the same page, but their standards for what counts as done can be very different.

The concept helps roommates create a shared definition of done, pair it with a timing rule, confirm agreement together, and reduce the need for repeated reminders.

Small mismatches repeated until they became social tension

Research showed that unclear expectations turn practical issues like dishes, counters, or bathroom cleanup into recurring interpersonal tension. In many shared homes, expectations stay implied rather than written down, and once one person feels forced to remind another more than once, the interaction quickly starts to feel like nagging.

“If I send one reminder, that should be enough, and beyond that it feels like nagging.”

My research into shared-space expectations

Our research narrowed from broader roommate coordination to the different expectations people brought to shared spaces.

My research contribution

  • I conducted 5 of the team’s 7 interview sessions.
  • I completed 2 contextual inquiries, one on-site and one remote, alongside contextual observations.

Team research scope

Across the team, we conducted 6 individual interview sessions and 1 two-person session.

These counts refer to sessions, not unique participants.

What our research suggested

  • Completion meant different things. People could finish a chore and still disagree about the result. Dishwasher loading was a specific example.
  • Reminders could feel personal. Repeated follow-ups created social discomfort.
  • Existing routines mattered. Some households used chat or a whiteboard successfully; other calendars went unchecked.

Choosing a shared definition of done

I chose the Shared Standard Reset concept to focus on expectation alignment. The other concepts explored contribution visibility and routine cues. I made a shared definition of done the centre of the interaction so roommates could discuss the expected result before agreeing to a task.

From research to refinement

  1. 01

    Research

    I conducted five of our seven interview sessions and both contextual inquiries to understand how roommates coordinated shared spaces.

  2. 02

    Synthesis

    Our synthesis identified mismatched definitions of done, discomfort with repeated reminders, and the importance of existing household routines.

  3. 03

    Opportunity gap

    Existing tools supported assignment and scheduling, but did not help roommates align on what a completed shared-space task actually meant.

  4. 04

    Concept narrowing

    I chose Shared Standard Reset to focus on expectation alignment and developed the concept around a shared definition of done.

  5. 05

    Wireframes and wireflow

    I contributed substantial wireframe work to the shared project. Our sketches explored the sequence of a shared space, chore criteria, and agreement.

  6. 06

    Prototype

    I created the design guide and contributed significant prototype work. The final mobile prototype includes shared work from our three-person team.

  7. 07

    Usability testing

    The evaluative summary documents four moderated think-aloud tests. I completed two follow-up tests after that round; those notes are not currently available.

  8. 08

    Iteration

    Testing identified priorities for clearer wording, visible examples, easier editing, and brief completion steps. The effect of those refinements still needs evaluation.

From rough ideas to a working flow

I developed the concept and design guide, then contributed substantial wireframe and prototype work to make the agreement tangible. The early sketches and final prototype also include shared team work.

A consistent language for shared tasks

I created the design guide to give our screens a consistent reference. I used a neutral base, green actions, and Inter to support a calm tone, and defined spacing, action hierarchy, status labels, and input feedback.

Colour

Give actions a clear emphasis

Green marks primary actions, while white and pale grey separate content. Warning, information, and error states have their own colours.

Components

Make status visible

Buttons, status chips, and form feedback distinguish an available action, a pending agreement, and an error that needs attention.

Layout

Keep the structure predictable

The guide specifies Inter, an 8-point spacing system, 12-pixel card corners, and a 48-pixel minimum tap target.

Full original design guide showing the colour palette, Inter type scale, spacing rules, and component states. View full size
My original project design guide

A spaces first tool built around alignment, timing, and light touch accountability

The final concept was a mobile first shared household tool organized by spaces. Rather than using points, surveillance, or gamification, it focused on making expectations explicit and helping roommates coordinate with less friction.

Define the standard

Roommates choose a space and chore, then define what done means through a short checklist.

Set a timing rule

The app pairs each standard with a timing expectation so the routine is clear, not assumed.

Keep reminders gentle

A shared agreement and one gentle reminder are intended to reduce repeated, emotionally loaded follow-up.

Three SharedStandard mockups showing the definition of done, a custom date and time, and a reminder.

Core prototype flows

Browse standards by space
Choose a chore
Define what done means
Set a timing rule
Confirm agreement together
Receive a reminder
Mark done
Update the standard if it fails

How a shared agreement takes shape

Four moments in the SharedStandard flow connect the space, the task, the timing, and the people involved.

  1. 01

    Start with the shared space

    The home screen groups standards by room. Due and recent items sit below the spaces, so the starting point is the part of the home that needs attention.

    Organize around a place roommates already share.

    View screen full size
    Home screen with kitchen, bathroom, entryway, living room, laundry, due standards, and recent activity.
  2. 02

    Agree on what done means

    A short checklist turns “clean the kitchen” into specific actions. Suggested items give roommates a starting point they can adjust together.

    Replace an open-ended expectation with visible criteria.

    View screen full size
    Dishes reset checklist defining what done means, with Continue and Cancel actions.
  3. 03

    Make the timing explicit

    A date and time sit alongside the standard. This makes the timing part of the agreement instead of another assumption to negotiate later.

    Connect the definition of done to a clear time.

    View screen full size
    Timing options for a shared standard, including tonight, within 24 hours, Sunday evening, and a custom deadline.
  4. 04

    Show who has agreed

    The confirmation screen brings the task, timing, and agreement status together. “Agreed” and “Pending” distinguish the creator’s decision from the roommate’s response.

    Sending a standard is different from everyone agreeing to it.

    View screen full size
    Confirmation screen showing You as Agreed and Alex as Pending, with an action to send the standard for review.

Portfolio refinement of the IXD 105 screens. The usability findings below refer to the original coursework prototype.

Individual work · IXD 203 · Later development

Motion that explains what just changed

I returned to SharedStandard to explore how motion could make the agreement flow easier to follow. I focused on three moments: opening a standard, setting a custom deadline, and sending a proposal for review.

These studies build on the earlier team prototype and were developed separately from its usability testing.

01 / Keep the context

Connect the choice to its details

I kept the selected Dishes card visible as it moves into the checklist view. The criteria then appear beneath it, connecting the new details to the standard just selected.

02 / Reveal what is needed

Make room for a custom deadline

Choosing Custom opens the day and time controls within the timing screen. After Apply deadline, the controls collapse and the proposed deadline stays visible for review.

03 / Show the handoff

Show who needs to respond

I used a moving document to show the proposal travelling to the other roommate. The amber state and “Sent. Waiting for approval.” message confirm the handoff while keeping their approval pending.

Testing clarified what needed refinement

The team’s evaluative summary documents 4 moderated think-aloud tests. I completed 2 follow-up tests after the initial round. Those follow-up notes are not currently available, so I am not claiming a measured improvement from those sessions.

What testing revealed

  • The idea felt relevant and useful
  • The word “standard” felt abstract without support
  • Users wanted templates instead of blank input fields
  • Edit and update actions needed to be easier to find
  • The flow had to stay short and low effort

Priorities from testing

  • Keep examples and suggested checklist items prominent
  • Make the relationship between a chore, its criteria, and timing explicit
  • Give editing a clear, predictable entry point
  • Keep completion brief and test the value of each added step
  • Check whether roommates understand the pending agreement state

SharedStandard reframed chores as a communication design problem

The outcome was a prototype built around clear expectations and mutual agreement. These principles guided the design; their effect on everyday household conflict has not been measured.

  • One shared definition of done

    A short checklist gives everyone the same reference point.

    Clarity
  • One gentle reminder

    A single prompt keeps follow-up brief and predictable.

    Restraint
  • No points, rankings, or surveillance

    The concept centres on agreement between roommates.

    Autonomy

What this project taught me

I delivered the concept, design guide, and substantial wireframe and prototype work within a three-person team. I learned to make expectations tangible before asking people to agree. Next, I would test whether roommates can explain the pending state and update a standard without help.