#1: a chef and a market researcher have book club

Why did I start a blog? Here's the answer: https://madimarvels.blogspot.com/2025/10/welcome.html

My first ever post is a book report, which is comical since I’ve never been much of a reader beyond the occasional beach read. But this summer, I flew through my book club pick (Change the Recipe by José Andrés and Richard Wolffe) during a rainy morning. Andrés, a celebrity chef and humanitarian who got his start in the DMV (DC-Maryland-Virginia area, not the Department of Motor Vehicles), chronicles his career through a series of short stories and lessons.

The book isn’t anything novel (no pun intended), but two lessons from Andrés’ career stuck with me. And that’s what this post focuses on.

Lesson #1: Don’t work for someone, work with them.

“‘I want to work for you,’ I said with a big smile on my face. ‘You don’t work for anybody,” he replied. You work with somebody.” (page 51 - conversation between José Andrés and a restaurant owner)

Throughout my career, I’ve been lucky to find myself at companies and on teams that value collaboration. It’s not just a buzzword in a job description, but a daily practice and a shared commitment. Whether I’m the most junior or most senior person in the room, that sense of working jointly, rather than simply giving or following orders, has made work enjoyable and greatly contributed to my professional growth.

I remember one instance where a Vice President came to me and said something along the lines of, “I’m stuck. The client wants to do XYZ with this budget, but I’m not even sure it’s possible. How do we make it happen?” We blocked off 30 minutes and spitballed ideas until we landed on a creative option we were both confident presenting.

The VP didn’t come to me because I had some rare skill they didn’t. And after my first few ‘anything goes’ suggestions, I even wondered why they’d asked for my input at all. But that was the point. Years of experience was irrelevant, and what was important was trust in each other to get the job done.

Working with junior teammates has taught me patience and leadership. It’s a delicate balance helping them bring their ideas to life while giving them space to experiment (and occasionally fail). I think back to countless 1:1s where we’d walk through a deliverable or project design together. We would discuss the steps they planned to take. Then, I would introduce additional components or challenge them to consider alternative options, encouraging them to defend or refine their original idea with confidence.

I never pretend to know more than younger team members. In fact, they often catch the small details that make all the difference for clients. And when it comes to technology, I am the student. The AI boom hit a few years after I graduated college, so many new hires continue to come in with fresh perspectives and clever ways to use emerging tools to make our work better - ideas I never would’ve dreamed up.

On the other hand, working with senior colleagues has taught me confidence and humility. I used to see higher-ups as unapproachable, assuming they didn’t want to hear my novice ideas. WRONG. Many appreciate a fresh take, especially when it is thoughtful and shared with enthusiasm. These conversations have been some of the most rewarding moments for me, providing the chance to think like a seasoned professional and build the skills I need for the next time I face a similar challenge.

To me, working with someone implies co-learning; both people grow and come out ahead. Working for someone, on the other hand, implies hierarchy; one person above giving directions, and the other below following them. From what I’ve seen, the best work happens when titles fade, and everyone’s focused on achieving the same goal, together.

Lesson #2: Progress beats perfection.

“That’s especially true in an emergency where not making a decision will always be worse than making the wrong decision. If the wrong decision is that we send food to the wrong place, at least there was a decision to send food and keep the food economy moving. It’s much easier to fix a bad decision. If you make the decision to buy a pot of twenty quarts or thirty quarts or ten quarts, I would prefer that you make the wrong decision in the size of the pot – whether it’s too big or small – rather than not buying any pot at all. Without the pot, nobody will be cooking. And nobody’s going to be fed.” (page 115 - reflections from José Andrés)

In this passage, Andrés states that in a crisis, any action is better than no action. Instead of waiting around for the perfect solution, make the best call you can in the moment and adjust as you go. 

I have mixed feelings about this attitude.

In my current industry (communications / public affairs), the wrong move can make a bad situation worse. A poorly worded statement or a rushed response can easily become the bigger headline. In those cases, I DO believe taking an extra hour (or two) to craft a solid plan is worth it. Once something is public, it’s hard to take it back.

On the other hand, Andrés’ point rings true for me when I think back to my consulting days with large enterprise clients. Many “crises” weren’t real emergencies, but rather they often started with an executive tossing out an idea that sent the rest of the company scrambling to bring it to life. Okay. No problem. It happens. I would help clients run expert interviews or online polls and lay out clear next steps. 

But that’s where things usually stalled: before anything came of it. The recommendations would get stuck while climbing the long ladder of approvals (with each step requiring more and more iteration). Eventually, the report got filed away to gather digital dust, and the emergency everyone was chasing was dropped or shifted direction entirely. 

This is where I see Andrés’ lesson in action. It’s tough to get buy-in (from the executives with the initial vision), especially when the return on investment feels uncertain… but leaders have to be flexible. Perfectionism kills momentum. If the initial plan is not totally off base, just start. You can always refine as you go. 

I get it. I’m not an executive, so it’s easy for me to talk about how things should go. But I do believe that mindset applies to anyone. Keep ideas flowing. Test things out. If it flops, figure out why and make it better next time. At the end of the day, you really do miss 100% of the shots you don’t take.

Comments

  1. This is a great post. I'd love to hear what you're eating (or drinking) alongside each post!

    ReplyDelete

Post a Comment

Popular posts from this blog

#2: football is just a sport where different teams show kindness by giving each other really strong hugs

Welcome!