Home / MEMO: Shrimp and Weenies

Shrimp and Weenies

Interesting Memo

May of 1993 by Mike Murray, Microsoft’s head of human resources, the message encouraged frugality in the company’s rank and file with this simple message: “One of the reasons we’re successful (and wealthy) is because we’ve been serving weenies (not shrimp) for the past 17 years! No need to change the menu.”

The core tenets of Microsoft’s “Shrimp and Weenies” memo revolve around promoting fiscal responsibility and curbing extravagant spending within the company. It emphasizes the importance of a modest, cost-efficient approach to employee perks and resource allocation, advocating for a culture where every expense is carefully considered and justified.

Read the Memo Collection
MEMO: Shrimp and Weenies

The “Shrimp and Weenies” memo authored in May 1993 by Mike Murray, then head of human resources at Microsoft, is a fascinating artefact of a particular era when they were still hustling.

You’ll see the memo and learn a little more about it.

Overview

1993 was a pivotal year for Microsoft. The company had just launched Windows 3.1 to significant acclaim and was steering Office towards industry dominance.

However, the early 90s were also marked by economic challenges, including a recession. It was within this context that Murray penned his memo, aimed at instilling a sense of frugality among Microsoft’s employees. The core message was simple yet striking: Microsoft had achieved its success and wealth by being economical (serving “weenies” instead of “shrimp”), and there was no need to deviate from this proven path.

The memo became a part of Microsoft lore, resonating beyond the company’s walls. It was seen as a reflection of Microsoft’s corporate ethos at the time – a blend of frugality, practicality, and a slight touch of eccentricity.

The media coverage generally viewed it as an interesting peek into the internal culture of a rapidly growing tech giant.

Key Learning Points from Microsoft’s “Shrimp and Weenies” Memo

The “Shrimp and Weenies” memo from Microsoft, along with Steven Sinofsky’s reflections, provides several key learning points:

  • Economic Context and Microsoft’s Paranoia: In 1993, amidst a broader economic downturn, Microsoft faced its own challenges. There was a fear within the company that the PC market had reached saturation, a concern amplified by the general recession. This backdrop set the stage for the memo, with Microsoft grappling with complacency and the fear of a potential downturn in their own success.
  • Risks and Company Reputation: The memo was a bold move, especially considering Microsoft’s image at the time. Referred to as a “Velvet Sweatshop” in 1989, the company had a reputation for providing a comfortable yet demanding work environment. Introducing cost-cutting measures risked exacerbating employee concerns about work conditions.
  • Memo’s Key Elements:
    • Shrimp and Weenies Analogy: Murray’s memo emphasized frugality with clear guidelines: “…we fly coach class; we stay in reasonably priced hotels; we don’t ride in limos; we don’t have executive dining rooms; our office furniture is of good quality, but reasonably priced; when dining at company expense, we order weenies not shrimp.”
    • T-shirts and Stupid Dog Tricks: The memo critiqued unnecessary expenditures, like the growing practice of handing out T-shirts for trivial reasons, stressing that they should be a reward for significant achievements like shipping a product on time.
    • Headcount Growth Philosophy: The memo explained Microsoft’s “n-1” theory of headcount growth – if a task needs five people, allocate four, exemplifying what Murray termed “weenier thinking.”
    • Cultural and Organizational Impact:
      • The memo was a critical cultural touchstone, especially in a company known for its modern, lean approach. It emphasized the importance of aligning with the company’s values and the customer’s needs.
      • The analogy of “shrimpy” behavior became a shorthand within Microsoft for practices not aligned with the company’s ethos.
    • Internal Support and Reinforcement:
      • Following the memo, an OpEd titled “Microsoft Did Not Promise You Club Med” was published in the company’s newsletter, “MicroNews”. It supported the memo’s themes and criticized those who were resistant to these changes, emphasizing the need to align with the company’s frugal and practical ethos.

Steven Sinofsky Twitter

