EA Bootcamp

Workplace Complaint

  • Adobe EA pre-sales bootcamp, role transition, and August 10 feedback meeting*

This document presents concerns for Adobe to review and investigate. It does not ask Adobe to assume discrimination, retaliation, or any policy violation. It preserves favorable and unfavorable evidence and distinguishes direct evidence from witness perception and inference.

Executive Summary

The core concern is not simply that negative bootcamp feedback was given. The concern is that the bootcamp was introduced in writing and at kickoff as a five-day instructor-led enablement program intended to provide EAs with skills, round out differing backgrounds, and create a common baseline, but later became the basis for immediate short-term work restrictions and a much stronger characterization: 'the boot camp is the job' and 'if you've checked out of the boot camp, you've checked out of the job.'

The record contains unfavorable evidence that should remain in the complaint: management said the technical exam score was the lowest Jay had seen in the bootcamp, criticized the presentation as AI-driven, inaccurate, and insufficiently polished, and said peers completed the same assignment using the same instructions. The record also contains favorable and mitigating evidence: the invitation framed the bootcamp as skills enablement; the kickoff described the first four days as grounding participants in skills before applying them on day five; a leader acknowledged valid points about compressed timing; and Ish's discovery score was explicitly stated as five out of five.

The requested review is a neutral investigation into process, communication, calibration, and proportionality: whether expectations and employment consequences were adequately communicated in advance; whether the evaluation was applied consistently; whether witness concerns about training resources and leadership style were considered; and whether any role restriction should be corrected, narrowed, or tied to objective written criteria.

Background

Ish joined during a prolonged team transition. In the July 21 transcript, the transition was described as a difficult and unusual timing issue, with uncertainty about whether SAs would remain under EA or what would happen. Against that backdrop, Ish received a bootcamp invitation for an instructor-led, multi-day EA bootcamp. The invitation did not characterize the bootcamp as a job trial, performance improvement process, or condition of maintaining the full EA role. It described the program as designed to provide an EA with skills for complex client engagements and asked participants to identify customer-meeting conflicts.

