Why the add-chore button asks who first, not what
The NestBoard team · 2026-07-18
When you tap to add a new chore in NestBoard, we ask who it's for before asking what it is. That sequence isn't accidental—it's a small choice that says something bigger.
Most task apps start with the task itself. You type "take out trash" or "vacuum living room," then somewhere down the line you assign it to someone. The work comes first. The person is a detail you fill in later.
We reversed that order.
The person is the starting point
When you hit the add-chore button, the first thing you see is your household roster. You pick a person, then you describe the task. It feels different because it is different.
Starting with "who" treats the task as something that belongs to a specific person from the very beginning. It's not a floating piece of work waiting to be assigned. It's Alex's chore, or Sam's responsibility, right from the first tap.
That shift matters in a shared household. Chores aren't abstract to-dos—they're part of how a family divides the labor of keeping a home running. The question isn't just "what needs doing?" It's "whose turn is it?" or "who's capable of this right now?"
Sequence shapes meaning
We noticed this during early testing. When we started with the task field, people would create the chore and then think about assignment. It felt managerial. One person was handing out work.
When we flipped it—person first, task second—the flow felt more conversational. You're thinking with someone in mind, not about work that needs delegating. Parents told us it made them more mindful about rotation. Teenagers said it felt less like being assigned homework.
The technical effort to reverse the order was trivial. The conceptual shift was significant.
It pairs with rotation
This sequence also sets up our chore rotation features more naturally. Once you've picked a person and defined the task, the next question—"should this rotate?"—makes immediate sense.
You're already in the mindset of "this is Jordan's chore this week." Asking "should it be Morgan's next week?" flows easily. If we'd started with a task description, rotation would feel like an advanced setting you bolt on later.
The same principle shows up elsewhere in NestBoard. When we redesigned how shared medication bottles work, we started with "who takes this?" before "how much?" Small sequences, big implications.
Not every app should do this
This pattern works for us because NestBoard is built around a household, not an individual. If you're designing a solo productivity app, leading with the task makes perfect sense. But in a family context, the relationships come first.
We're not saying our way is universal. We're saying the order you ask questions shapes how people think about the answer. And for a shared household, starting with the person felt right.