Nahum v. The Boeing Company

District Court, W.D. Washington·Decided July 24, 2020·No. 2:19-cv-01114·Unknown

Opinion

UNITED STATES DISTRICT COURT AT SEATTLE SETONDJI VIRGILE NAHUM Case No.: 19-cv-01114-BJR Plaintiff, ORDER DENYING MOTION TO v. COMPEL THE BOEING COMPANY, et al. Defendants.

I. INTRODUCTION Plaintiff Setonji Nahum (“Plaintiff”)1 brings this employment discrimination action against The Boeing Company (“Boeing”) and one of its managers, Jeffrey Dillaman, (collectively, “Defendants”) in which he asserts several employment-related causes of action. Currently before the Court is Plaintiff’s motion to compel discovery, which Defendants oppose. Dkt. Nos. 70, 73. Having reviewed the motion, opposition thereto, the relevant legal authority, and the record of the case, the Court will deny the motion. The reasoning for the Court’s decision follows.

1 Plaintiff is pro se. Plaintiff served Defendants with his first request for written discovery and production of documents on October 1, 2019. Dkt. No. 70, Ex. A. Defendants responded to the discovery request on March 27, 2020.2 Plaintiff alleges that Defendants’ document production was insufficient and,

as such, in mid-April 2020, the parties held a meet and confer conference to discuss Plaintiff’s concerns regarding Defendants’ production.3 During this telephone conference, Plaintiff identified additional materials that he wanted Defendants to produce.4 Defendants allege that Plaintiff’s 2 Defendants alleged that they produced the following documents in response Plaintiff’s discovery request: • Plaintiff’s personnel file, including his application materials, training history, performance evaluation, and payroll records; • Plaintiff’s labor relations file, including documents related to his union grievances of his corrective actions and communications with union representatives; • Boeing’s file on Plaintiff’s EEOC charge, including investigation materials, witness statements, and submissions to the EEOC; • Boeing’s file on Plaintiff’s unemployment claim; • Investigation files maintained by Boeing’s fact-finding investigators, including emails and substantive work product, relating to Plaintiff’s corrective action and discharge; • Investigation files maintained by the Boeing’s EEO and Ethics departments regarding Plaintiff’s challenges to his corrective actions; • substantive work product, that Plaintiff himself submitted to the investigator to support his claims that corrective action was unwarranted; • Documents regarding Plaintiff’s performance maintained by Plaintiff’s manager, Jeffrey Dillaman, including emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact-finders and investigators; • Documents regarding Plaintiff’s performance maintained by Plaintiff’s second-level manager, including organizational charts, emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact- finders; • All SATs assigned to Plaintiff during his employment, including, but not limited to, those related to his corrective actions; • All PPCR reports assigned to Plaintiff during his employment, including, but not limited to, those related to his corrective actions; and • Relevant company policies. Dkt. No. 74 Declaration of Kathryn J. Ranieri at ¶¶ 6, 8 3 Defendants have their own concerns regarding Plaintiff’s response to their discovery requests but have not yet moved to compel his responses, but continue to attempt to resolve this issue without this Court’s intervention. 4 Defendant requested the following additional documents: • Documents related to his work stored on Boeing’s shared files; • Bar charts and doors packages for control codes 304BM, 306, and 307; • Bar charts from the analyst who held Plaintiff’s position before him; • Governing protocols for PPCRs; • Line of Balance data; • Correspondence/documents evidencing other employees saying that they refused to work with Plaintiff; and request for additional material was overbroad, unduly burdensome, and irrelevant; nevertheless, Defendants agreed to “search[] for and collect[] [the] additional documents”. Dkt. No. 74, Declaration of Kathryn J. Ranieri at ¶ 15. Thereafter, on June 11 and 16, 2020, Defendants produced “all work files uploaded by Plaintiff to his team’s shared folders, all bar charts in the

shared folder from both Plaintiff and the preceding analyst in his role, Line of Balance files, PPCR authoritative documents, and additional email correspondence regarding Plaintiff’s work product.” Dkt. No. 73, (citing Ranieri Decl. at ¶ 21). Defendants allege that with this production, they have produced all documentation responsive to Plaintiff’s discovery requests that is relevant to his claims in this lawsuit. Plaintiff disagrees. He claims that “[D]efendants ha[ve] not shown any desire to take [his] request for discovery seriously. Instead the [D]efendants have been producing whatever [they] wish[] to produce as opposed to providing clear answers to the discovery and actually sufficiently satisfy the plaintiff’s request for discovery.” Dkt. No. 70 at 2-3. He complains that Defendants have produced “disjointed email communication, non-genuine material, and multiple set[s] of

irrelevant materials.” Id. at 2. He also alleges that the “font and formatting” of the documents produced indicate that Defendants “have been t[a]mpering with the evidence in this federal case.” Id. at 4. Therefore, Plaintiff requests that this Court order Defendants to promptly comply with his outstanding discovery requests. Federal Rule of Civil Procedure (“FRCP”) 37(a)(1) provides that in the event a party does not respond to a discovery request the proponent of the discovery “may move for an order compelling disclosure or discovery.” Fed. R. Civ. Pro. 37(a)(1); see also Lim v. Franciscan Health • Documents related to an audit he performed as an independent contractor. Dkt. No. 73 at 5. Systems, 2006 WL 3544605, *1 (W.D. Wash. Dec. 8, 2006) (“Where the response to discovery is unsatisfactory, the party seeking discovery may file a motion to compel discovery . . . .”). The movant must certify that he has “in good faith conferred or attempted to confer with the person or party failing to make disclosure or discovery in an effort to obtain it without court action.” Fed. R.

Civ. Pro. 37(a)(1). The movant bears the burden of informing the Court: “(1) which discovery requests are the subject of his motion to compel, (2) which of the [] responses are disputed, (3) why the responses are deficient, (4) the reasons [the] objections [if any] are without merit, and (5) the relevance of the requested information to the prosecution of his action.” Hupp v. San Diego County, 2014 WL 1404510, *2 (S.D. Cal. April 10, 2014) (citing Brooks v. Alameida, 2009 WL 331358, at *2 (E.D.Cal. Feb.10, 2009) (“Without knowing which responses plaintiff seeks to compel or on what grounds, the court cannot grant plaintiff's motion.”)). Defendants object to Plaintiff’s motion to compel on two grounds. First, they charge that the motion is procedurally deficient because Plaintiff failed to exhaust the meet and confer

Free access — add to your briefcase to read the full text and ask questions with AI

Nahum v. The Boeing Company, (W.D. Wash. 2020).

Nahum v. The Boeing Company (Nahum v. The Boeing Company) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.