Career Change to Management Consultant at 40

Sixteen years in automotive supply chain. Why consulting?

I was good at my job. I was director of supply chain at a tier-one supplier, 2,400 employees, four plants, $680 million in annual revenue. I managed a procurement team of 14 people. I negotiated contracts with steel mills and resin suppliers and logistics providers. I knew every production schedule, every inventory buffer, every lead time for every component in our top 50 SKUs. And I was bored. Not because the work wasn't complex. It was complex. But it was the same complexity on repeat. Different quarter, same problems. Steel goes up, I renegotiate. Logistics costs spike, I find a new carrier. A supplier goes bankrupt, I dual-source. After 16 years, I could see every problem before it arrived and I knew the playbook for every one. The playbook worked. That was the problem. When the playbook always works, you're not thinking anymore. You're executing. And I missed thinking.

A recruiter reached out about a VP of Supply Chain role at a competitor. $195,000 base, bigger team, same industry. I looked at the job description and I thought: this is the same job with a bigger title. In 10 years, I'd be a VP doing the same thing I'm doing now at a slightly larger scale with slightly more people and a slightly nicer office. And then I'd be 54 and I'd retire at 62 and the sum total of my professional contribution would be: I kept the supply chain running at three or four companies for 30 years. That's valuable. It's not enough. I wanted to solve problems I hadn't seen before. Consulting seemed like the place where that happens.

You went back for an MBA at 41. How did that happen?

It almost didn't. My wife, Cheryl, is a pediatric nurse. We have two kids: Marcus, who was 13, and Elena, who was 10. Our combined income was about $265,000. Mortgage, two car payments, the kids' activities, Cheryl's student loans from her BSN. We were comfortable. Not wealthy. Comfortable. An MBA at Michigan Ross, which is where I applied because I wanted to stay in the Midwest and it's a top-15 program, costs about $130,000 in tuition for two years. Plus the opportunity cost of my $162,000 salary. The total price tag was roughly $425,000 if you include lost income.

Cheryl and I sat at the kitchen table with a spreadsheet. Not a metaphorical spreadsheet. An actual Excel file that I built with every line item of our household budget, projected over five years, under three scenarios: I stay in supply chain, I do the MBA and go to consulting, I do the MBA and go to industry at a higher level. The consulting scenario required two years of Cheryl carrying the mortgage on her salary plus about $90,000 in loans (we could cover $40,000 from savings). The breakeven point, the year where cumulative earnings in the consulting path exceeded what I would have earned staying in supply chain, was year seven. I'd be 48 before the MBA paid for itself financially. Cheryl looked at the spreadsheet and said "this is a terrible investment." Then she said "but you've been miserable for two years and I'd rather be broke with the person you were at 30 than comfortable with who you're becoming." That was the conversation. The spreadsheet lost. The marriage won.

What was the MBA like at 41?

Academically, easier than I expected. Not easy. But I'd been doing P&L analysis and contract negotiations and supplier risk assessments for 16 years, so when the finance professor taught DCF modeling, I'd already built a dozen of them for capex decisions at work. Operations management was basically a formalized version of what I did every day. The cases in strategy class, which were about companies making competitive positioning decisions, were engaging because I could map them to real decisions I'd made or seen made at my company. The 26-year-olds in my cohort were learning concepts. I was recognizing patterns. That's the advantage of going back at 41. You're not learning from zero. You're connecting frameworks to experiences you already have. The connection is faster and deeper.

Socially, it was strange. My study group was four people: me (41), Kenji (28), Sanjana (27), and Olivia (31). I was older than Kenji and Sanjana's parents would have been when they had them. We got along because the MBA strips you down to a level where everyone is just trying to survive the workload, and age doesn't matter when you're all in the library at midnight trying to finish the same case write-up. Kenji is the one who taught me how to format slides the way consultants expect. He'd look at my PowerPoint and say "this looks like it was made by someone in industry" and he meant it as a kindness, not an insult. He was right. Industry slide decks are functional. Consulting slide decks are performative. The same information, presented differently, means something different in consulting than it does in a boardroom at an automotive supplier. Learning that translation was worth about $20,000 of the tuition, and I'm not exaggerating.

How was recruiting?

Harder than for younger candidates. Consulting firms recruit at MBA programs with a specific model in mind: hire 27-to-32-year-olds with 3-to-5 years of pre-MBA experience, train them in the consulting skillset, and put them on a trajectory toward partner by their late 30s. I was 43 during recruiting. The partner trajectory for me would start at an age when most people who started at 28 are already at the decision point. The firms see a 43-year-old and they think: compressed timeline, limited partner potential, possible cultural fit issues with younger teams. These things were never said to me directly. They were communicated through the specific way interviewers asked "where do you see yourself in 10 years?" which is a question designed for 28-year-olds and becomes uncomfortable when the honest answer is "I'll be 53 and I'd like to still have functioning knees and a relationship with my teenagers."

