Woodland Tools Inc. v. Fiskars Brands, Inc.

CourtDistrict Court, W.D. Wisconsin
DecidedMay 24, 2024
Docket3:22-cv-00540
StatusUnknown

This text of Woodland Tools Inc. v. Fiskars Brands, Inc. (Woodland Tools Inc. v. Fiskars Brands, Inc.) is published on Counsel Stack Legal Research, covering District Court, W.D. Wisconsin primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Woodland Tools Inc. v. Fiskars Brands, Inc., (W.D. Wis. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF WISCONSIN

FISKARS FINLAND OY AB and FISKARS BRANDS INC.,

Plaintiffs, v. OPINION and ORDER

WOODLAND TOOLS INC., LUMINO, INC., 22-cv-540-jdp ROSS GUNDLACH, VANCE KOCH, and STEPHANIE COTA,

Defendants.

This case arises from a dispute between competitors in the hand-held gardening tool industry. Plaintiffs Fiskars Finland Oy Ab and Fiskars Brands Inc. allege that defendants Woodland Tools Inc. and Lumino, Inc. poached Fiskars’ employees and misappropriated Fiskars’ trade secrets and confidential information to unfairly compete with Fiskars. Fiskars asserts claims for trade secret misappropriation, breach of contract, tortious interference, and breach of duty. Fiskars also asserts claims for false advertising and patent infringement. Defendants countersued, seeking to invalidate the two design patents at issue, and claiming tortious interference.1 Before the court are Fiskars’ four motions to compel defendants to produce a wide range of information. For the reasons below, the court will deny Fiskars’ motion to compel production of source code and grant in part and deny in part each of the remaining three

1 Unless otherwise specified, “defendants” refers to the two corporate defendants, Woodland and Lumino. motions. The court will also reset certain case deadlines to allow the parties sufficient time to review and comply with these rulings.

ANALYSIS A. Fiskars’ motion to compel source code, dkt. 98.

Fiskars’ first motion seeks to compel “source code, data sets, and other programming artifacts.” Dkt. 98. The motion is ostensibly premised on 22 document requests, id. at 4, but Fiskars does not address the requests individually; rather, it takes a more all-encompassing approach. Essentially, Fiskars asks the court to compel defendants to provide all source code, data files, and other documentation that defendants use in connection with point of source (POS) data for 12 retailers. Fiskars provides a chart in its motion purporting to show the gaps between what it has requested and what defendants have provided. Id. at 4. In a vacuum, the court would generally be receptive to this request for court

intervention. This case is, in part, a trade secret case involving alleged misappropriation of source code, so requests seeking production of source code and related data are an expected part of discovery.2 This is particularly true here, considering the specific (supported) allegations that defendant Vance Koch e-mailed Fiskars’ POS source code and data to his personal e-mail account prior to leaving Fiskars and then downloaded that same source code and data to his work laptop after he began work with defendants. Dkt. 94-2, Koch Dep. Tr., at 152:20-153:23, 155:17-156:4.

2 The court will grant motions to compel production of or access to source code in trade secret cases when the standard is met. See e.g., Distefano v. Nordic Consulting Partners, Inc., No. 3:23- cv-00657-wmc, Dkt. 75, Order (W.D. Wis. May 17, 2024). But Fiskars’ request is not made in a vacuum. Fiskars brought this motion to compel late—over three months after the liability expert disclosure deadline. Compare Dkt. 33 at 6 (liability expert disclosures due October 20, 2023) with Dkt. 98 (motion filed February 7, 2024).3 Fiskars concedes that the information it seeks to compel is the sort of information

that requires expert analysis. Dkt. 98 at 12 (correspondence from Fiskars’ counsel discussing how an expert would analyze the information). In fact, Fiskars’ liability expert complained about the lack of source code information in his report. Dkt. 82-3 at 24–25. Fiskers seeks to remedy the situation by asking the court to order an inspection of defendants’ computer systems, dkt. 98 at 2, but Fiskars did not notice an inspection until the filing of this motion, id. at 13 n.10—again, over three months after the liability expert disclosure deadline.4 So, Fiskars would need to supplement its liability expert’s report for the information it now seeks to compel to have an impact on the case. And Fiskars would need leave from the

court to do so—it conceded as much when it filed a motion seeking to amend the case schedule. Dkt. 76. But the court has already denied Fiskars that very relief. Dkt. 85 (“the court finds

3 It appears from the filings that the parties moved the liability expert disclosure deadline from October 20, 2023 to November 2, 2023. Dkt. 76 at 1–2; Dkt. 82-3 at 28. The parties may move these types of disclosure deadlines by agreement without leave of court. The later agreed- upon deadline does not change the court’s analysis. 4 The parties informed the court in their status updates that this inspection did not go forward as noticed. Defendants seem to believe the appropriateness of the inspection rises and falls with Fiskars’ motion. Dkt. 197 at 2–3. Fiskars disagrees, arguing the inspection is separate and apart. Dkt. 200 at 2. But it was Fiskars that proposed that the inspection act as a remedy for defendants’ alleged lack of production. Dkt. 98 at 2, 13 n.10. The court will not decide whether the inspection should have progressed in the natural course, as Fiskars did not bring an independent motion to compel the inspection once properly noticed and conferred upon. Suffice to say, an inspection is not ordered as a remedy here. that plaintiffs have not established good cause to justify another round of liability reports”). The court will not revisit this ruling via a belated motion to compel. The bottom line is this: Even if the court were inclined to compel production of source code and related documents, that information would be unusable in this litigation absent a

dramatic upheaval of the schedule. It is true that information need not be admissible to be discoverable, but there are other considerations at play, including “whether the burden or expense of the proposed discovery outweighs its likely benefit,” Fed. R. Civ. P. 26(b)(1). Here, the burdens associated with the proposed discovery, including re-doing liability expert reports and depositions, are heavy; and the likely benefits, given the elapsed deadlines, are nil. The court will deny Fiskars’ motion for this reason alone. There are other problems with Fiskars’ motion, which the court will discuss briefly for completeness. Fiskars asks the court to compel information missing from a 5x13 chart. The

chart lists retailers on the y-axis and “steps” for which Fiskars “would have expected to receive” source code and data files on the x-axis. Dkt. 98 at 7. But that is not what the requests that Fiskars propounded on defendants seek. Id. at 4. For the most part, the requests were limited to information related to Python code that Koch and/or the defendants developed or used to analyze POS data.5 This makes sense, because the Fiskars source code that Koch allegedly e- mailed himself was Python code used to analyze POS data. See Dkt. 94-2, Koch Dep. Tr., at 39:21-40:10. After receiving the requests, defendants produced the source code they used for POS data that was written in Python. Dkt. 111 at 4-5.

5 The parties agree that Python is a human-readable programming language. Dkt. 98 at 2 n.4; Dkt. 111 at 2 n.2. Fiskars is unsatisfied, now asking for all “POS source code, data files, and other programming artifacts” regardless of programming language. Dkt. 98 at 2. But Fiskars hasn’t connected the dots between the alleged stolen trade secrets and this broader request. Perhaps it is possible, or even plausible, that the Python code and data that Koch allegedly stole could

be helpful to developing code and data in other languages, but that point hasn’t been explained or supported for this motion.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Woodland Tools Inc. v. Fiskars Brands, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/woodland-tools-inc-v-fiskars-brands-inc-wiwd-2024.