Conduct lets you describe the day you already understand, then decide how the people in your life should be able to reach you as that day changes.
Morning. Work. Evening. Sleep. Jackie can always call. Mike can call during Work and message in the Evening. School can break through a meeting. The apps become channels beneath those human decisions.
Time + Relationship + Access
Now2:30PM
2:30 PM · Work
Your coworker's group chat can wait. A newsletter can wait. Your friend's meme can wait. Your child's school calls. That comes through.
You did not configure four apps. You told Conduct who should be able to reach you during Work.
Conduct starts with two things people already understand: their day and the people in their life. It turns those human decisions into communication behavior.
The person is the primary object. Time is the context. Calls, messages, email, and participating apps become ways that relationship can reach you.
Describe the life, not the machinery
Start with “Who should reach me during Work?” Conduct translates that answer into the settings underneath.
One access decision, quieter channels included
If Jackie can call, she can also message or email. The system does not ask you to grant the same relationship repeatedly.
One continuous day
Morning becomes Work, Work becomes Evening, and Evening becomes Sleep. Access changes on the same timeline instead of living in separate policy containers.
The person comes before the app
One relationship policy can guide every participating channel where platform capabilities, APIs, identity resolution, and user permissions allow.
Design Principle
“This is my day. These are my people. This is how they should be able to reach me. Conduct handles the rest.”
Conduct begins with one continuous day: Morning, Work, Evening, and Sleep. Shape the time blocks once, then decide how the people in your life can reach you as that day changes.
Personal time before work begins. Close contacts only — a quiet start before the day opens up.
Professional tier. Colleagues, clients, and critical family — the people whose calls genuinely can't wait.
Social and family time. The widest personal access of the day — the people you actually want to hear from.
Near-total filter. Only true emergencies from a carefully chosen handful of people break through.
After weekday setup, Conduct asks if your weekend looks different — and offers an identical ring to adjust or copy from.
Tap any segment of the ring to mark it as personal time. These blocks layer on top of any existing structure.
9-to-5 Weekday, Shift Worker, and Freelance Flexible — pre-populated Day Objects for users who want a starting point.
Drag any white boundary handle to resize a block. Tap a segment to select it. Use + to add a block, − to remove the selected one.
Conduct walks through your day in order and asks about people, not apps. Jackie may always be close. School may call during Work. Mike may message in the morning, call during Work, and wait after hours.
Call access includes messages and email. Message access includes email. The technical tiers stay underneath; the visible decision remains human and clear.
Access Matrix — Sample Configuration
Hover any badge to see which channels are included.
"Set access once at the top. Everything below it falls into place."
Choose a real situation and watch one relationship decision travel through the system. The cascade is the machinery underneath—not another task for the user.
Whitelist-First
Conduct grants access explicitly for each relationship and part of the day. Anything not granted stays quiet.
Access Implies Access
Call access automatically includes messages and email. One decision covers all channels — no per-app drift.
Daytime Adds, Nighttime Subtracts
Morning→Work asks who to add. Evening→Sleep asks who to remove. The question direction follows the shape of the day.
People Before Apps
One relationship policy can guide participating channels where platform APIs, identity matching, and user permissions allow.
Smart Defaults
Conduct may suggest starting points on device, but the user confirms every lasting access decision. Inference never silently becomes policy.
Trace a Notification
← Select a scenario to trace
"The system asks the right question at the right moment — so you never have to think about what you forgot."
Tap a time block to see the people and access rules active at that moment. The interface makes the day legible without forcing users to rebuild the same policy app by app.
iOS Settings View — Tap any block to explore
Your Day — Wednesday
Quick Quiet
Apps — Work
Quick Quiet
Apps — Work
Design Decisions
Always Chronological
Morning. Work. Evening. Sleep — shown in the order the day actually unfolds.
Categories, Not Lists
Communication channels are grouped by what the user is trying to allow. Supported apps can participate without repeated person-by-person setup.
Dial for Time Nudges
A round dial bumps any block boundary in 15-min increments — no re-entering setup required.
Status Bar Presence
The active block name lives in the status bar — replacing the Focus dot with something meaningful.
Tap any block in the mock
Drill into tier breakdowns and app settings — the same hierarchy a user navigates on device.
Conduct keeps one access policy attached to the person. Supported communication channels can follow that policy where platform capabilities, APIs, identity resolution, and user permissions allow.
Participating Channels
Smart Contact Lists
A person can carry a labeled access policy across the parts of the day. Contacts can expose that policy wherever the platform permits.
In-Card Access Control
Open any contact card and a "Conduct Access" row shows their tier across every block — editable directly from within the card, without opening Settings.
The Conduct API
Participating apps can request the current access decision through a Conduct integration. Exact control depends on each platform, its APIs, verified identity, and the user's permission.
“Choose access once. Let supported channels follow the relationship.”
Sometimes you need quiet now, without reconfiguring your life. Quick Quiet temporarily overrides the day for a chosen duration, then returns to the access policy already in place.
Accessible from Lock Screen, Control Center, and Conduct settings — wherever you are when you need quiet.
Five timer options from 15 minutes to indefinite. The "Until I End It" option is for the times you can't predict when you'll be ready.
When the timer ends, your normal block rules resume. No action required. The system just picks up where it left off.
Pause for how long?
Apple Focus is a powerful mode-based interruption system. It supports people and app allow or silence lists, schedules, exceptions, filters, status sharing, cross-device behavior, and intelligent prioritization. Conduct explores a different primary question.
Focus: “Given what I’m doing, which people and apps may interrupt?”
Conduct: “Given this part of my day, how should this person reach me?”
One continuous access policy follows the day, so the right communication changes without another round of configuration.
The day as it unfolds
Jackie texts. Jackie has message access in Morning, so it comes through immediately. A colleague group chat waits until Work begins.
Work block activates. The colleague group chat that was held since 6:45am delivers its queued notifications. You read them when you're ready — not when they arrived.
Child's school calls mid-meeting. School has call access during Work, so it rings through while lower-access communication remains quiet.
Unknown number calls. Not in any Work tier. Conduct silences it — no ring, no vibration, no badge. Goes straight to voicemail without interrupting your afternoon.
Evening activates. The day's queued notifications arrive — the afternoon Slack threads, the newsletter, the group chat from this morning. All at once, on your terms.
Sleep activates. Only three contacts can call. Everything else is completely silent until morning. The system didn't ask you to manage anything — it just did what you told it your life looked like.
"The system didn't ask the user to manage their notifications. It asked them to describe their life — and then managed the notifications for them."
Most communication systems expose their own structure: apps, modes, channels, permissions, exceptions, and rules. The person has to translate a human outcome into the system’s vocabulary.
Conduct reverses the brief. Describe the day. Name the people. Choose how they may reach you. The software handles the machinery underneath.
Conduct is a Workshop concept: a concrete demonstration of what changes when product design begins with a human outcome instead of the machinery a platform exposes.
MMWB applies that same lens to existing products and new software: preserve what works, expose less friction, and make the system carry more of the burden.
How we work
Start from the human.
Every brief starts with behavior, not requirements. We ask what the user actually experiences before we ask what the product should do.
Work outward.
The system is designed from the inside out — logic first, interface second, technology last. It keeps the experience coherent under pressure.
Ship something leagues ahead.
We don't optimize existing patterns. We find the version users didn't know was possible — then make it inevitable.
Start a conversation.
Tell us what you're building, where the experience is breaking down, or where the idea still feels fuzzy. We'll bring the same level of clarity, structure, and product thinking you just saw on this page.
Common starting points