How some Employment Attorneys Think... (Not Us!)

Law Office of Vincent P. White
Law Office of Vincent P. WhiteMar 29, 2026

Why It Matters

Understanding these incentive misalignments helps claimants avoid under‑settlement and protects their financial recovery in employment disputes.

Key Takeaways

  • Some attorneys settle quickly for low fees, maximizing hourly rate.
  • 40% contingency can yield modest earnings from minimal work.
  • Clients often receive far less than potential claim value.
  • Poor evidence valuation leads to risky trial decisions.
  • Lawyer incentives may conflict with client’s best financial outcome.

Summary

The video critiques a subset of employment lawyers who prioritize rapid, low‑value settlements over maximizing client recoveries. It argues that these attorneys are driven by a self‑interest model where a modest contingency fee on a quick resolution yields a comfortable hourly rate, even if the claim’s true worth is far higher.

Key data points illustrate the misalignment: a typical 40% contingency on a $20,000 settlement translates to an $8,000 fee, or roughly $4,000 per hour if the case closes in two hours. The speaker notes that many lawyers accept such deals, effectively “throwing away” potential payouts that could reach $100,000, because the effort required to pursue the full value is disproportionate to their earnings.

A striking example quoted in the video describes an attorney settling a case in two hours for $20,000, walking away with $8,000, and feeling “thrilled” despite leaving the client undercompensated. The narrative also warns that clients who lack proper evidence valuation may be pushed toward risky trials, betting on juries they do not know.

The broader implication is that contingency fee structures can create conflicts of interest, prompting clients to scrutinize attorney incentives, demand transparent valuation of their claims, and consider alternative representation models to ensure they receive the full economic benefit of their workplace grievances.

Original Description

Comments

Want to join the conversation?

Loading comments...