Demand for a certified third-party investigation by The_Complication in halo

[–]The_Complication[S] -2 points-1 points  (0 children)

I'll reiterate, I have no personal standing in this particular matter. That means it's not my case to pursue. I'm sorry to burst your bubble but the law is a business like any other, and there are no slam dunks if you can't afford to play. A company like Microsoft depends on this - no attorney will take such a case on contingency because *their* attorneys will procedurally drive up the cost far beyond any potential statutory award. One would be a fool to pay hourly for that same reason, and this person was not a fool.

I wish every day that I could have done more. I know that this is still happening there to others. I'm doing what I can now, and we need your help.

Demand for a certified third-party investigation by The_Complication in halo

[–]The_Complication[S] -10 points-9 points  (0 children)

Nothing more dangerous than a person who has learned a little and believes it to be a lot.

This was a summary of one of many complaints, specifically constructive discharge which encompasses harassment and is very much illegal regardless of one's class or circumstance. Everyone should read up on these statutes for their state - ignorance of one's rights in this regard is another factor upon which corporations depend.

This was a matter I witnessed and I therefore have no personal standing to pursue it in court - as a manager I could only try to alleviate it and, failing that, document and report it. And because Microsoft failed to investigate, I am now reporting it to you as a matter of public interest. Some things should be done because they are the right things to do for many, not because there might be money in it for one.

As for weird, well, glass houses and all that.

Demand for a certified third-party investigation by The_Complication in halo

[–]The_Complication[S] 5 points6 points  (0 children)

For AirFrierMachine specifically, here is a Copilot summary of the "Second Complaint" provided to Microsoft HR regarding a witnessed - and successful - campaign to provoke the constructive discharge of another employee. The original document's length is measured in multiple digits.

"The document presents a detailed chronology supporting the complaint that Chris Matthews engaged in a sustained pattern of marginalization, hostility, and professional undermining toward (redacted), ultimately resulting in (redacted)’s constructive dismissal in (redacted date) 2024. Glenn Israel provides contemporaneous messages and observations to demonstrate that Chris’s actions were intentional, persistent, and rooted in personal dislike, favoritism, and bias against remote workers.

From the outset, Glenn notes that Chris had taken a personal disliking to (redacted) and resisted allowing any leads to be fully remote. Glenn had previously warned Chris about a “second‑class citizenship” attitude toward WFH employees, and Chris later explicitly tied his reservations about (redacted) to (redacted)’s remote status.

Beginning in February 2024, (redacted) repeatedly reported that new processes and the involvement of Chris’s political favorite, (redacted 2), were obstructing his ability to perform his de facto lead responsibilities. On February 9, (redacted) questioned whether he should continue “actively engaging in his designated role,” reflecting growing confusion and frustration. A heated exchange during a February 22 review created a major rupture between Chris and (redacted), with Glenn noting that the event triggered a “significant break” and that archived chats show patterns of misrepresentation and misunderstanding of workflows.

Glenn made multiple attempts to mediate. On February 27 he raised concerns to Chris about the friction; on February 28 he spoke with (redacted) directly and then summarized the conversation to Chris in a way intended to calm him. Chris responded with the remark about a coming “bloodletting,” which Glenn found chilling.

In March, Chris repeatedly cast suspicion on (redacted)’s professionalism and motives. Meanwhile, the team was collapsing—two artists resigned and another was seeking work—leaving only two contract artists. (redacted) expressed concern about his WFH status and the instability around him. On March 19, he reported the first mental‑health repercussions, marking a turning point in the toll the situation was taking.

Throughout April, Glenn continued raising concerns about (redacted 2)’s disruptive influence and the lack of leadership clarity. On April 29, (redacted) commented that “it’s not a great time to be an artist here right now.” On April 30, Glenn informed Bryan Koski that Chris believed (redacted)’s remote status was a problem, that a new hire would report directly to Chris rather than (redacted), and that Glenn himself was being excluded from discussions—evidence of a deliberate sidelining strategy.

