Projects in MarlowProjects 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. Sample 3: How-To Piece (Practical/Instructional)
Title: How to Build a Household System That Survives a Bad Week
Most organizational systems are designed for your best days — when you're rested, motivated, and have an hour to spare. They fall apart the moment life gets hard, which is exactly when you need them most. Here's how to build one that holds up anyway.
Design for your worst day, not your best one. Ask: "Will this still work if I only have 10 minutes and I'm exhausted?" If the answer is no, simplify it until it is.
Reduce decisions, not just tasks. A schedule that tells you what to do removes more mental load than a checklist you have to interpret. "Monday: kitchen" beats "wash dishes, wipe counters, sweep, take out trash" — same result, fewer decisions.
Make the system visible, not memorized. If a system only lives in your head, it dies the moment you're too tired to think. Post it. Write it down. Put it somewhere you'll see it without having to remember to look.
Build in a "good enough" version. Every task should have a stripped-down version for hard days — the 20% that matters most. A quick wipe-down still counts. Partial progress still counts.
Review and adjust monthly, not daily. Don't try to perfect the system in real time. Let it run, notice what keeps breaking, and adjust once a month. Systems that get redesigned every day never get the chance to actually work.
A system built for your best day will always fail you on your worst one. Build for the worst day, and the good days take care of themselves. Sample 2: Short Blog-Style Piece (Parenting/Household)
Title: The Zone Method Saved My Sanity (and My Baseboards)
For years I ran my cleaning schedule off a mental list that lived entirely in my head. It failed constantly — not because I was lazy, but because a list that only exists in your memory falls apart the second life gets chaotic. And with six kids, life is always a little chaotic.
The fix wasn't a better list. It was fewer decisions.
Instead of forty scattered tasks, I assigned each weekday one zone:
Monday: Kitchen
Tuesday: Bathrooms
Wednesday: Windows, walls, baseboards
Thursday: Bedrooms
Friday: Floors
That's it. On a Tuesday, I don't have to think about what needs cleaning — I already know. If the day goes sideways and I only get to half the bathroom, that's fine. Tuesday's job was bathrooms, and I did some of it. Nothing carries the guilt of "I didn't get to my list" because there was no long list to fail.
The zone method works because it removes the thing that actually burns people out: not the cleaning itself, but the constant re-deciding of what to clean. Once the decision is made in advance, showing up gets a lot easier. 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. 