Chronological Timeline

  • July 21, 2026 - Team transition context* Type: Direct transcript Manager/colleague described the transition as a difficult timing issue: 'it is ridiculous that you joined this team' during a prolonged organizational change, and said there had been uncertainty about whether SAs would continue under EA or what would happen. Source: Team Transition and Operational Update, 5:53-6:38

  • Pre-bootcamp - Notice and stated purpose* Type: Direct invitation The invitation described an instructor-led, five-day bootcamp designed to provide an EA with skills to support complex client engagements using technical architecture for non-technical digital marketing objectives. It asked participants to block calendars and identify customer meetings or engagements that conflicted with the five-day bootcamp. Source: Bootcamp invitation

  • July 27, 2026, 12:38 PM - Bootcamp framed as enablement and baseline-setting* Type: Direct transcript At the opening, Jay stated that the bootcamp was meant to marry technical skills with real-world business challenges, round out AEP-related skills, and give everyone a baseline. The first four days were described as grounding participants in technical skills, leading into day five. Source: EA Pre-Sales Boot Camp Agenda Overview, 1:17-5:33

  • July 27, 2026, 12:38 PM - Final exercise and exam disclosed* Type: Direct transcript The bootcamp included a day-five mock customer presentation and a technical exam. The presentation was described as using skills from the first four days to present an architecture and point of view for a mock customer with a real-world challenge. Source: EA Pre-Sales Boot Camp Agenda Overview, 4:19-5:24

  • July 27, 2026, 5:17 PM - Hands-on training context* Type: Direct transcript Jay stated the bootcamp was not an implementation class and that EAs' jobs are not implementation. He also described bootcamp examples as ways to reduce starting from zero and learn best practices. Source: AEP Architecture and Core Components, 14:08-14:54

  • July 28, 2026 - Calendar conflicts and time expectations* Type: Direct transcript Participants discussed conflicts with customer or internal meetings. Jay asked that meetings be scheduled before 10, after 6, or during lunch, and offered to back up participants dealing with internal conflicts. Source: Meeting Notes: Day 2, 1:29-3:31

  • July 31, 2026 - Sales lifecycle and final presentation* Type: Direct transcript On day five, the agenda included discovery, use-case validation, architecture, storytelling, and a final customer presentation. Jay stated participants would be given a customer and asked to provide a point of view because 'this is a sales job.' Source: Sales Lifecycle & EA Tools Overview, 0:03-1:53

  • July 31, 2026 - Presentation polish expectation* Type: Direct transcript Jay emphasized that customer-facing outputs should be polished and professional, including use of PowerPoint where appropriate. Source: Sales Lifecycle & EA Tools Overview, 147:45-148:34

  • August 3, 2026, 2:12 PM - Leadership/communication concerns before August 10 decision* Type: Witness perception A colleague/manager said he also got certain 'vibes' from Jay, said he did not think the issue was unique to Ish, and described it as a broader pattern across demographics. The same discussion questioned whether extra resources or office hours were being provided and criticized not sharing slides if the goal was education. Source: EA Team Leadership and Communication Challenges, 4:42-6:46; 10:42-12:34

  • August 3, 2026, 5:15 PM - Contemporaneous support for ideas/value* Type: Witness perception A later discussion reflected that peers may see value in Ish's contributions or ideas even when they do not receive sponsorship. This is supportive context, not proof of improper motive. Source: Personal & Professional Feedback Discussion, 27:00-28:04

  • August 10, 2026 - Feedback meeting opened as bootcamp feedback and role impact* Type: Direct transcript Jay said he wanted to discuss what was seen from a bootcamp perspective and what it meant going forward, at least in the short term, for Ish's EA role on the team. Source: Ish | Jay | Gibby - Bootcamp Feedback, 2:17-2:35

  • August 10, 2026 - Favorable evidence preserved* Type: Direct transcript Jay praised Ish's confidence and eagerness to use AI, and said AI use had been excellent before the bootcamp in Slack/channel interactions. Source: Ish | Jay | Gibby - Bootcamp Feedback, 2:35-3:05

  • August 10, 2026 - Unfavorable evidence preserved* Type: Direct transcript Jay said Ish was first to finish the exam but had the lowest score ever seen in the bootcamp, and that the presentation appeared primarily, if not 100 percent, AI-driven, inaccurate, and lacking brand polish/professionalism. Source: Ish | Jay | Gibby - Bootcamp Feedback, 3:35-5:10

  • August 10, 2026 - Management view that mock exercise was equivalent to real customer presentation* Type: Direct transcript Jay stated there may have been a disconnect because the fictitious customer did not exist, but 'this was a real customer presentation' for leaders to evaluate approach and deliverable. Source: Ish | Jay | Gibby - Bootcamp Feedback, 5:13-5:44

  • August 10, 2026 - Compressed time and bathroom break issue* Type: Mixed direct evidence Gibby/Matt acknowledged valid points about compressed time and a fast timeline. A bathroom-break exchange was discussed, with Jay clarifying that he initially said no, then corrected himself and said a break was allowed. Source: Ish | Jay | Gibby - Bootcamp Feedback, 13:13-14:06

  • August 10, 2026 - Five-out-of-five discovery score* Type: Direct transcript Jay stated Ish's discovery performance was a five out of five, and clarified that this was a five-point scale. He then said presentation and solution accuracy were the areas of struggle. Source: Ish | Jay | Gibby - Bootcamp Feedback, 20:17-21:21

  • August 10, 2026 - Management explanation of assignment concerns* Type: Direct transcript Jay said the assignment was not to create from scratch in 45 minutes, but to use the customer ask, provided documentation, template, and architecture materials. He also said peers solved it with the same instructions. Source: Ish | Jay | Gibby - Bootcamp Feedback, 22:35-24:41

  • August 10, 2026 - Key characterization change* Type: Direct transcript / management inference Jay stated: 'the boot camp is the job' and 'if you've checked out of the boot camp, you've checked out of the job.' This statement appears inconsistent with the earlier framing of the bootcamp as skills enablement and baseline-setting. Source: Ish | Jay | Gibby - Bootcamp Feedback, 27:25-27:36

  • August 10, 2026 - Short-term role restriction* Type: Direct transcript Jay said Ish would focus on the SA component of the job while management formulated a plan to build confidence. He later clarified Ish was in the 'O role' because Jay perceived risk in putting Ish in front of customers and internal stakeholders. Source: Ish | Jay | Gibby - Bootcamp Feedback, 28:01-29:26

  • August 10, 2026 - Severity of employment consequence* Type: Direct transcript / management inference Jay said the conversation was not a tryout and that Ish was already an employee. He also said that if he thought Ish could not do the job, he would 'simply release' him. Source: Ish | Jay | Gibby

  • Bootcamp Feedback, 30:49-31:07; 34:00-34:09

