Operations Management Projects in MarlowOperations Management Projects in MarlowSample 4: VA / Organizational Case Study
Title: Case Study — Building an Inbox & Scheduling System from Scratch
The situation:
A household (or business) with a constant stream of incoming requests — appointments, deadlines, follow-ups — and no system to track any of it beyond memory. Things were getting missed, followed up on late, or duplicated.
What I did:
Triage first. I sorted incoming items into three categories: needs action today, needs action this week, and reference/no action needed. This alone cut visible "noise" by more than half.
Built a single source of truth. Instead of tracking things across memory, sticky notes, and half-remembered conversations, I moved everything into one shared calendar and a simple running list — so nothing depended on any one person's memory holding up.
Set a recurring review rhythm. A 10-minute check-in at the same time each day to re-sort anything new and confirm nothing time-sensitive slipped through.
The result:
Missed follow-ups dropped to near zero. Response time on time-sensitive items improved because nothing was waiting to be "remembered" — it was already sorted and visible.
Why this matters for VA work:
This is the same skill set I bring to inbox management, calendar coordination, and admin support — building a system that doesn't rely on anyone's memory, so nothing falls through the cracks even on a chaotic day. Writing Sample: Household Logistics / Parenting Niche
Title: The Job Nobody Hired Me For
I have six kids. I did not choose to become the family's default calendar, inventory manager, appointment scheduler, and emotional weather station — it just happened, the way water finds the lowest point in a room.
Most parenting advice treats the mental load like a scheduling problem. It's not. It's a memory problem. You're not just tracking what needs to happen — you're the only one who remembers that it needs to happen, that it happened last time too, and that if you forget, nobody else notices until it's a crisis.
After two decades of running a household this size, here's what actually moved the needle:
Stop trying to hold it all in your head. Every system that failed me failed because it depended on my memory working better than it does. The ones that worked took the memory out of me and put it somewhere external — a shared list, a posted schedule, a system that doesn't care if I'm tired.
Zone-based beats task-based. A cleaning schedule that says "Monday: kitchen" survives bad weeks better than one that lists forty individual tasks. When life gets scattered, you need a system with fewer decision points, not more.
"Good enough" is a skill, not a failure. Six kids taught me that the version of a task that actually gets finished beats the perfect version that lives in my head. That's not lowering the bar. That's understanding where the bar actually needs to be.
The mental load isn't a personality problem or a time-management problem. It's an infrastructure problem. Build the infrastructure, and the load gets lighter — not because you're doing less, but because you're not the only thing holding it up anymore. 