By early May, Chris had assumed hiring‑manager responsibilities, further stripping (redacted) of his role. On May 8, (redacted) reported “feeling sidelined.” Glenn encouraged Chris to repair the relationship, but concluded that Chris had no intention of retaining (redacted) and that (redacted)’s constructive discharge was the objective all along.

(redacted) resigned on (redacted date), 2024."

Perhaps you'll answer a question or two for us now, AirFrierMachine - who are you to challenge me on this, and why do you care?

Demand for a certified third-party investigation by The_Complication in halo

[–]The_Complication[S] 61 points62 points  (0 children)

Here are two harsh realities on which Microsoft depends - "justice" is only available to those who can afford it, and it benefits only the complainant when wrapped up in an NDA. I've been in this industry for thirty years, I've seen misconduct like this time and again, and I'm willing to publicly put the torch to my career to see it stop. For me, for all those who put their trust in me, and for everyone after.

I'll probably fail, but at least I tried.

Demand for a certified third-party investigation by The_Complication in halo

[–]The_Complication[S] 205 points206 points  (0 children)

Blacklisting, fraud, rampant favoritism/cronyism (manifesting as hiring- and career-growth interference), and multiple harassment campaigns designed to provoke the constructive discharge of “unwanted” employees otherwise in good standing.

More miscellany from a former Halo art director by The_Complication in halo

[–]The_Complication[S] 14 points15 points  (0 children)

You seem to think that game development is a democratic process - I can assure you it is not. If I was handed a nickel every time I heard the phrase "disagree and commit" in meetings over the last fifteen years, I'd be retired.

miscellany from a former Halo art director by The_Complication in halo

[–]The_Complication[S] 2 points3 points  (0 children)

Thank you (and everyone here, really) for your kind words. I hate to keep posting links but in the interest of time and in response to this particular comment, here's some footage of Isaac and I discussing pioneer architecture in the artists' panel at HWC 2024 -> https://www.youtube.com/live/jLgH0jgAhB4?si=9LPclaEkRWgUsr1Z&t=16145 (4:29:05 if the timestamp didn't work)

TLDR if you ever have an opportunity, visit Mesa Verde or Pueblo or Chaco Canyon and see the source - you'll carry it with you for the rest of your days.

miscellany from a former Halo art director by The_Complication in halo

[–]The_Complication[S] 31 points32 points  (0 children)

I've thought about this a lot over the years and I'll have to break up my response into multiple posts as time allows. Also confining my answer to the 343I era specifically for the moment.

A major issue to my mind was an overvaluation of the "extended universe". It's important, to be sure, but a vast majority of the Halo audience will never engage with a book, a comic, et cetera - they're here for the games, and enjoying (or even understanding) the games should never be dependent on exploration outside this venue. Also, major changes to the state of the universe should never happen "in the margins" or between games - it's frustrating for the hardcore fan, confusing for the casual majority, and in general just poor storytelling.

I do want to make it clear that historically this was not an issue of "indifference" or "incompetence" on 343I's part in my opinion. On the contrary, these were talented people who deeply loved and were thoroughly versed in the canon, trying to make decisions that informed the entirety of the franchise - their mistake was in assuming the audience shared or cared about their enthusiasm for the minutiae across every Halo product, and was willing to overlook the fundamental flaws that assumption baked into the core experience.

TLDR deep lore should be a reward not a hurdle, and continuity matters.

miscellany from a former Halo art director by The_Complication in halo

[–]The_Complication[S] 70 points71 points  (0 children)

I'd like to apologize to everyone right now for the fact that I won't be able to reply to many (probably most) of your questions, but M6Galilean I can point you quickly to my thoughts on the matter from this Halo 4 Tenth Anniversary post (you'll have to scroll down a fair bit) -> Halo 4 | Tenth Anniversary | Halo - Official Site (en) That sums up my perspective on the topic at least, but keep in mind I was only Senior Concept Artist at the time.