Two locations, one problem: too much calling and texting
Carol directs a nonprofit family homeless shelter — an organization with office staff working days and shelter staff covering nights, at two locations a few minutes apart. One manager was effectively reachable around the clock, and most day-to-day coordination happened the way it does at a lot of small organizations: texts, phone calls, whoever you could reach first.
Her goal going into this was specific: replace the scattered calling and texting with one place everyone already knows to check — for schedules, for updates on the families the shelter serves, for volunteer coordination — without making the tool itself something people need training to use.
What actually needs to move through the hub
Three streams of information run through Carol's organization at once, each with different access needs. Office staff track the needs of the families in the program — information that has to stay secure and visible only to the people who need it. Volunteer coordination is the opposite: contact information for the churches and groups signing up for weekly dinner shifts needs to be easy for the whole team to find, not locked away. And staff updates need to flow constantly enough that nobody is stuck guessing what happened on the shift before theirs.
That last point shaped the whole approach: not a place to check occasionally, but something closer to a live, ongoing record — one spot to look for whatever is currently true about the shelter, rather than reconstructing it from a chain of missed calls.
There's also a practical adoption constraint worth naming: not everyone on a team like this is equally comfortable with new software. Whatever the setup ends up looking like has to be simple enough for someone to pick up the app and understand it without a training session — which is part of why the plan started with the basics rather than the most advanced setup possible.
Step one: getting every task to actually show up in one place
The session started with a simple diagnosis: Carol had projects for her team, her board, and herself, plus a personal workspace with several sub-projects — but her Planner looked nearly empty. The tasks existed; they just didn't have due dates, which is the one thing that makes a task surface in My Planner automatically.
- Any task, in any project — personal or shared — with a due date shows up in My Planner. No separate sync step, no manual linking. Add a date, and it appears in the weekly or daily view.
- Text can become a task instantly. Highlight existing text and use "Turn into" → Task, or type the shortcut `( )` followed by a space to create one from scratch.
- Assigning a task to a teammate puts it on both planners. The assignee gets an email and, if they have the mobile app, a push notification — without a separate message having to be sent.
That single fix — assigning due dates to tasks that already existed — turned an empty Planner into a working one within the session, which is exactly the kind of change that matters more than any advanced feature for a team just getting started.
Organizing shared work across two shifts without piling everything into one project
For recurring things — an annual fundraiser, a seasonal event, anything that happens on a cycle — the cleaner pattern is a dedicated Space with one project per occurrence, rather than nesting a growing pile of sub-projects inside a single catch-all. It keeps a two-shift team's shared spaces scannable: a day-staff member and a night-staff member should each be able to find what they need without wading through everything the other has ever created.
Assigning tasks across that shared structure works the same way as inside a personal project: create it wherever the work naturally lives — a shared team project, a specific event's page, the tasks collection — and assign it to whoever owns it. They see it on their own Planner; Carol sees it on hers if she's the one who created or was assigned it.
What's next: a project-level planner and pulling in outside tools
Two things came up as the natural next step once the basics were in place. First, a planner scoped to an individual shared project — not just each person's personal one — so a whole team can see every task tied to that project, who owns it, and what's due, in one visual view rather than reconstructing it from individual planners.
Second, deeper AI integration via Claude, which Carol was already curious about — connecting inbox, calendar, and other day-to-day tools so that updates flow into xTiles on a schedule instead of being entered by hand, building toward the kind of live dashboard she described wanting from the very first question. That session was deliberately split in two: get the fundamentals — Planner, tasks, shared projects — solid first, then come back roughly a week later for the more advanced automation work once the basics were second nature.