Issue and Pattern Analysis

1. Change in bootcamp characterization

Direct evidence supports a concern that the bootcamp's meaning changed over time. The invitation and kickoff framed it as instructor-led skills enablement. The August 10 meeting framed it as a proxy for the job itself. The question for investigation is whether participants had fair notice that a compressed training exercise would be used to restrict core EA responsibilities or assess job engagement.

2. Evaluation process and instruction clarity

The record cuts both ways. Management stated that everyone had the same compressed time, same exam, same assignment, and same instructions, and that peers completed the task. Ish's concern is that the bootcamp was also described as training designed to ground and enable participants, that time was compressed, that the mock assignment became treated as a real customer presentation, and that witness comments before August 10 raised questions about resources, office hours, slide sharing, and leadership style. This supports a process-review concern, not a conclusion that the score was invalid.

3. Proportionality of immediate role impact

The August 10 meeting connected bootcamp performance to short-term role restriction: Ish would focus on the SA component, was described as being in the 'O role,' and was not to be put in front of customers/internal stakeholders because Jay perceived risk. The question for investigation is whether that restriction was proportionate, objectively documented, and based on criteria communicated before the bootcamp.

4. Direct evidence versus witness perception

The August 3 witness statements are useful but must be treated carefully. They do not prove discrimination, retaliation, or improper motive. They do show contemporaneous perception before the August 10 employment-impact meeting: one person perceived Ish as being challenged harder or on the radar, while another said concerns about Jay's style were not unique to Ish and appeared broader across demographics. That distinction weakens any unsupported protected-class claim but strengthens the request for a neutral process review.

5. Favorable and unfavorable facts to preserve

Favorable evidence includes the initial enablement framing, 5/5 discovery score, positive comments about confidence and AI use, and acknowledgment that time was compressed. Unfavorable evidence includes the low exam score, criticism of presentation quality and solution accuracy, management's view that peers completed the same assignment, and management's concern that Ish did not ask clarifying questions when confused. A credible complaint should include both.

Adobe Policy and Guidance Considerations

Code of Business Conduct

The Code supports filing a good-faith concern and says reports should be made to someone neutral and not directly involved. It also says managers must immediately report potential violations they witness or complaints they receive, and that Adobe will investigate reported concerns and take corrective action as needed. Relevant workplace principles include dignity, fairness, respectful treatment, and open/honest communication. This complaint asks Adobe to apply those processes; it does not assert a Code violation as a conclusion.

Non-Retaliation Policy

The Non-Retaliation Policy protects good-faith reporting and participation in investigations. Based on the current record, the strongest use of this policy is prospective: this complaint itself is protected good-faith reporting, and Ish asks Adobe to ensure there is no retaliation for filing it or participating truthfully. To the extent any August 10 role restriction followed earlier good-faith concerns about the bootcamp, that timing can be reviewed, but the current record does not independently prove retaliatory motive.

Equal Employment Opportunity Policy

The EEO Policy applies to employment decisions and protected classifications. The available transcripts do not establish that any action was because of race, color, religion, gender, gender identity/expression, marital status, age, disability, veteran status, sexual orientation, national origin, citizenship, or another protected classification. This document therefore does not assert discrimination. It asks only that Adobe preserve EEO review if HR identifies protected-class facts not currently in the record.

Investigation and Reporting Guidance

Adobe's reporting guidance identifies the hotline, Compliance Office, ERC, and managers as reporting channels; states that managers must report concerns once informed; and says reports are reviewed by neutral experienced professionals. The Investigation FAQs explain that neutral trained investigators gather documents and witness names, maintain confidentiality to the extent possible, and require truthful cooperation. This complaint is structured to support that process.

Requested Review and Remedies

  • Assign a neutral trained reviewer or investigator not directly involved in the bootcamp evaluation or August 10 role restriction. - Preserve Ish's title, pay, reporting status, and opportunities while the review is pending, and confirm in writing that no retaliation will occur for filing this complaint or participating truthfully. - Review the bootcamp invitation, prerequisites, agenda, scoring rubric, exam, presentation instructions, templates, architecture files, slides/resources, and any written follow-up from August 10. - Determine whether participants were told in advance that the bootcamp would be treated as equivalent to the job or could result in short-term restriction from customer/internal-stakeholder work. - Review whether the 'checked out of the boot camp / checked out of the job' characterization is supported by objective facts or should be removed, narrowed, or corrected in any employment record. - Interview witnesses and bootcamp participants about instruction clarity, time constraints, slide/resource access, office hours, evaluation consistency, and whether expectations were understood the same way by all participants.

  • If a temporary ramp plan remains appropriate, provide objective written criteria, milestones, support resources, expected duration, and a clear path back to full EA pre-sales responsibilities.

  • Consider restoring customer-facing or internal-stakeholder opportunities where the only barrier is an unreviewed inference from a compressed bootcamp exercise.

  • Provide a written outcome or summary sufficient for Ish to understand what facts were reviewed and what corrective steps, if any, Adobe will take.