I targeted Big 4 because the ops practices at Big 4 firms value industry experience more heavily than MBB. MBB wants generalists. Big 4 ops wants people who've been in the room. My 16 years of automotive supply chain experience was a liability at McKinsey and an asset at Big 4. I got offers from two Big 4 firms. I chose the one that let me stay in Detroit, which matters when your wife is a nurse at a specific hospital and your kids are in a school they love and the idea of uprooting everyone for a career change that's already asking enough of your family feels like one ask too many.

How's the first year?

Fast. Disorienting. Occasionally exhilarating. My first case was an automotive OEM, which the staffing team deliberately chose because of my background. The engagement was a manufacturing footprint optimization: should the client consolidate two plants into one? I knew how to answer that question from the supply chain side because I'd been on the receiving end of those decisions for 16 years. What I didn't know was how to answer it from the consulting side, which means: how do you build the business case, structure the analysis, present the recommendation, and manage the client's emotional response to closing a plant that employs 800 people? The analytical work was straightforward. The advisory work, the part where you sit across from a plant manager and tell him that the math says his plant should close, that was new. My boss, a director named Tanya, watched me do it on my second engagement and afterward she said "you were too empathetic." I said "I've been that plant manager." She said "I know. That's why you're good at this. But you need to deliver the recommendation and let the client process it. Don't process it for them." She was right. Empathy is an asset in consulting. Over-identification is not. The line between them is something I'm still learning to walk.

What's the thing about career-changing into consulting at 40 that nobody prepares you for?

The title reset. For 16 years, I was a director. People reported to me. I had a budget. I had authority. When I spoke in a meeting, people wrote things down. At the firm, I'm a consultant. That's the second-lowest rung. People who are 15 years younger than me are managers and senior managers. They review my work. They give me feedback. They tell me my slide isn't formatted correctly. A 31-year-old named Aisha told me last month that my executive summary "needed more so-what" and she was completely right and I wanted to crawl under the table. Not because Aisha was wrong. Because I'm 44 years old and I'm being coached on slide formatting by someone who was in middle school when I negotiated my first $30 million steel contract. The knowledge I have is real. The skills I'm building are real. But the position, the title, the place in the hierarchy, it's a full reset. And resetting at 44 is different from resetting at 28. At 28, you have nothing to lose. At 44, you have 16 years of identity to grieve. It's a quiet grief. Nobody holds a funeral for a title. But it's there. It sits in the room when Aisha reviews my slides and it sits in the car on the way home and it sits at the kitchen table when Marcus asks me "Dad, are you, like, a boss at your new job?" and I say "not yet" and he says "oh" and that "oh" contains everything.

Eight years as an executive director. What was the breaking point?

The last board meeting. Or rather, the last board meeting where I presented a strategic plan that I knew was wrong and the board approved it unanimously because board members at mid-size nonprofits don't challenge strategic plans, they ratify them, and I was tired of being ratified. The plan called for expanding our youth workforce development programs into two new counties. The expansion was based on grant availability, not demand. We were following the money, not the need. I knew this. The program director, Angela, knew this. The data showed that the two counties we were expanding into had three existing providers serving the same population. We weren't filling a gap. We were competing for the same participants to satisfy a funder's geographic reach requirement. But the grant was $1.8 million over three years and our operating budget was $12 million and you don't turn down $1.8 million when your development director, Kevin, has been telling you for six months that individual giving is flat.

I sat in that board meeting and I watched 11 people approve a plan that I knew was strategically weak, and I thought: the problem is not the board. The problem is not Kevin. The problem is that I've been making decisions based on funding availability instead of strategic analysis for eight years because that's how nonprofits work. The incentive structure rewards revenue capture, not impact optimization. And I wanted to be on the other side, helping organizations like mine make better decisions with better data instead of making the same compromised decisions from inside the system.

You didn't get an MBA. How did you get into consulting?

Directly. No MBA. This is unusual and I'm aware that it's unusual. The path was: I attended a social sector conference in 2023 where a boutique firm, the one I now work for, presented a case study about a strategic restructuring they'd done for a regional health system's community benefit programs. The presentation was sharp. The analysis was rigorous. The recommendations were the kind of recommendations I wished I'd had when I was making the expansion decision. After the presentation, I talked to the partner, a woman named Diane, for about 20 minutes. I told her what I did and what I wanted to do. She said "we don't usually hire people without consulting experience or an MBA." I said "you don't usually find someone who's run a $12 million social sector organization and wants to learn the analytical tools they were missing." She gave me her card. I emailed her the next day. We had coffee three weeks later. Six months after that, I interviewed. The interview included a case study, which I'd prepared for by buying a case interview prep book and practicing with my friend Ronnie, who is a management consultant at McKinsey and who said "you're going to be terrible at the math and great at the recommendation" and he was right about both.

