Journal
NOTES IN PROGRESS
NOTES IN PROGRESS
This page holds dated notes on what I’m learning and how I’m applying it, newest first.
Each entry ties back to real work on this site, from a case I’m following to a tool I’m practicing.
The projects have finish lines. The learning doesn’t, and this is where I keep track of it.
Newest first
Documentation has to match what the system actually does.
Goal: Document my calendar routing workflow as a formal use case.
What happened: When I checked my use case against the script, the code ran the duplicate check before the routing rule. My swimlane showed it after.
What I changed: I corrected the use case and the diagram to match the code, and logged an open question: should a blank “Calendar Required” be skipped or flagged?
Next time: I verify documentation against the system before I call it final.
See the use case: Calendar Routing
A sign-off isn’t the finish line.
Goal: Track the Salad and Go bankruptcy through to real outcomes.
What happened: The court approved a $1.48 million sale of two Arizona stores, but weeks later the buyer still hadn’t closed, and the creditors joined the push to enforce it.
What I changed: My case log now separates approvals from completed results, so a step doesn’t read as done until the money moves.
Next time: I track sign-off and completion as two separate milestones in any process.
Read the case: Salad and Go — The Quiet Collapse
A swimlane answers one question: who does this?
Goal: Map request routing as a clear swimlane in Visio.
What happened: My first draft had too many lanes, because I was treating steps as lanes.
What I changed: I rebuilt it so each lane is a who (requester, person or script, Calendar, Sheet), and the handoffs showed up on their own.
Next time: I name the roles first, then place the steps.
See the map: Request Routing
Decide the rules once, then every page follows them.
Goal: Rebuild nine portfolio pages so they read as one site.
What happened: I kept fixing the same inconsistencies page by page: labels, tool lists, intros.
What I changed: I set the standards once (one label pattern, one Tools Used format, one intro order), and every page after that went faster.
Next time: I define the standard before building the second page, not the fifth.
See the method: How I Work