Evidence Index

  • E1 - Bootcamp invitation (Direct written evidence): Initial program description: instructor-led, multi-day, skills-oriented, five-day program; requested calendar conflicts.
  • E2 - July 21 transition transcript (Direct transcript): Organizational transition context and uncertainty around role/team placement.
  • E3 - July 27 agenda transcript (Direct transcript): Bootcamp purpose, baseline/round-out language, mock customer presentation, technical exam.
  • E4 - July 27 AEP transcript (Direct transcript): Hands-on training context; not an implementation class; jobs are not implementation.
  • E5 - July 28 transcript (Direct transcript): Calendar conflict handling and expectation that participants be out of field during bootcamp hours.
  • E6 - July 29 transcript (Direct transcript): Technical training content. Reviewed for chronology; no central complaint quote relied upon.
  • E7 - July 31 transcript (Direct transcript): Day-five sales lifecycle, discovery, use cases, customer presentation, polish expectation.
  • E8 - August 3 leadership transcript (Witness perception): Perception that issues with Jay's style were not unique to Ish; questions about resources/slides.
  • E9 - August 3 personal/professional transcript (Witness perception): Peer-value/support context. Useful as context, not proof of motive.
  • E10 - August 10 feedback transcript (Direct transcript): Performance critique, 5/5 discovery score, presentation and solution accuracy critique, 'boot camp is the job,' role restriction/risk statements.
  • P1 - Code of Business Conduct (Policy): Reporting concerns, neutrality, no retaliation, cooperation, dignity/fairness, prompt investigations.
  • P2 - Non-Retaliation Policy (Policy): Good-faith reporting and participation protections; reporting channels; corrective action if improper retaliation found.
  • P3 - EEO Policy (Policy): Protected-class employment decision standards and reporting process. Current record does not establish protected-class discrimination.
  • G1 Report Integrity Concerns (Guidance): Reports can go to hotline, Compliance, ERC, or manager; managers must report concerns; neutral professionals review reports.
  • G2 - Investigation FAQs (Guidance): Neutral trained investigators; good-faith concerns should be reported; confidentiality limits; witnesses and documents should be gathered.

Witness List

  • Jay Jackson - Director; bootcamp leader/evaluator. Relevant topics: Bootcamp purpose, instructions, scoring, August 10 statements, role restriction rationale.
  • Matt Gibby - Manager or leader present in August 10 feedback meeting. Relevant topics: Acknowledged compressed time; participated in discussion of role impact and feedback.
  • Michael McGarry - Named speaker in August 3 transcript. Relevant topics: Perception that Ish was being challenged harder and/or on the radar.
  • David Ensign - Named speaker in August 3 transcript. Relevant topics: Contemporaneous responses to concerns; can clarify what was observed directly versus inferred.
  • David Baker - Bootcamp articipant referenced in July 28 transcript. Relevant topics: Calendar conflict handling and bootcamp scheduling expectations.
  • Other bootcamp participants - Peers in same bootcamp. Relevant topics: Whether instructions, resources, slides, timing, evaluation expectations, and job consequences were understood consistently.
  • Managers invited to observe final presentations - Potential observers/evaluators. Relevant topics: Rubric, score basis, whether evaluation was calibrated and communicated.

Source Integrity Notes

The local folder contains nine distinct individual transcript files plus a combined transcript file that repeats those same nine transcript headings. The prior conversation referenced ten uploaded transcripts, so if a separate tenth transcript exists it should be added before filing or noted as unavailable. The transcripts also contain repeated filler text such as 'Thank you' from the transcription tool; this document does not rely on those filler segments. Three Non-Retaliation Policy PDFs are duplicate files by hash; this document treats them as one policy source. The HRA Guide to Services report appears to be an accessibility/tagging report rather than Adobe workplace policy guidance and is not relied on for the policy analysis.

Transcripts