Diane hired me as a senior consultant, which is one level above entry, because my executive experience justified it even though my consulting experience was zero. My salary: $105,000. My previous salary as ED: $118,000. I took a $13,000 pay cut to become a junior employee at a firm where I'd never built a slide deck. My husband, Paul, who teaches high school history, made a face when I told him the number. Not a bad face. A calculating face. He teaches AP History. He thinks in terms of consequence. The consequence of $13,000 less per year, in Portland, with two kids (ages 8 and 12), a mortgage, and Paul's salary of $68,000, is: tighter. Not desperate. Tighter. We cut the landscaping service. I started packing lunch. The kids noticed. Our daughter, Bea, asked why we don't get pizza on Fridays anymore and Paul said "Mom's investing in herself" and Bea said "can she invest in pizza instead?" She's 12. She has a point.

What does a nonprofit executive bring to consulting that other people don't?

Stakeholder fluency. When you've managed a board of directors, a staff of 85, funders who each want different outcomes measured differently, a community that distrusts institutions, and a local government that controls your largest contract, you know how to read a room. That's not a metaphor. It's a literal skill. I can walk into a meeting with a hospital CEO and a community health center director who disagree about resource allocation and I can feel where the tension lives before anyone says a word. The CEO is worried about margin. The health center director is worried about access. Neither will say their actual concern first because saying it first gives the other person leverage. My job is to name both concerns in a way that makes each person feel heard without making either feel exposed. I learned this from eight years of board meetings where the real agenda was never on the printed agenda.

What I didn't bring was analytical rigor. My first month at the firm, Diane reviewed a strategic plan I'd drafted for a community development financial institution and said "where's the analysis?" I'd written a narrative. A persuasive, well-structured narrative with recommendations based on my professional judgment. Diane wanted: a market sizing model, a competitive landscape assessment, a financial sustainability analysis with three scenarios, and a benchmarking comparison against four peer institutions. She wanted numbers. Not in place of the narrative. Underneath the narrative. Supporting it. Making it defensible. I'd been making recommendations based on experience and instinct for eight years. Consulting requires you to make recommendations based on experience, instinct, AND data. The data is the part I was missing. Learning it at 42 was humbling in a way that was different from learning anything else I'd learned at 42. Because I was already an expert at the thing I was bad at. I was an expert strategic thinker who couldn't build a financial model. That's a specific kind of gap that feels more embarrassing at 42 than it would at 26 because at 26, you're supposed to be learning. At 42, you're supposed to know.

What's the work actually like at a social sector boutique?

Different from Big 4 in ways that matter to me and similar in ways that surprise me. Different: the clients are nonprofits, health systems, foundations, and government agencies. The problems are about impact, not shareholder value. The budgets are smaller. The timelines are longer because nonprofit decision-making involves consensus processes that corporate clients don't have. A hospital CEO can decide to restructure a department in a meeting. A nonprofit executive director has to get board approval, funder sign-off, and staff buy-in, and each of those constituencies has a veto that they'll never call a veto but that functions as one.

Similar: the slide decks, the data analysis, the stakeholder management, the partner dynamics. I still build decks in PowerPoint. I still build models in Excel. I still sit in meetings where the client nods at my recommendation and then does something different for reasons that are political, not analytical. The universality of that experience across sectors is something nobody told me about. I thought consulting would be more rational than the nonprofit world. It's not. It's equally political. The politics just have different currencies. In nonprofits, the currency is mission alignment. In consulting, the currency is billable hours and partner approval. Both systems reward performance theater. Both systems punish honesty at inconvenient moments. The difference is that in consulting, the theater is explicit. Everyone knows the steerco is a performance. In nonprofits, the theater pretends to be authentic, which is worse because it corrodes the mission it claims to serve.

What's the thing that nobody prepares you for?

The guilt. Not career guilt. Mission guilt. I spent eight years telling funders and community members that workforce development was my life's work. I gave speeches. I wrote op-eds. I sat on panels at conferences and said things like "this work is about people, not programs." And then I left. I left the organization I built to go work at a consulting firm that charges $250 per hour for my time. The organization hired my replacement, a woman named Jess, who is competent and dedicated and who calls me occasionally to ask about institutional knowledge that I should have documented better before I left. Every time Jess calls, I feel a specific pang that I can only describe as: you said this was your life's work and then you left for a better job. The better job is better. The work is more intellectually stimulating. The pay, even at $13,000 less, will eventually exceed my ED salary as I move up. The learning curve is steep and satisfying. But the guilt doesn't care about any of that. The guilt is about the gap between what I said and what I did. I said the work was about people. I did the thing that was about me. Both were true at the time they were true. But the overlap is uncomfortable, and sitting in it at 43, with enough self-awareness to see exactly what I did and why, is a particular kind of accounting that nobody teaches you in case interview prep.