The “Shrimp and Weenies” memo from Microsoft in 1993, authored by HR head Mike Murray, was a pivotal moment in the company’s history, symbolizing a shift towards cost-efficiency and frugality. This memo, written during a time of economic downturn and corporate expansion, aimed to clamp down on lavish spending and promote a culture of financial responsibility. It emphasized the importance of modesty in employee perks, spending, and headcount growth, encapsulating the idea that frugality contributed to Microsoft’s success.

Steven Sinofsky, a former Microsoft executive, reflects on this memo and its long-term impact in a Twitter thread. He notes that the memo led to a cultural shift within the company, where employees began to view company funds as shareholder and investor money rather than their own. This mindset was exemplified by his personal experience in 1991, where he, like a school teacher, paid for a team t-shirt out of his own pocket, seeing it as part of his job.

However, Sinofsky points out that this frugal approach did not last indefinitely. By 2004, Microsoft faced challenges in maintaining this culture, as evidenced by the controversy over the removal of free gym towels, which were later reinstated in 2006. This incident highlighted a growing sense of entitlement among employees.

Sinofsky also mentions the broader implications of this cost-cutting culture in the tech industry. He notes that some companies, like Google, recognized the potential downside of excessive perks and benefits, which could be “penny wise and pound foolish.” He also comments on rumors about Google cutting back on PC purchases, emphasizing the significant financial implications of such decisions.

The thread underscores that the issues addressed in the “Shrimp and Weenies” memo are not unique to Microsoft or the tech industry but are common challenges for growing companies. Sinofsky observes that at scale, there’s a tendency for cost and savings responsibilities to be diffused among various groups within a company. He concludes that the stages of cutbacks experienced by Microsoft and other tech companies are a natural evolution and part of a “mean reversion” or cultural reset that every scaling company must navigate.

Steven Tweeted. I’ve provided his commentary, but you can read the original here.

  1. One of the most famous memos in all of Microsoft history was a first memo about cost-cutting which came about in 1993 (see early 90s recession). Mike Murray, leading HR, wrote the memo “Shrimp and Weenies”—before MS, Mike was at Apple, having led OG Mac marketing. 1/ (third try)
  2. The company was going through challenges like much of the macro-economy. Only we were worried “maybe this is it? PCs are saturated—MSFT paranoia. GDP was down. Sales were slowing. We were getting complacent.
    1. Still, memo could have backfired. MS in 89 was a “Velvet Sweatshop”
  3. Yet the memo had not only the intended effect but it was a (re-)turning point for the company. Mike wrote about 3 challenges—things we needed to change—featuring allegories we would never forget.
  4. Shrimp and Weenies: “…we fly coach class; we stay in reasonably priced hotels; we don’t ride in limos; we don’t have executive dining rooms; our office furniture is of good quality, but reasonably priced; when dining at company expense, we order weenies not shrimp.”
  5. T-shirts and Stupid Dog Tricks “…T-shirt can and should be a great team building device for a group … (i.e., shipping a product on time). On the other hand, we need to halt the growing practice of handing out random T-shirts…for simply attending a required business meeting.
  6. Headcount Growth & Lack Thereof “The company has always enjoyed an “n-1” theory of headcount growth. If a task absolutely, positively needs 5 people in order to get the work done, we allocate 4 heads to the task (and the work does get done). This is classic weenier thinking.”
  7. The Bottom Line – “Excess will destroy success. Is your team fueled by weenies or shrimp?”
  8. In a company with private offices, casual dress (a thing), and prided itself on being modern and lean this was a big huge deal. Every company was experiencing “belt tightening” but this seemed different because we were a symbol of national success. This could have backfired.
  9. Instead it became a cultural touchstone—much like how BillG thought of the company 15 years earlier which was to always have cash on hand to meet payroll for a year. The idea of being “shrimpy” was a shortcut for not being aligned with the company, customer, etc.
    1. 9A/ An OpEd to the weekly printed newsletter “MicroNews” a month later in support of Shrimp & Weenies going against the hold-out whiners was titled “Microsoft Did Not Promise You Club Med” and was widely posted on doors (we still had those).
  10. People started to talk about money not as their own but as shareholder and investor money. I was reminded of my first t-shirt in 91 I made for the team which I paid for myself and like a school teacher buying supplies was just part of the job.
  11. This didn’t last forever. As Mike warned us, being a big company is a constant fight to avoid Shrimp. In 2004 (other tough times) we famously did away with free (to use) gym towels—a favorite of joggers and bikers alike. The company practically imploded. Towels retuned in 06.
  12. The key failure was a sense of entitlement had taken over. Some companies in the news today are struggling with this reaction.
    1. One company took a forward-looking view saying perqs and other benefits could easily be “penny wise and pound foolish”. Here’s Google’s S-1
  13. Not to “told you so” but there is no way this was going to last. I’d been battling these benefits in recruiting for a couple of years and just “knew”.
    1. 13A/ Google is even rumored to be cutting back on PC purchases. Oh my!
    2. Being well-known for being thoughtful (aka frugal) in this regard, do the math. $5000/year for R&D can easily be $250M dollars domestic. And what gain (esp for a cloud company!) But Sheets and Slides, yikes!
  14. Many are using the “tech layoffs” to pile on to anti-BigTech or Silicon Valley. That would be dumb. As Mike noted, this is not unique to tech in any way. It is a product of scale.
    1. At scale, everyone thinks some other group will make up for costs/savings. Just a fact.
  15. These stages of cutbacks are a natural evolution not just of tech companies but all companies. It is sad that it happens and feels like a cultural reset or “mean reversion”. It is. Scale is a challenge for every company and this is one of the steps.

 

