#company

Posts mentioning hashtag #company

Below are all the posts — topics as well as replies — that mention the hashtag #company.

Mention #company in your post to continue the discussion!

Run don't walk...

Walgreens is doomed. A company that is firing so many people, and then giving artificial titles to try and keep others on board is a huge red flag. There is no future at WAG. The leadership team is a shell of talent, most 2nd or 3rd choices as the true talent left long ago. What once was an icon of a company stands an organization that simply cannot rise above the chaos. Within two years top, Walgreens will be no more......


it's time

for this company to focus on efficiency and deliverables. way too much drama and politics in the various offices. if you're not here to grow revenue, leave. leaders of you see these unaligned people, remove them.


Hubs Based Geographically

Companies that operate with a hub-based workforce model should align their teams geographically rather than scattering small numbers of employees across multiple states. When the majority of a department or function is concentrated in a primary hub, it makes operational, financial, and collaborative sense to place the entire team in that same location instead of maintaining one or two employees in various other states.

First, collaboration and communication improve significantly when teams are centralized. Even in remote environments, employees located within the same region or hub tend to share similar, leadership structures, and workplace culture. When teams are spread out as “one here and two there,” those individuals often become disconnected from the main group, making collaboration less efficient and creating unnecessary communication barriers.

Second, centralizing teams supports stronger leadership and accountability. Managers can more effectively support employees when their teams are structured in a clear and cohesive way. When a handful of employees are placed outside the main hub, they may receive less consistent oversight, mentorship, and integration into team processes. Bringing employees together in the dominant hub location creates clearer reporting structures and stronger team cohesion.

Third, there are cost and operational efficiencies. Supporting employees in multiple states often introduces additional administrative complexity such as payroll compliance, state-specific regulations, and HR management differences. Consolidating teams in the primary hub reduces these complexities and allows resources to be focused where the company already has the strongest infrastructure.

Finally, a hub model should actually function like a hub. The purpose of a hub is to concentrate talent, resources, and collaboration in one central location. Maintaining scattered employees across various states contradicts the very concept of a hub structure and weakens the benefits that such a model is intended to provide.

For these reasons, companies that promote a hub-based workforce strategy should ensure that teams are largely located within the same primary hub rather than distributing small numbers of employees across multiple states where they operate in isolation from the core teams.


Perrigo Announces Seven Percent Workforce Cut

Perrigo plans to reduce its workforce. The pharmaceutical company expects to lay off 7% of its employees. This action aims to streamline operations and enhance effectiveness. The information comes from Perrigo's fiscal year 2025 report. Further details on affected departments were not provided.

https://wkfr.com/west-michigan-perrigo-layoffs/


Ssense Reports 215 Recent Layoffs After Founder Buyout

Ssense reported 215 layoffs last month to the Quebec government. This brings the total to 307 layoffs over the past year. The luxury online retailer filed for bankruptcy protection in August. Founders recently received court approval to buy back the company. Lenders opposed the buyout, favoring liquidation for debt recovery.

Montreal, Quebec

https://montrealgazette.com/business/local-business/ssense-reported-over-200-layoffs-last-month-to-quebec-government


Morgan Stanley - March 2025 Layoffs Summary (some selected post)

# Morgan Stanley Layoff Report — March 4, 2026
Source: TheLayoff.com | Thread: Morgan Stanley WM/Tech RIF
Thread ID: @OP+1kjtkpz73
Views: 8,754 | Replies: 60 | Last Activity: 8 hours ago (as of report generation)


## Executive Summary

On March 4, 2026, Morgan Stanley carried out a significant reduction in force (RIF) affecting its Wealth Management (WM) and Technology divisions globally. The Wall Street Journal pegged the cuts at approximately 2,500 employees, representing roughly 3% of the total workforce (@ez). The layoffs rolled out across time zones throughout the day, beginning in Asia and progressing through EMEA and North America. Affected employees reported being escorted out of offices, receiving garden leave notices, and in some cases discovering their severance was capped below what their tenure would suggest. No WARN Act filings were identified by thread participants ahead of the event.


## Scale & Official Confirmation

The thread was initiated by Anonymous 72 (@OP+1kjtkpz73) on March 4, who confirmed the RIF for WM was set to occur that day. The original post was made approximately one day before widespread reporting emerged.

The scale was subsequently corroborated by a user citing Wall Street Journal coverage (@ez):

"Wall Street Journal just posted a story. Said 2,500 or 3% of the workforce."

This figure places the event among Morgan Stanley's more significant recent headcount reductions. The thread notes no advance WARN Act filings were identified in the US (@eg, @dq), which generated discussion — one user speculated this may be because the majority of cuts were concentrated outside the US (@dr), which would exempt the firm from domestic filing requirements.


## Geographic Scope

Layoffs were confirmed or credibly reported across at least six cities spanning four countries, suggesting a coordinated global action rather than a regionally isolated restructuring.

