Professional Documents
Culture Documents
Amazon v. Brian Hall - Response Re: Google Cloud Next
Amazon v. Brian Hall - Response Re: Google Cloud Next
1 FILED
2 2020 JUN 10 09:00 AM
KING COUNTY
3 SUPERIOR COURT CLERK
E-FILED
4 CASE #: 20-2-08977-0 SEA
14 INTRODUCTION
15 The majority of Amazon’s motion argues baselessly Brian Hall cannot work in his
16 permanent role as Vice President of Product Marketing, Cloud at Google LLC. In practical
17 terms, however, this motion has nothing to do with Hall’s anticipated permanent role, and neither
18 Google nor Hall have suggested in any way to Amazon that Hall will imminently begin work in
19 that role. Rather, as Google and Hall have repeatedly informed Amazon, Google will continue
20 voluntarily to hold Hall out of his permanent role until the Court has an opportunity to rule on
21 Amazon’s forthcoming motion for a preliminary injunction.
22 Instead, the issue before the Court today is a narrow one. Amazon has asked the Court to
23 enjoin Hall (1) from editing a series of speeches that Google has already prepared for an
24 upcoming conference; and (2) from continuing an organizational advice role to which Amazon
25 has already consented—and which Amazon itself admits in its motion is a “non-competitive”
26 position. To be clear, those are the only two projects on which Google currently seeks to have
27 Hall work. Nevertheless, Amazon believes (to borrow a phrase from its motion’s introduction)
ANGELI LAW GROUP LLC
DEFENDANT BRIAN HALL’S OPPOSITION
121 S.W. Morrison Street, Suite 400
TO PLAINTIFF AMAZON.COM, INC.’S MOTION Portland, Oregon 97204
FOR TEMPORARY RESTRAINING ORDER - 1 Telephone: (503) 954-2232
Facsimile: (503) 227-0880
1 that, somehow, its “entire confidential . . . cloud product roadmap” will be compromised if a
2 former employee is permitted to edit prewritten speeches and advise on how best to structure the
3 marketing organization.
4 Could that possibly be true? To ask the question is all but to answer it: Amazon has failed
5 to offer any evidence that, in working on those two narrowly-defined projects, Hall inevitably
6 will use or disclose any particular confidential information, or that he otherwise will threaten any
7 of Amazon’s legitimate business interests. Amazon is seeking, in other words, to co-opt the
8 Court into imposing a naked and unjustifiable restraint on competition by a former employee.
9 Amazon’s motion should be denied for that reason. Its motion also should be denied on
10 grounds that Amazon is equitably estopped from enforcing the noncompetition agreement on
11 which its claims are based, and has waived its right to do so.
12 LEGAL STANDARD
13 “The law is well settled that to obtain injunctive relief, a plaintiff must establish (1) he
14 has a clear legal or equitable right; (2) he has a well-grounded fear of immediate invasion of that
15 right by the entity against which he seeks the injunction; and (3) the acts about which he
16 complains are either resulting or will result in actual and substantial injury to him.” Nw. Gas
17 Ass’n v. Wash. Utilities & Transp. Comm’n, 141 Wn. App. 98, 115 (2007). “To establish a clear
18 legal or equitable right, the moving party must show that it is likely to prevail on the merits.” Id.
19 at 116 (quoting San Juan County v. No New Gas Tax, 160 Wn. 2d 141, 154 (2007)) (internal
20 quotation marks omitted). Courts disapprove of injunctions that would bar an employee from
21 practicing his or her chosen profession. See Cerro Fabricated Prod. LLC v. Solanick, 300 F.
22 Supp. 3d 632, 657–58 (M.D. Pa. 2018) (“[T]he public interest, including the risk of causing an
23 employee significant economic harm and preventing him from engaging in his chosen
24 profession, as well as preventing an employer from hiring the person of its choice, weigh against
25 any injunctive relief barring [an employee] from working for any period of time.”); PSC, Inc. v.
26 Reiss, 111 F. Supp. 2d 252, 253 (W.D.N.Y. 2000) (“Such a remedy—barring a person from
27
4 Hall began his prior role at Amazon on June 18, 2018. Ariel Kelman, AWS’s Vice
5 President for Worldwide Marketing, interviewed and hired Hall into the role. (Decl. of Brian
6 Hall (“Hall Decl.”) ¶ 4.)
7 At the start of Hall’s employment, Amazon required Hall to sign a Confidentiality,
8 Noncompetition, and Invention Assignment Agreement (the “Agreement.”) (Id. ¶ 5.) During
9 conversations with Kelman regarding the Agreement, he advised Hall that he believed the
10 Agreement’s noncompetition provisions were unenforceable. (Id. ¶ 6.) Kelman also told Hall that
11 he had never seen Amazon enforce these provisions against a marketing employee, even though
12 several such employees had previously departed for competitors. (Id.) Kelman gave these
13 statements to Hall both before and after Hall executed the Agreement. (Id.)
14 Hall decided in early January of 2020 that he would resign from Amazon. (Id. ¶ 8.) His
15 last day of substantive work at Amazon was February 13, 2020, and his employment formally
16 concluded at the end of March. (Id.) Hall later decided to join Google LLC in a senior marketing
17 role, and when he did so, he immediately and forthrightly informed Amazon of his plans. (Id. ¶
18 11.) In response, Amazon led Hall to believe — seemingly in confirmation of Kelman’s earlier
19 comments — that it had no objection to the new role. Paz Patel, the Amazon human resources
20 executive responsible for all of AWS’s thousands of marketing employees, “had a feeling that
21 [Hall] would land there” and told Hall that he was “[v]ery happy to hear this news.” (Id. ¶ 12.)
22 AWS CEO Andy Jassy echoed Patel’s comments in a subsequent email, telling Hall that he
23 “underst[ood] [his] perspective” on wanting to depart Amazon and “wish[ing] [him] nothing but
24 the best.” (Id. ¶ 13.) Nowhere in those communications did Amazon suggest that, in spite its
25 well-wishes, a lawsuit over Hall’s new role would soon follow. (Id. ¶¶ 12–13.)
26 Google hired Hall as a Vice President of Product Marketing, Google Cloud. Since joining
27 Google on May 4, 2020, Hall has been sidelined from virtually all substantive work due to
26 Based on those facts, Amazon’s motion should be denied for three independent reasons.
27 First, there is no risk that Hall’s organizational advice or speech-editing—through which he will
9 Amazon has presented zero evidence that Hall’s temporary roles will require him to use
10 or disclose any particular Amazon confidential information. In particular, Hall’s speech-editing
11 project will consist of two tasks: (1) “[r]eview[ing] final script[s] and slides to ensure
12 consistency,” and (2) “[p]repar[ing] weekly summar[ies] and blog post[s] of what was included
13 in each keynote.” (Wagonfeld Decl. ¶ 11; id. Ex. B.) By their terms, those tasks do not implicate
14 any Amazon confidential information because they concern content that Google already has
15 created: “[W]hat Google ‘says’ in keynotes and other sessions has already been determined by
16 those speakers, using narratives created by the product teams. These narratives already tell the
17 speakers (and [Hall]) what features to emphasize.” (Wagonfeld Decl. ¶ 13.) Even if it were up to
18 Hall to decide on areas of “emphasis” and “de-emphasis” in speeches that Google has
19 independently prepared and intends to make public, Amazon cannot as a matter of law have any
20 protectable interest in preventing him from doing so. See, e.g., Incyte Corp. v. Flexus
21 Biosciences, Inc., No. CVN15C09055MMJCCLD, 2018 WL 6428155, at *11 (Del. Super. Ct.
22 Aug. 23, 2018) (“No matter its value or source, [former employee’s] opinion
23 on public information is not an actionable trade secret.”).
24 B. Amazon’s claims are barred by the Doctrine of Equitable Estoppel.
25 Amazon’s request that Hall be barred from working in his two narrow, temporary roles
26 should be denied for a second, independent reason: Amazon’s claims are barred on the merits by
27 the doctrine of equitable estoppel. The Court need not fully and finally resolve that question
20 s/ Tyler P. Francis
Tyler P. Francis, WSBA No. 53533
21
s/ Edward A. Piper
22 Edward A. Piper, OSB No. 141609
(pro hac vice application pending)
23
Attorneys for Defendant Brian Hall
24
25
26
27
18
19
20
21
22
23
24
25
26
27
19
20
21
22
23
24
25
26
1 from virtually all substantive work because Amazon contends the role would violate the
2 noncompete agreement Brian signed. Google disputes these allegations, and the parties have
3 scheduled a preliminary injunction hearing for July 31, 2020.
4 4. In the interim, I began to consider how to keep Brian busy for the nearly three
5 months that will have passed between his start date and the preliminary injunction hearing.
6 Amazon was aware of this effort and, in fact, encouraged Google to offer temporary positions,
7 suggesting that putting Brian in a temporary role would alleviate some discovery and scheduling
8 challenges related to the preliminary injunction.
9 5. I devised two areas where Brian could be useful without any risk of using
10 Amazon’s allegedly confidential information: (1) helping Google Cloud optimize roles and
11 responsibilities in its marketing department and (2) editing keynote speeches for and
12 summarizing public comments made at Google Cloud’s ‘20 Next conference.
13 6. This year the Next conference is entirely online. Held over nine weeks, the
14 conference focuses on a different subject area each week. Viewers can watch videos of keynote
15 speeches from Google employees about that topic, attend breakout sessions and learn about
16 Google’s products. Although the conference is geared towards developers, customers and
17 potential customers, it is free and open to the public. Anyone may register to “attend”—even
18 Amazon employees.
19 7. For example, the first week of the Next conference revolves around “Industry
20 Insights.” It features Google Cloud executives discussing trends and challenges faced in retail,
21 healthcare, financial services and other industries. The second week revolves around
22 “Productivity and Collaboration,” and features speakers talking about how cloud computing
23 enables employees to work remotely more easily, among other related topics. And so on.
24 8. Attached as Exhibit A is a copy of a letter that Google’s counsel sent to Amazon.
25 It truly and accurately describes the duties and responsibilities that Brian would have in the
26 temporary role supporting the Next conference.
1 9. In essence, Brian’s role supporting the Next conference is limited to reviewing the
2 speeches that are written by the speakers themselves and editing them to ensure consistency and
3 avoid duplication across nine weeks. For example, if two speakers highlight how Google Cloud
4 helped a particular customer, Brian might suggest that one of the speakers use a different
5 customer example. Brian will also summarize comments made at the conference to prepare
6 emails and blog posts for attendees who missed them.
7 10. In short, Google wants attendees to feel they are receiving a consistent message,
8 and Brian will help ensure that each of the keynote speeches (and summaries of them) are using
9 one “voice” to the extent possible. Brian’s assignment is self-contained, and the materials that
10 Brian would use to perform these tasks are created by Google personnel about industry trends
11 and Google products. This temporary assignment for Brian was selected due to his experience at
12 Microsoft as a communications advisor for senior Microsoft executives, not due to his
13 knowledge of Amazon’s confidential information
14 11. In fact, nothing Brian would be doing related to the Next conference will involve
15 the use or disclosure of Amazon’s confidential information. Brian will be reviewing other
16 people’s materials that are already prepared. Attached as Exhibit B is a true and correct
17 timeline that shows the preparation of keynote materials for Next. I do not believe that Amazon’s
18 arguments to the contrary have merit.
19 12. Amazon claims that Brian would be able to reposition existing Google products
20 based on his knowledge of Amazon’s roadmap by, for example, accelerating the announcement
21 of Google products or altering Google’s pricing structures. These concerns are misguided. The
22 decisions regarding which products to announce at Next (if any) have already been made by
23 other people. Brian will have no input into product releases or pricing. He will have no input
24 into Google’s product roadmap at all.
25 13. Amazon also claims that Brian could preempt Amazon’s existing marketing plans
26 through anticipatory marketplace messaging (for example, by using his knowledge that “Amazon
1 is going to say X,” to determine that “Google should say Y”). But what Google “says” in
2 keynotes and other sessions has already been determined by those speakers, using narratives
3 created by the product teams. These narratives already tell the speakers (and Brian) what
4 features to emphasize. Brian will have no input into the product narratives and will not be
5 drafting any speeches from scratch. In fact, the Next conference was originally scheduled for
6 early April but postponed just three weeks before due to the COVID pandemic. Because the
7 conference was postponed so close to the start date, most keynote messages were prepared back
8 in March, two months before Brian’s arrival at Google
9 14. The job responsibilities related to the Next conference require neither any
10 competitive knowledge about Amazon nor even someone with Brian’s seniority. In past years
11 this responsibility was covered by someone three levels lower in the organization. But I would
12 like to assign this temporary assignment to Brian (which is far more limited than the permanent
13 job responsibilities of the Vice President, Product Marketing role) so that he has something to do
14 while the parties prepare for the preliminary injunction proceedings.
15 I declare under penalty of perjury under the laws of the State of Washington that the
16 forgoing is true and correct to the best of my knowledge and recollection.
17 EXECUTED this 8th day of June, 2020, in Sunnyvale, California.
18
19
_________________________________
20 ALISON WAGONFELD
21
22
23
24
25
26
EXHIBIT A
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
Kellen A. Hade
[email protected]
206.777.7411 direct line
BY EMAIL
Zana Bugaighis
Davis Wright Tremaine LLP
920 Fifth Avenue, Suite 3300
Seattle, WA 98104
Dear Zana:
As you know, Google continues to disagree with Amazon’s expansive view about
the scope of Brian Hall’s noncompete, especially when Brian will have no input into
Google’s product roadmap. We still hope that the parties can resolve that dispute without
ultimately needing court intervention. But if we can’t, and in response to Amazon’s re-
quest that Google consider other roles for Brian to accommodate an extended discovery
and briefing schedule, Google has identified two temporary and discrete assignments for
Brian: (1) consulting on the structure of its cloud marketing organization and (2) writing
communications, slides and scripts for the Google Cloud Next ‘20 Conference. These as-
signments are not alternatives; Brian will be doing both.
As important as what these assignments are is what they are not. Neither assign-
ment involves input into Google’s product roadmap. Neither involves collaboration with
product managers about product design. Neither involves development of Google’s go-
to-market strategy. And neither involves direct customer contact. Instead, as explained
below, both assignments rely exclusively on information derived from Google about
Google.
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
Zana Bugaighis
May 28, 2020
Page 2
Brian will review and consult on the Cloud Marketing team’s organizational design
to help Google reorganize its marketing efforts and improving its processes. In that way
he will act much like a third-party consultant.
Brian will review responses to the most recent “GoogleGeist,” an annual employee
satisfaction survey. The survey allows employees to comment on and rate broad organi-
zational topics like Google’s leadership, performance incentives and priorities. Brian will
consider these survey responses to identify where there are problems with Google Cloud’s
current marketing organization and processes, with an eye toward suggesting improve-
ment. By their nature, these survey responses are specific to Google’s people, culture and
environment.
Similarly, Brian will consider and suggest improvements to areas that marketing
leadership have identified as problems. Google believes Brian can add value here by
drawing from his experience at Microsoft, where he transitioned between many different
teams and products over two decades, affording him varied perspectives on what enter-
prise models or processes may work or may not.
• Work with the broader Google Marketing team to review the current
organizational structure focused on optimizing global, regional and
country roles.
Brian will also assist the broader Google Marketing team (supporting product ar-
eas across Google along with Cloud) in reorganizing its global, regional and country mar-
keting teams. As their names imply, these teams have different priorities and expertise
depending on their geography and product area focus. Brian will help define the specific
marketing-related roles and responsibilities for these teams.
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
Zana Bugaighis
May 28, 2020
Page 3
Ultimately, Brian will synthesize what he learns about Google from the employee
surveys and interviews with leadership into concrete recommendations for organizational
or structural improvements to the marketing team. Again, this work is like that of a third-
party consultant like McKinsey, and it does not involve Amazon’s allegedly confidential
information.
Google Cloud Next ‘20 Communications, Slide Creation & Script Creation
Brian will also assist Google Cloud with messaging at its Next ‘20 conference for
current and prospective customers, partners and developers. This year, Next has been
modified to a digital, on-demand format. Each week for nine weeks (July 14-September
8), viewers can access keynote addresses about different components of Google Cloud,
along with related breakout sessions. By its nature, Brian’s work on Next will be public-
facing and focused on communications about Cloud products, not positioning them
against Amazon ones.
Brian will harmonize the speeches for keynote and breakout presenters to ensure
consistent communications during the conference (“red threading”). Presenters write
their speeches from narratives created by the product teams. Brian will read each of these
speeches and weave common themes into each, based on those narratives provided to
him. For example, Brian will ensure that speakers do not repeat the same success stories
or highlight the same features. He will act essentially as an editor. And as a practical
matter, preparations for Next (originally planned for April) are too far along for Brian to
have much substantive input into its content anyway.
The materials Brian needs to perform this role are given to (not created by) him
and are self-contained. He will review Google’s narratives and speeches prepared by oth-
ers. His interactions with product marketers will be limited to recommending changes to
their presentation based on previous presentations at Next. His interactions with the sales
team will be limited to asking whether they believe particular messaging would resonate
with their customers. If Brian would use anything besides Google documents given to
him, it would be third-party research on market trends.
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
Zana Bugaighis
May 28, 2020
Page 4
The Leaders Circle and Partner Summit are breakout sessions for key custom-
ers. Speakers will be spinning off content from their broader Next presentations for these
sessions. As with the broader conference, Brian will be reviewing premade narratives
from different presenters to ensure consistency. Brian will not have direct contact with
any customer or partner who attends.
Brian will similarly ensure that Google has consistent, red threaded communica-
tions in its Next collateral, all of which is limited to the conference itself and public com-
ments made there.
Again, Brian’s deliverables in this role are all public facing: websites and content
summarizing comments about a particular Next topic into concise communications (blog
posts, emails, and so on).
Brian will start this limited work starting Monday, June 1, 2020. We hope Amazon
appreciates the significant concessions that Google is making in removing Brian from the
responsibilities of his intended role—which Google continues to believe is outside the
scope of any legitimate business interest Amazon may have—and engaging him in these
temporary assignments.
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
Zana Bugaighis
May 28, 2020
Page 5
Best regards,
Kellen A. Hade
4853-1241-7469.1
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
EXHIBIT B
DocuSign Envelope ID: D27FEE6C-1959-4157-9710-47F688BD4F1B
How the keynotes for Google Cloud Next 2020 OnAir are prepared:
SECOND DECLARATION OF ALISON WAGONFELD - 1 MILLER NASH GRAHAM & DUNN LLP
ATTORNEYS AT LAW
T: 206.624.8300 | F: 206.340.9599
PIER 70
2801 ALASKAN WAY, SUI T E 3 0 0
SEATTLE, WASHINGTON 98121
4811-3272-4415.1
DocuSign Envelope ID: 0D663337-A065-43C1-9C39-686117718977
22
23
24
25
26
SECOND DECLARATION OF ALISON WAGONFELD - 2 MILLER NASH GRAHAM & DUNN LLP
ATTORNEYS AT LAW
T: 206.624.8300 | F: 206.340.9599
PIER 70
2801 ALASKAN WAY, SUI T E 3 0 0
SEATTLE, WASHINGTON 98121
4811-3272-4415.1
The Honorable Sean O’Donnell
1
5
SUPERIOR COURT OF THE STATE OF WASHINGTON
6
IN AND FOR KING COUNTY
7
AMAZON.COM, INC., No. 20-2-08977-0 SEA
8
Plaintiff,
9 DECLARATION OF BRIAN HALL IN
v.
10 OPPOSITION TO PLAINTIFF
BRIAN HALL, AMAZON.COM, INC.’S MOTION
11 FOR TEMPORARY RESTRAINING
Defendant. ORDER
12
13
15 1. I am older than the age of 18 and otherwise competent to testify about the matters
18 way up over the course of over 20 years from a product manager to the Corporate Vice President
19 of Microsoft Devices.
20 3. I left Microsoft in 2017 to become the COO and then CEO of a technology
21 startup, and ultimately joined Amazon on June 18, 2018 as the Vice President of Product
23 4. Ariel Kelman, Vice President of Worldwide Marketing for AWS, interviewed me,
24 hired me into the role, and was my direct supervisor until his departure in January 2020 to
16 I want to tell you that it was a pleasure to work with you, and I
particularly appreciate learning about the Amazon culture from
17 you. I’m a big fan of AWS obviously and think you two are the
soul OF IT, and even more importantly, will keep evolving it
18 smartly. I’m out tomorrow and am not sure what I’ll do next, but
have interesting opportunities.
19 See you around town and I’m sure our paths will cross again. My
personal email is on cc.
20
Go AWS!
21
Brian
22
10. Jassy did not immediately respond, but Garman responded later that evening in an
23
email that stated as follows:
24
Thanks Brian - good luck in your next set up endeavors. I am
25 sorry we couldn’t find a great fit for you at Amazon - I am sure
you will kill it at your next role and I am sure we will work
26 together again soon - Seattle is a pretty small place
27 11. On April 10, 2018, I accepted an offer of employment from Google. That
20 I declare under penalty of perjury of the laws of the State of Washington and laws of the
21 United States that the foregoing is true and correct to the best of my knowledge and
22 understanding.
23 Executed at Seattle, Washington, this ____ day of June 2020.
24
By:
25
26 _____________________________
Brian Hall
27