Video from the Mike Murray

I found a video with Mike Murray where he jokes about the memo. You can see it here:

Memo: Shrimp and Weenie Guidelines

Shrimp and Weenie Guidelines

As you finalize FY94 budgets and prepare for the next fiscal year, the following set of reminders and guidelines are provided as a convenience.

1. Shrimp and Weenies

As one drives into Reno, Nevada there is a sign saying, “Reno, the biggest small city in the world.” One might wonder if we should erect a similar sign at our entrance, “Microsoft, the biggest small company in the world.” When you think small, you don’t spend big. Every penny counts, every new headcount is precious, and you feel personally accountable for the top line (revenue), the bottom line (profitability), and all the stuff in between.

Novell recently announced (yet another) record quarter of revenue growth and profitability. The frosting on this cake was to lay off 4% of their 3,600 employees. Novell is serving weenies, not shrimp.

Much of what we do is symbolic, yet this becomes the current upon which our corporate culture rides. Microsoft’s corporate culture is perpetuated by visible actions, not by a list of values printed on coffee mugs.

It is true that we lead by example, and due to growth in headcount, many employees now watch these examples from distant binoculars–we no longer enjoy the small company luxury of rubbing shoulders with all employees on a daily basis. So it is important that some of these symbolic actions remain quite visible: we address each other on a first name basis; we have an informal dress code; we fly coach class; we stay in reasonably priced hotels; we don’t ride in limos; we don’t have executive dining rooms; our office furniture is of good quality, but reasonably priced; when dining at company expense, we order weenies not shrimp.

It’s important that our administrative assistants, event planners, and managers see it, hear it and get it:

Given the choice, we prefer weenies over shrimp. (Lest we throw the baby out with the bath water, there are legitimate times for shrimp, but these are the exception, not the rule).

With no guidance from management, the path of least resistance propels one to the “bigger is better” mindset. This is clearly evident today in the number of fancy catered lunches being served thoughout the company. The world’s preoccuptation with Microsoft’s success can confuse the issue. One of the reason’s we’re successful (and wealthy) is because we’ve been serving weenies (not shrimp) for the past 17 years! No need to change the menu.