### Asia (First Wave)
The thread noted that March 4 arrived in Asia first, and that the RIF had "started" there (@b6). Specific details from Asian offices were limited in the thread.

### London & EMEA (Second Wave)

  • A London equities employee reported being told their position was at risk (@cw).
  • Tech in London was independently confirmed as affected (@d0).
  • One user reported that London had "finished" processing before the US wave began (@dn), suggesting a structured, time-zone-sequenced rollout.
  • An EMEA-wide mandatory call for tech staff was reportedly called on short notice (@cp).

### Glasgow

  • Affected divisions confirmed: finance, legal, and cyber security (@dd).
  • Notably, one user suggested the cuts in Glasgow may have begun as early as mid-February, with several VPs disappearing around February 15 on apparent "leave" of 1.5–2 months — interpreted by the poster as quiet separations ahead of the formal RIF date (@dd).
  • One IB employee in Glasgow confirmed their role was designated "at risk" and that a 30-day consultation period had commenced (@f8).

### Montreal

  • Tech division confirmed affected (@ed).
  • One employee reported a colleague was escorted out of the office with all her belongings (@ef).
  • An Executive Director in Montreal was confirmed let go (@ey).

### New York

  • WM Operations confirmed affected; at least one employee confirmed they were laid off (@dj).
  • A 28+ year veteran (VP L4, tech) in NYC confirmed separation (details in Severance section below) (@dv).

### Alpharetta, GA

  • Confirmed affected (@dk).

### Arlington, VA

  • Multiple people escorted out of the Arlington office (@er).

## Seniority of Those Affected

Reports suggest the RIF was not limited to junior employees. Confirmed or reported senior separations include:

Title Location Division Source
VP L4 (28+ yrs) New York Technology @dv
Executive Director Montreal Unspecified @ey
VP(s) Glasgow Unspecified @dd
IB Employee (role at risk) Glasgow Investment Banking @f8
Equities Employee London Equities @cw

The presence of EDs and senior VPs in the affected pool suggests this was a performance-agnostic cost reduction exercise rather than a targeted performance-based action.


## Severance & Compensation Details

One of the most detailed firsthand accounts came from a 28+ year NYC VP (L4) in technology (@dv):

  • Placed on garden leave through June 30, 2026
  • Severance was described as capped, despite tenure exceeding the cap threshold
  • The poster noted "there were good things there and better things ahead"

A follow-up post from another affected employee (@dx) added:

  • Received 3 weeks of severance per year of service, but capped at 15 years despite 20 years of actual tenure

This cap drew scrutiny. Anonymous 72 (@e4) noted the cap represents a specific dollar ceiling tied to officer title, and that it may be legally challengeable since the cap threshold is never disclosed to employees prior to a RIF.

A separate user confirmed there is an internal HR website listing the dollar caps by title (VP/ED/MD) (@e7), though the URL was not publicly shared in the thread.


## Process & Transparency Concerns

Several users raised concerns about how the RIF was handled procedurally:

  • No WARN Act notices identified for the US as of the time of posting (@eg, @dq). One user noted this may be because the cuts were primarily non-US in focus (@dr), which would exempt the firm from the 60-day advance notice requirement under the federal WARN Act.
  • No advance media coverage — multiple users expressed surprise that a reduction of this scale had not appeared in the press beforehand (@b5, @dq).
  • One user speculated the March 4 date may not represent the end of reductions, suggesting a rolling layoff model in which additional divisions (e.g., Banking, non-tech WM) could follow in subsequent weeks (@ds).
  • The Glasgow situation (@dd) raises the possibility that some separations were being quietly processed weeks before the official RIF date, which would be consistent with a rolling or pre-staged reduction strategy.

## Division Breakdown

Based on thread reports, the following divisions were mentioned as affected:

Division Locations Mentioned
Wealth Management (WM) New York, US broadly, Asia
Technology Montreal, London, Glasgow (Cyber), Alpharetta, EMEA
Operations (WM) New York
Investment Banking (IB) Glasgow
Equities London
Finance & Legal Glasgow

## Notable Contested Claims

Two posts (@e9, @ej) made claims alleging that layoffs disproportionately targeted white employees and attributed this to managerial bias. These posts received heavily split reactions (roughly equal upvotes and downvotes) and generated significant sub-thread debate. They are noted here for completeness but:

  1. Are not independently verifiable from thread content
  2. Represent individual perceptions, not documented patterns
  3. Should not be treated as factual reporting absent external corroboration

## Key Open Questions (As of Report Date)

  • Will additional RIF waves affect Banking and non-tech WM, as speculated in @ds?
  • Are severance caps legally defensible given the non-disclosure issue raised in @e4?
  • Did Glasgow separations beginning ~February 15 (@dd) constitute a pre-staged RIF, and does this affect WARN Act or UK employment law compliance?
  • What is the total headcount impact in each geographic region?

  • Report compiled from user posts on TheLayoff.com thread @OP+1kjtkpz73. All information is sourced from anonymous employee accounts.