How I Work
THE METHOD
THE METHOD
Behind every work sample on this site is the same five-step approach: Listen, Map, Find the Gap, Build, Teach. It's how I move from understanding a problem to developing something practical.
Each step connects to work I've actually completed. You can follow the process, see the decisions I made, and look at the work behind them.
A résumé tells you where I've worked. This site shows you how I think.
Each step links to the work that proves it
Understand the people before deciding what to build.
For Picnic Sessions, the DJ didn’t know exactly what he wanted, so I started with observation: I attended several events myself and built around what the community valued, including extras like a merch store. Once I showed him a working draft of the site, the real elicitation began. Seeing it, he could finally say what he needed. On every project, that back-and-forth sorts the must-haves from the nice-to-haves and checks what the platform can realistically support. The lesson I carry forward: I listened closely to the community, but not closely enough to what the owner could run and maintain.
View Work Sample: Picnic Sessions
Make the work visible before changing it.
I modeled request routing in Microsoft Visio as current-state and future-state swimlane diagrams, manual and automated. Modeling both showed where decisions happen, how work is handed off between people and systems, and where a person still needs to step in.
View Work Sample: Request Routing
Look beyond what appears to be working.
Salad and Go was a business I knew as a customer. Using public court filings, I ran a gap analysis between what customers could see and what the financial records revealed: busy stores on the surface, and underneath, expansion stores losing money before overhead, a costly central kitchen, and rent still owed on closed stores.
View Work Sample: Salad and Go — The Quiet Collapse
Turn what I've learned into something that works.
I turn requirements into working solutions with Google Apps Script, Google Sheets, Tally, Stripe, Google Sites, and the Gemini API: calendar routing, an AI executive brief, NNS client intake and delivery, and a Client Control Center. Each build follows defined business rules and is tested against them with sample data before I rely on it.
See how I test: NNS Build Manual
View Work Samples: Calendar Routing · AI Executive Brief · Client Intake & Delivery · Client Control Center
Make the process clear enough for someone else to carry forward.
I write documentation so a solution is adopted and maintained throughout its life cycle, not just delivered. My chain-of-title documentation set includes an SOP, a swimlane, a job aid, and a training deck. My NNS Master Build Manual keeps testing checklists and known gaps current, so the installation procedure is followed the same way every time.
View Work Samples: Film Legal Delivery — Chain of Title Clearance · NNS Build Manual
I give AI the right information and a clear direction, then check what it produces against the source. For my chain-of-title training deck, I chose the template and built the first slides, then gave Claude my SOP to complete the remaining slides. I reviewed every slide against the SOP and corrected what didn't match. The same principle applies to my AI executive brief: AI makes the first pass, but a person reviews the information and makes the decision. I use ChatGPT for writing and Claude for structure and planning, while keeping responsibility for the final work with me.
↙ View ↘