Operations built for the real world: systems that hold when people leave, rollouts that plan for what breaks, and data that leads to decisions. Chief of Staff and then Director of Operations at a home care company across seven territories.
Territories
Service lines over my tenure
Caregiver workforce: 25 to 230 at peak, about 9x
Active clients (3.8x), with about 270 served in total
<aside> 👋
Open to operations and Chief of Staff roles, contract or full-time. Remote, or hybrid in the Long Beach area. Reach me at [email protected]
</aside>
For the executive side of this work (org design, the decision forum, coaching the CEO): Portfolio: Chief of Staff
Work Sample: The AI Evidence Standard
The standard I wrote for when AI output counts as a fact and when a human has to verify it: failure modes, trust tiers and guardrails, built after two of its findings in one day nearly became accusations.
Work Sample: How I Rolled Out a Scheduling App That Was Still Being Built
Rolled out a scheduling system while it was still being built: failure planning, fail-safes, a clear escalation path, and cut over on the originally planned date.
Work Sample: Executive Briefing on Changing Our Hours of Operation
Modeled visit demand by time block to show how operating hours could extend service to 8 p.m. without paying for a 12-hour day. Approved organization-wide across all 7 territories; caregivers disliked split shifts, so we moved to a continuous 8 a.m. to 8 p.m. day staffed by a morning crew and a night crew. The sample's figures are illustrative.
Work Sample: What a Class Average Hides
Dashboards that segment results so leaders see which groups need what, and track whether an initiative is working over time.
Operating Systems and Governance
The record, the standards, and what happens when the person holding them leaves.
Measurement, Reporting and Evaluation
What gets counted, who is missing from the count, and whether a rating means the same thing twice.
Roya Bolouri · Long Beach, CA · [email protected] · linkedin.com/in/roya-bolouri/