2. T-shirts and Stupid Dog Tricks

David Letterman has “stupid dog tricks.” Microsoft has “stupid, unneeded T-shirts.” Yet dog is man’s best friend and T-shirts are an integral part of our culture. So where do we draw the line? Not only is it easy to go overboard on this stuff, there has also been a recent phenomenon of “one-ups-manship” within the company. It would not be surprising to see Gucci leather jackets with the MS logo as a reward for attending a required meeting, or for successfully moving from one building to another!

The line seems fairly clear: Each department in the company has an employee morale budget. For FY94 it is recommended that this budget be based on the number of people in the department multiplied by (no more than) $20/month. The resultant number becomes the department’s fiscal year employee morale budget. This budget should be used to recognize individual and group achievement, including product ship parties. T-shirts, sweatshirts, department parties, special one time bonuses, an expense paid weekend away for a deserving employee, etc. all come from this budget–and ONLY from this budget. If your group has an annual holiday party (separate from the company sponsored Holiday Party), then it too comes out of this budget. The local management team is empowered to determine best use of these funds.

A well designed T-shirt can and should be a great team building device for a group and/or a reward for the achievement of a key goal (i.e., shipping a product on time). On the other hand, we need to halt the growing practice of handing out random T-shirts and other goodies for simply attending a required business meeting.

Large events, such as sales meetings, have separate budgets. T-shirts, trash and trinkets, etc. should be included in the overall budget for these events–they should not be in the employee morale budget.

3. Headcount growth — and the lack thereof

Mike Maples has created a spreadsheet that clearly shows how headcount growth, even when it is a smaller percentage than revenue growth, can dampen corporate profitability. The company has always enjoyed an “n-1” theory of headcount growth. If a task absolutely, positively needs 5 people in order to get the work done, we allocate 4 heads to the task (and the work does get done). This is classic weenier thinking. We must reinforce this principle as we face headcount growth pressure in FY94.

At the Exec Retreat (Feb 93) a recommendation was made that we carefully evaluate the effectiveness of our lowest performing employees. Microsoft managers are responsible for weeding out the non-performers, and HR is responsible for providing managers with the competence to know how to do this. We need to work in partnership with this. If you feel that you need specific training from HR, please contact your HR representative immediately.

A current popular “trick” is to give an employee a 3.0 rating (when they truly deserve a 2.0 rating). The manager then gives the employee the private message that they should look for a new job in another group at MS. The manager is avoiding the painful task of getting the person out the door and thus “hands off” their problem to an unsuspecting group. This is crazy garbage. HR is committed to helping you build strong teams and to weed out the non-performers. If we identify our weak performers early on, we can move quickly to either a recovery strategy or an exit strategy.

Some groups may not receive all the headcount they feel they need in order to accomplish their objectives. These groups are encouraged to do some “spring cleaning”. Most employees will not volunteer that they are working on useless or no-longer-necessary projects! But some are!! In each of our organizations we are using processes that may be outmoded and no longer needed. Look for ways of streamlining and re-engineering your work flows. This will often “free up” some headcount that can be redeployed to higher priority projects.

The Bottom line

As companies grow, and Microsoft is no exception, there is a tendency for managers to assume that someone, someplace is making sure we don’t “mess up.” The fact is that the responsibility belongs with each of us. Excess will destroy success. Is your team fueled by weenies or shrimp?

Microsoft’s success is not guaranteed. The challenges of running a 14,000+ employee organization are huge. But our employees represent an enormously talented, self-motivated asset. To the degree that we can empower these resources, and provide constructive guidance and leadership, we can and will continue to succeed. Hopefully the above messages will help you in your efforts.

 

You can read the rest of the memo collection here:

Memo collection

    Get in the game

    Free tools and resources like this shipped to you as they happen.

    Comments (0)

    There are no comments yet :(

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    Leave a Reply

      Join Our Newsletter

      Get new posts delivered to your inbox

      www.alexanderjarvis.com