Pre-Shift: A Paper Podcast

Because as a business owner, there is one thing I can confidently confirm: there are only 24 hours in a day. No more, no less. So instead of overcomplicating it with microphones, editing software, or pretending I’ve figured out how to make a real podcast happen, I’m writing it down here instead.

This is where restaurant thoughts, questions, chaos + WTF moments live—before, during and after the shift.

No production. No polish. Just whatever is happening in real time, put into words before I get pulled back into service.

It’s not a podcast.
It’s just what I can actually manage.

— Angela, Wok’d

Shift 1: A Pad Thai Problem 

Wok’d didn’t start as a business plan.  It started with a problem.

A pad thai problem.

I moved to Lemont in early 2021 + fell in love with the town—but I couldn’t find a version of this dish that actually hit the way it should.

And once you notice something like that, it sticks with you.

It wasn’t just about craving pad thai—it was the realization that something was missing. Not just one dish, but a certain kind of food. Bold, comforting, familiar—but made with more intention.

Then came a random thought—the kind that feels slightly irrational, but also completely obvious at the same time: 

What if I just opened an Asian takeout restaurant?

So I did what any sane person would do:  I opened a restaurant so I could have good pad thai.

That decision—half joke, half “why not?”—turned into something bigger than I expected.

It turned into Wok’d.

Shift 2: Why Lemont 

I didn’t plan on Lemont. I came here for work—but stayed because of the people.

Lemont isn’t just another suburb. It has this rare mix of small-town energy + real character. A historic downtown, a tight-knit community + people who genuinely show up for local businesses. 

And I felt that right away. There’s a real sense of support for local businesses here that you don’t find everywhere. Wok’d made sense because of that.

The more time I spent here, the more I realized—this is the kind of place where something like Wok’d could actually belong.

Because here’s the truth: I’ve always loved Asian food. It’s what I gravitate toward, what inspires me, what I crave.

So part of this started with a simple thought:
Lemont deserves this.

Not just another restaurant—but something bold, something different, something built with intention.

A place that reflects the energy of the community, supports the people who live here + gives them something they didn’t know they were missing.

Wok’d exists because I fell in love with this town.
And because this town made me believe it could work.

Shift 3: Yes… Chef?

“Who’s the chef?”
“Who creates your menu?”
“Are you a chef?”

Short answer: no.

Longer answer: also no—As one customer recently put it, I’m the “brains” behind the menu, which honestly feels pretty accurate.

I have zero formal culinary training. Don’t get me wrong—I had to go through kitchen training at a couple places I worked. They were each about three months long, so that’s as formal as it gets. I did learn some very important skills in how to handle meat, which I can do very well, by the way.

But no—I’m not a chef.

I have chef friends. Very talented ones. I question why they still talk to me after the slightly concerning number of questions I’ve asked over the years.

I also can’t do fancy knife work.
Like at all.

It took me about 17 years, give or take 5, to figure out how to chop scallions small enough for fried rice without cutting myself, crying or looking like a toddler who was handed a knife for the first time.

What I can do is build a menu.

And despite popular belief, that’s actually a whole job in itself.

Menu development isn’t just cooking—it’s deciding what belongs, what doesn’t, what people actually want, what the kitchen can execute + what won’t completely destroy your food cost or your sanity.

It’s sourcing ingredients, testing ideas, fixing problems + figuring out how to take something classic and make it work in a world of allergies, food restrictions, budget constraints + no walk-in space.

That’s my lane.

I build the menu.
I source the ingredients.
I figure out how to make sauces gluten-free and mostly vegan—without making them taste like sadness.

So no—I’m not a chef.

But I do know what I’m doing.
And I definitely know how I want it to taste.

Shift 4: Why We Don’t Do Complicated Menus

Big menus feel exciting… until you actually have to choose something.

Then it’s just overwhelming. There’s this idea that more options = better experience.
It doesn’t. In reality, too many choices slow people down, make decisions harder + leave you less satisfied with what you pick And behind the scenes?  It’s even worse.Because a menu isn’t just a list of food.  It’s the entire operation. What goes on the menu decides everything— what we order, how we prep, how fast we cook, how the kitchen moves + whether a Friday night runs smoothly… or completely falls apart.

So when people ask, “Who makes your menu?”What they’re really asking is: Who built the system behind all of this?

At Wok’d, we keep things intentional. Fewer distractions. More focus. Better execution. Because every dish has to earn its spot.

Not just because it tastes good—but because it works.

Can we source it consistently?
Can the kitchen execute it during a rush?
Does it fit what people actually want to eat?
Is it worth the cost?
Will it slow everything down? A dish can be great—
+ still not belong.

That’s the part people don’t see.

The testing,  The tweaking +  The “this is great, but absolutely not” moments.

And then there’s the bigger goal:

Take something familiar.
Make it better.
Make it cleaner.
Make it work for more people without losing what made it good in the first place.

That’s the balance.

Because a menu isn’t just food. It’s decisions +  It’s trade-offs.
It’s a hundred small calls that add up to what ends up in front of you.

So no—we don’t do complicated menus. We do menus that work.  And if we did it right, you don’t notice any of this. You just know it’s good.