The homepage lists the lessons. This page tells the stories behind them.
Honest caveat. These chapters didn’t unfold in a clean line. For most of the last sixteen years I’ve been running two or three operating engagements in parallel. The chapter structure below is the story I tell in retrospect, not the timeline as it was lived. The lessons section on the homepage is what the work actually taught me.
My first case study in operational excellence wasn't a boardroom. It was my parents' cleaning business in Orange County. Six in the morning to six at night. Six days a week. They didn't just clean houses across Irvine and the surrounding cities. They built the most trusted name in their category, one customer at a time, over years.
Watching them taught me three things before I had language for any of them. Reputation is a multi-year compounding asset. Quality control is a process, not a value statement. The work that's invisible to the customer is what makes the work the customer sees feel effortless.
I didn't know I was learning operations. I thought I was just helping out. By the time I started working my own shifts, I had already internalized something most operators don't pick up until much later in their careers: that the floor is the source of truth, that systems work when nobody has to be a hero, and that grit without architecture just produces burnout.
Wasabi Sushi. Baja Fresh. These were the entry-level food service jobs that taught the fundamentals. The smell of a service line at peak hour. The rhythm of a ticket queue. The cost of a wrong order in dollars and minutes. The difference between a checklist and a habit.
These shifts weren't impressive on paper. They were impressive in what they made permanent. The kitchen line is where you learn that strategy that never touches a shift schedule is theater. The strategy decks I would later write all had to pass that test, learned at sixteen years old behind a counter in Orange County.
Multi-unit general management at Gen Korean BBQ, BCD Tofu House, and Sake2Me Sushi taught me how a single operator can hold multiple units accountable at the same time. The scale was small enough to learn from but big enough to require systems instead of presence. I couldn't be in every kitchen, every shift. Something had to run the units when I wasn't there.
That something was the operating playbook. And I learned to build them by failing first. The first SOPs I wrote were too rigid. The second batch were too vague. The third batch worked because they answered one specific question per page: what does good look like for this part of the work, and how would you know if you were doing it wrong.
SEO and operations leadership at SEOD Digital Marketing came next. The hospitality background turned out to be a feature, not a bug. Operators who came up through digital marketing knew the math but didn't know the operating reality of a high-volume service business. I knew both.
The discipline that came out of this era: every campaign mapped to unit economics. Every dollar tied to a margin target. Strategy never leaves the floor. Execution never leaves the spreadsheet. Two hundred plus campaigns delivered consistently above ROI across industries and channels. The rule that emerged: if you can't kill the campaign that isn't working, you don't have a marketing function. You have a marketing hobby.
The contractor engagement with Mike Diamond Services, the well-known Los Angeles plumbing brand, was a sharper version of the SEOD pattern. They needed marketing that performed, and web development to support it. I came in as a contractor to lead both.
The work bridged campaign execution, conversion architecture, and the operational reality of a high-volume service business. Most marketing contractors would have treated the brief as a creative exercise. I treated it as an operations problem. The web development served the campaign. The campaign served the unit economics of the call center. The unit economics served the broader business. That's how you make marketing accountable to the operating reality of a services brand.
Hana Group was the chapter where the operating method had to scale across geographies. Twenty-one franchise units inside Whole Foods, Walmart, Sam's Club, and Target host environments. Six states. Multiple compliance regimes that didn't match. KPIs that weren't comparable across units because the units weren't comparable in scope, market, or maturity.
The four years I spent there were the years the playbook earned its name. We standardized the operating model so units could be benchmarked apples to apples. We redesigned the KPI tracking so variance was down fifteen percent inside a year. We built the regulatory framework that handled six critical incidents per quarter with zero penalties on record across the entire six-state portfolio. Twelve new stores opened in a single year, because the playbook had matured to the point where new units could come online without disrupting the operating cadence of the existing ones.
The lesson from Hana: multi-state isn't a scale problem. It's a coordination problem. The operators who fail at multi-state are the ones who treat it as more of the same. The operators who succeed are the ones who build the systems that make coordination invisible.
Zareen's was different. It was a Bay Area hospitality group growing faster than its operating systems could keep up. Three locations heading to five plus catering. Two hundred fifteen employees. A twenty-six-million-dollar annual budget. And SOPs that lived in the heads of the longest-tenured managers.
I was brought in as Senior Operations Consultant and Interim Head of Operations to redesign operations during the expansion. The mandate was complete operational reset. Document the SOPs. Tighten the financial controls. Rebuild the labor model. Audit-ready everything. And do it without disrupting the hospitality that made the group worth recognizing in the first place.
Eleven months later: three locations grew to five plus catering. Productivity lifted thirty percent without touching service quality. Operating profit during the engagement totaled $4.9M. The Michelin Guide recognized the restaurants during this window. The recognition wasn't the goal. The recognition was the byproduct of the operating discipline. That's the difference. You don't pursue Michelin. You build the operation that makes the recognition inevitable.
The next test was outside hospitality entirely. Obaba Fresh is a seafood and meats distributor in San Jose with a main facility, a satellite office, drivers, sales teams, and overseas backoffice partners. The operating problem was coordination across all of those moving parts while warehouse and accounting systems stayed accurate.
I came in as Operations Executive to be the central communication hub and to install operating discipline across the layers. WMS, ERP, and TMS systems oversight. KPIs for office and warehouse performance. Lean and continuous improvement applied to the workflow architecture. Compliance oversight across HACCP, FSMA, and insurance regimes. Office and support staff supervision. Reporting directly to the Managing Director.
The pattern that worked in hospitality worked in distribution. Different vocabulary. Same operating rule. The architecture transfers because the underlying question never changes: how do you turn the work that depends on heroics into a system that compounds without you.
In a parallel chapter, Bay Area Youth Foundation (the anonymized name for a 42-year-old faith-based youth nonprofit in the Bay Area) was hiring a Director of Development. Their goal was to double annual fundraising from $1.5M to $3M. Most candidates were preparing slide decks.
I built a working version of what the development office could look like on day one. A live donor CRM, a board-grade dashboard, an operations playbook, and a twelve-slide live-pitch deck for $50K to $250K major-donor conversations. Seven days. Solo build. End to end.
The case study lives at work/donor-crm with the actual dashboard and the actual deck. The lesson: walking in with the working version of the office beats walking in with a slide deck about the office. Every time.
The corporate operating work is the main thread of this story. But there's been a second thread running underneath since 2007. Eighteen years of mission-driven volunteer service across four organizations. Irvine First Korean Evangelical Church. Irvine Bethel Church. Korean Methodist Church. And Anchor Point Ministries from 2013 through 2025.
The Anchor Point chapter alone covered twelve years of volunteer fundraising. $1.2M capital campaign for a new church property. $300K every six months in recurring mission funding for college-campus outreach. 90%+ congregation tithing rate against an industry typical of 10 to 25 percent. The pattern behind the tithing number is the same pattern behind every operating engagement on my resume: engaged people are giving people, and engagement is built across years, not quarters.
I never thought of the volunteer work as separate from the operating work. The discipline is the same. The vocabulary is different. The full chronology of the volunteer thread lives at community.
The next chapter is the VP-level operating role at a multi-unit, franchise, restaurant-tech-adjacent, or founder-led operating company that needs the operating method applied at a larger scale than I've run before. The platform that's already been built — sixteen years of operating depth, the donor stewardship track underneath it, the AI-forward consulting practice, the published operating prompts other operators use — gets to do its compounding work in a single seat with a single mandate.
That's the chapter I'm writing now.
The homepage carries the impact numbers, the case studies, the credentials, and the contact path. This page is for the people who want the longer version of how I got here.