Why we started Ophlow on the floor of an assisted living community

We started Ophlow in an assisted living community because that was where we could see the work up close. We wanted to understand how a day actually moves: what happens at the start of a shift, how a request reaches the right person, and what someone needs to know before taking over from a teammate.

The first step was to listen and shadow the operations team. We spent time alongside the people coordinating rooms, housekeeping, dining, maintenance, and activities. The goal was not to arrive with a finished product in mind. It was to learn which parts of the day felt harder than they needed to be, and why.

Following the work from one person to the next

It is easy to describe a task as a single item: clean a room, deliver a meal, fix a leak, or prepare an activity. In practice, each item passes through several hands. Someone notices what needs doing. Someone records it. Another person decides who should take it. The person doing the work may need to report a delay or ask a question. A manager needs to know whether the task is finished and what should happen next.

That handoff is where context matters. A note that says “room 104” may be enough for one person and incomplete for another. A request can change after it is written down. A shift can end before the work is done. The next person needs more than a reminder that something exists; they need its current status and enough detail to act.

We paid attention to the ways the team already handled those moments. Paper checklists gave people a simple place to record work. Whiteboards made shared priorities visible. Group texts helped answer questions quickly. These tools were familiar and useful. They also left information in different places, and it could be hard to tell which note was current or whether someone had already taken care of a task.

Start with the day people have

Shadowing changed the questions we asked. Instead of asking what features a system should have, we asked where people look for information, which details they need while moving between tasks, and what makes a handoff clear. We watched for the moments when a worker had to stop and ask around because the status of a task was uncertain.

Those observations also helped us see what a tool should not do. A phone screen needs to be quick to understand in the middle of a shift. Staff should not have to sort through options that have nothing to do with their role. A manager needs a useful overview, but the overview should come from the work being recorded as it happens, rather than another reporting chore at the end of the day.

We built the first version with the operations team and kept coming back to the same practical test: does this make the next step clearer? If a checkout happens, can the people responsible for preparing the room see it? If a repair is requested, can someone tell whether it has been assigned or completed? If a task is delayed, can the manager find out without asking several people?

A small system for shared work

The result is a manager website and a staff phone app that share one live system. It brings daily work into a common view, with timestamps and status changes that help people understand what has happened and what remains. Staff see the screens for their jobs, while managers can follow the flow of work across the day.

We began in senior living because that is where we learned how these handoffs affect a real team. The details of a hotel, restaurant, clinic, or facilities crew will be different. The way people coordinate work across roles and shifts is familiar in many places. We want to keep learning from each team rather than assume one setup fits them all.

Starting on the floor is a way of building with respect for the people who will use the software. Their day is already full. Any new system has to make the work easier to see and easier to hand off. That remains the question we bring to every product decision.