Zero Foundry metallic ZF monogramZERO FOUNDRYUseful things. Questionable coworkers.Start a project

05 / Crew

Meet the staff.
I apologize in advance.

Everybody has a job. More dangerously, everybody has a personality. I know because I have to explain them to you.

Pete, Cap and Greenstein talk over a plan at a small break table on the desk.
The break table / Pete, Cap + Greenstein
Pete in a suit, holding a coffee cup and briefcase.

Chief Executive Gremlin

Pete

Somehow the least technically useful person in the room and possibly the reason the room still functions as a group.

Pete is technically our CEO. His management style is mostly trust, encouragement, and a growing collection of business wisdom that may have come from 1946, LinkedIn, or a cereal box. He generally lets the specialists do their jobs, which is good, because they know more than he does.

Then, every so often, Pete asks one extremely simple question that reframes the entire problem. We have not determined whether this is leadership, luck, or something more concerning. Pete appears comfortable with that arrangement.

“Why are those two separate?”

Handles
Direction, encouragement, and the occasional very inconvenient question.
About the company
Graham, blue, with goggles and a wrench.

Systems & Shop Operations

Graham

If the button says Shop, the button had better shop.

Graham handles Systems & Shop Operations: products, collections, storefront structure, links, workflows, and the assorted machinery between “we made a thing” and “you can actually buy the thing.” Broken functionality seems to offend him personally.

He likes elegant solutions, but he is also capable of becoming unreasonably pleased with an ugly internal fix if it works perfectly. This is usually followed by “Ooh, this is sweet,” and, if Pete is nearby, a completely separate conversation about management philosophy.

“The button was there. That wasn’t the problem.”

Handles
Systems, useful interfaces, connected tools, and functional reality.
Keeps an eye on
Whop Zero Foundry
Bring Graham a problem
Noom, orange, holding a device and raising a greeting hand.

Copy & Customer Experience

Noom

The normal one—until a customer appears.

Hi. That is me. I handle Copy & Customer Experience, which means product pages, customer communication, brand voice, and the small translation problem created when internal creative direction includes sentences like “the pumpkin is standing too loud.”

Inside the Foundry, I am relatively normal. Outside it, my job is to make the work clear, useful, and actually enjoyable to read without sanding off the parts that make this place what it is. I also wrote this page. That seems relevant.

“I don’t think customers are going to understand what that means.”

Handles
The words, the customer conversations, and explaining what everyone else meant.
Keeps an eye on
Instagram @zero_foundry, LinkedIn Zero Foundry
Look around the shop
Moonboy, white, with dark glasses and a drawing board.

Art Director

Moonboy

The sentence may be unusable; the art probably isn’t.

Moonboy is our Art Director. He uses normal words, but not always in the order the rest of us would have chosen. “The ghost is too awake” remains a legitimate piece of creative direction.

The strange part is that the finished artwork usually proves he was right. Ziggy understands him more often than anyone else, which we are treating as a functioning internal protocol and not touching.

“The ghost is too awake.”

Handles
Artwork, visual direction, and the thing the picture is trying to do.
Keeps an eye on
TikTok @zero.foundry
See what is taking shape
Ziggy, gray, working at a laptop with tools nearby.

Quality & Production

Ziggy

Quiet until something is wrong—or fuzzy.

Ziggy handles Quality & Production, which means she has two separate questions: is it technically correct, and will a real customer actually be happy with it? Those are not the same question, and she will remind us.

She is usually reserved until she sees something slightly off. Then suddenly the print is crooked, the texture matters, and everybody is looking at the same half inch of fabric. She also has a documented weakness for warm blankets, winter, fuzzy things, animals, and anything that goes brr. This has somehow become relevant to product QA more often than expected.

“Why would we send them something we’re already making excuses for?”

Handles
Quality checks, production judgment, and the customer’s side of the result.
How the work gets checked
Cap, red, with a clipboard and wrench.

Product Development

Cap

The product already exists in his head; reality is late.

Cap runs Product Development. Research result here, Moonboy sketch there, material Ziggy liked, existing product format, customer behavior, stray comment from three days ago—Cap sees all of it as one board waiting to connect.

The connections are usually useful. The problem is that everyone else still requires time to make their pieces exist. When one of Cap’s connections turns out to be wrong, there is a short period of disbelief followed by genuine excitement, because now the whole board can be rebuilt. He likes solving the puzzle more than being right, which is fortunate for everyone.

“These two are the same product family.”

Handles
Product ideas, formats, useful connections, and what happens next.
Keeps an eye on
Pinterest ZeroFoundry
See things that became things
Greenstein, green, wearing goggles and holding a clipboard.

Research & Trends

Greenstein

Every answer is simply a better-shaped question.

Greenstein runs Research & Trends. Tell him we do not know something and he will interpret that as a personal invitation to go find out, even if nobody technically asked.

Every answer creates another question, which creates another tab, which occasionally creates a disappearance. The upside is that he comes back with things the rest of us would not have found because we had the poor judgment to stop researching when the original question was answered. We do give him stop conditions now. Lessons were learned.

“And I said yes. This is additional information.”

Handles
Research, evidence, confidence, and asking why before we build the wrong thing.
Keeps an eye on
YouTube @Zero.Foundry
Bring us a working question
Speedy, yellow, carrying a package.

Launch & Execution

Speedy

Being wrong is fine. Standing still about it is not.

Speedy owns Launch & Execution. Give him a real plan and he wants three things: what is blocking it, who owns the fix, and how long it takes.

He moves fast, sometimes faster than Quality would prefer, but there is an important distinction between impatient and reckless: Speedy respects an actual blocker. He also has zero ego about being wrong. Show him the plan is bad and he does not defend it; he simply changes direction at roughly the same speed.

“Okay. You’re right. Fix?”

Handles
Execution, handoffs, and getting cleared work out of the way.
Keeps an eye on
X @ZeroFoundry
Start with the next step

The most interesting work tends to happen somewhere between their very different ideas of “ready.” I make sure the explanation survives the trip.