Removing a difficult manager is rarely as straightforward as filing a complaint with senior leadership, according to former Amazon vice president Ethan Evans, who says employees often underestimate the institutional resistance that protects poor leadership.

In remarks on The Peterman Pod, Evans offered a blunt assessment of how workplace complaints are typically received at the top: senior managers may have strong incentives, even if subconscious, to discount concerns raised about one of their direct reports.

“If you come to me with a weakness in one of my employees,” Evans said, the instinctive calculation is whether to dismiss the complaint as oversensitivity or accept it and trigger a much larger operational problem.

That problem, he explained, can quickly escalate into a leadership crisis. If the complaint is deemed credible, the senior executive may need to manage the person out, oversee a replacement process, and absorb the disruption that follows, often while carrying the additional workload themselves.

“So you can see why, even if it’s subconscious, I have a lot of reasons not to listen or not to believe very easily,” he said.

His comments offer a rare insider look into the political mechanics of workplace hierarchy, where the process of addressing bad management often collides with incentives around continuity, optics, and workload.

At its core, Evans’ argument is less about whether complaints are justified and more about how organizations process risk.

For skip-level managers, acknowledging that a subordinate manager is failing does not merely validate an employee’s grievance. It can also raise uncomfortable questions about their own judgment in hiring, promoting, or supervising that person. In many organizations, this creates an institutional bias toward delay, denial, or minimization.

This is why, Evans argues, lone complaints frequently go nowhere. His advice is deliberately collective: “Never mutiny alone.”

Rather than escalating concerns in isolation, employees should first compare experiences with trusted colleagues to determine whether the issue is systemic or simply a mismatch in management style.

That “sanity check,” as he describes it, serves two purposes. First, it helps separate subjective frustration from an objectively harmful pattern. Second, it transforms a personal grievance into a team-level operational concern, which senior leadership is far more likely to take seriously.

When multiple employees raise the same issue, the complaint ceases to look like a personality clash and starts to resemble a leadership failure. Evans said that in one case involving a problematic leader, he would likely not have acted on a single complaint. But once several consistent reports surfaced, it became clear that intervention was necessary.

In a follow-up email to Business Insider, he expanded on that point, stressing that documentation is often the difference between being heard and being dismissed. The most effective approach, he said, is to present at least three clear, fact-based examples, ideally corroborated by others, and frame the issue in terms of business impact rather than personal emotion.

One of the most common mistakes employees make, according to Evans, is allowing frustration to dominate the complaint. Bitter or emotionally charged grievances can be easily reframed by leadership as interpersonal conflict or hypersensitivity.

A more effective strategy is to acknowledge what the manager does well before outlining specific shortcomings and their consequences for team performance, morale, retention, or delivery.

This approach shifts the conversation from accusation to risk management. Senior leaders are far more likely to intervene when they believe the manager’s behavior is creating measurable organizational harm, particularly if top talent is leaving or if the conduct introduces legal, ethical, or compliance risks.

Absent those factors, complaints often remain easy to ignore.

Play Chess Not Checkers

Evans also outlined an alternative route for employees who may not want to confront leadership directly: reposition the issue as a business case for internal mobility. Rather than criticizing the manager, he suggests making a case for moving to another team by emphasizing where one’s skills can better serve the organization.

“Don’t even bring up the manager,” he said. “Just say, ‘hey, I was looking at this other role, and I think I could do so much more for you and the org over here because of A, B, and C.'”

Ultimately, Evans admitted navigating these situations requires careful strategy: “You’ve gotta play chess, not checkers.”

This is, in effect, corporate diplomacy.

It allows employees to exit a damaging reporting line without forcing leadership into a defensive posture. In many companies, this route may be more practical than seeking to have a manager removed, especially where power structures are entrenched.

Evans’ remarks also tap into a broader management problem that extends well beyond any one company.

Across corporate America and the wider global workplace, ineffective managers are often the by-product of flawed promotion systems. High-performing individual contributors are frequently elevated into leadership roles without the training, emotional intelligence, or coaching skills required to manage people effectively.

This structural issue has been widely documented by management experts and labor economists, who argue that technical excellence does not automatically translate into leadership competence. As organizations continue to flatten hierarchies and expand spans of control, many managers now oversee larger teams with fewer resources, intensifying the pressure and often exposing weaknesses in communication and people management.

Evans draws an important distinction between bad managers and underdeveloped ones. Some, he says, are simply untrained and can improve with coaching and support. The more troubling category consists of leaders who view questioning as insubordination and default to rigid top-down authority, especially under stress. These are often the cases where escalation proves most difficult, particularly if higher-level leaders share the same blind spots.

Evans describes this as “stacked flaws” — situations where the leadership chain reinforces the same dysfunctional management style, making recognition and correction unlikely. In such environments, he argues, employees may need to make a harder calculation.

If colleagues are unwilling to corroborate concerns and the culture discourages dissent, the most strategic move may not be escalation at all, but exit. Sometimes, he suggests, the problem is not just the manager but the organization’s culture itself.

In that sense, his advice is ultimately less about office politics and more about institutional reality: changing a bad boss requires evidence, allies, and timing. Without those, the smarter play may be to protect one’s career by moving on.

Anchor, a global banking and payments infrastructure platform, has announced the acquisition of key regulatory licences in Nigeria and Canada, marking a significant milestone in its expansion strategy.

The company has secured a Microfinance Bank (MFB) licence and an International Money Transfer Operator (IMTO) licence in Nigeria. In addition, Anchor obtained a Money Services Business (MSB) registration in Canada.

These approvals strengthen the company’s compliance framework and enable it to offer more robust embedded financial services across borders.

Speaking on the development, Segun Adeyemi, CEO and Co-founder of Anchor, highlighted the importance of these licences in building reliable infrastructure for the next wave of fintech innovation. “These regulatory milestones reinforce our commitment to providing compliant, scalable infrastructure that powers businesses to build and scale financial products efficiently,” Adeyemi noted.

As Nigeria’s fintech industry continues to mature, infrastructure providers like Anchor are becoming increasingly important. Founded in 2021 and publicly launched in 2022, the company has quickly established itself as a key player in the embedded finance space.

Anchor represents a critical layer in the fintech value chain. While companies like payment processors focus on transactions, Anchor goes further by enabling businesses to build entire financial ecosystems within their platforms.

The platform provides API-driven tools for embedded accounts, payments, cards, and other financial products, allowing businesses to integrate banking features seamlessly into their applications.

Since its inception, Anchor has processed over $2.5 billion in transactions while onboarding more than 1,000 businesses across 18 countries spanning Africa, the Americas, and Europe.

Over 300 businesses now run on Anchor from startups like Bujeti, Kredete, Ramply, Cedar Money, Timon Financials, Kobotrade, Curacel, Trove, and Accrue, to established enterprises such as MoMo, the fintech arm of MTN.

Anchor’s growth comes at a time when African fintech companies are facing increased regulatory scrutiny and consolidation. By securing these licences, the company positions itself as a trusted infrastructure partner capable of supporting cross-border payments, local account services, and international money transfers.

The MFB licence in Nigeria will allow Anchor to offer deposit-taking and other microfinance services directly, while the IMTO licence enhances its ability to facilitate international remittances. The Canadian MSB registration further extends its reach into North America, creating smoother corridors for businesses operating between Africa and global markets.

With its API-first approach, Anchor has become a go-to platform for startups and enterprises looking to launch banking and payment solutions rapidly without building complex infrastructure from scratch.

Anchor’s infrastructure is fueling a new wave of financial innovation across Africa. Remittance companies like Veloremit and Quick Remit are making it possible for families to send and receive money safely, quickly, and at a lower cost. Expense management platforms such as Bujeti are giving SMEs smarter tools to manage spending and grow with confidence.

By lowering the barriers to entry, the company is helping to democratize access to financial services infrastructure, empowering startups and enterprises alike to innovate and scale. In a region where financial inclusion remains a major challenge, such infrastructure plays a vital role in extending services to underserved populations.

The latest regulatory wins build on Anchor’s strong momentum, following its third anniversary celebration in 2025, where it first highlighted crossing the $2.5 billion transaction milestone.

Less than a year after Anthropic publicly cast China as an “adversarial nation” and moved to restrict access to its artificial intelligence tools, the US start-up has found itself facing an uncomfortable irony: its own proprietary code is now being dissected by the very developer community it sought to keep out.

What began as a packaging error has quickly evolved into one of the most closely watched AI industry incidents of the year, exposing not customer data or model weights, but something nearly as valuable in the current race for dominance: the engineering blueprint behind one of the world’s most advanced coding assistants.

According to multiple reports, Anthropic inadvertently released a software package for Claude Code that contained a large internal JavaScript source map, enabling the reconstruction of roughly 512,000 lines of TypeScript code spread across nearly 2,000 files. The file, intended for internal debugging, was included in a public npm release in what the company later described as a “human error” rather than a cyber breach.

The scale of the leak immediately caught the attention of the global developer community. But nowhere was the reaction more intense than in China, where Claude remains officially unavailable.

According to SCMP, Chinese developers, many of whom already access Anthropic’s services through virtual private networks, quickly moved to download mirrored copies and began a line-by-line examination of the exposed codebase. On Chinese social platforms, discussions around what some described as the “Claude Code source code leak incident” surged, with developers sharing breakdowns of the tool’s architecture, agent framework, and memory systems.

Even though Anthropic, like OpenAI and Google, restricts access to mainland China on national security grounds, Chinese engineers have remained deeply interested in frontier US AI models, particularly coding assistants that promise to automate software development workflows.

The leak has, in effect, handed them a rare technical window into the orchestration layer that transforms a large language model into a usable developer product.

Industry analysts note that while the incident did not expose the underlying model weights, which remain the crown jewels of any closed-source AI company, the operational logic and product design choices revealed by the code may still prove highly valuable.

As Beijing-based systems architect Zhang Ruiwang observed, the leaked code batches are a “treasure” because they reveal key engineering decisions behind the product.

“But the code batches are indeed a treasure for AI companies or developers, as they revealed all the key engineering decisions Anthropic made,” Ruiwang said.

Model weights determine the intelligence of the system. But the orchestration layer, memory mechanisms, tool permissions, session handling, and prompt routing define how that intelligence is deployed in real-world workflows. In practical terms, this is where much of the user experience advantage lies.

Early examinations by developers suggest the code exposes sophisticated systems for long-context memory management, agent coordination, and autonomous workflow repair. Several reports point to a “self-healing memory” architecture that helps Claude Code manage context drift during long-running development sessions.

For Chinese developers and rival AI labs, this is precisely the kind of information that can accelerate internal product development. The timing also adds to the strategic embarrassment for Anthropic. The company has built much of its reputation around AI safety, security, and operational discipline. Yet this marks the second damaging information exposure linked to the company in recent weeks, intensifying scrutiny over its internal controls.

Anthropic pulled the problematic release and issued takedown notices to code-hosting platforms, including GitHub. But as often happens with internet leaks, containment proved difficult once the material had been mirrored and redistributed across multiple repositories and discussion forums. Some reports indicate thousands of repositories were affected in the takedown sweep, raising further controversy in the developer community.

The larger issue now extends beyond intellectual property. For US AI firms increasingly positioning themselves within national security and geopolitical debates, the incident underscores the limits of access restrictions in a globally networked developer ecosystem.

Anthropic’s efforts to block access in China may have constrained formal usage, but they did not dampen demand. If anything, the leak appears to have intensified interest, offering Chinese developers a level of visibility into a frontier US product that they otherwise would not have had.
This situation also highlights a deeper truth about the AI race, where competitive advantage no longer rests solely on model performance. Product architecture, agent design, memory systems, and deployment workflows are becoming equally important battlegrounds.

In that sense, what leaked was not merely source code. It was a snapshot of how one of Silicon Valley’s leading AI firms is trying to build the future of software development. And for developers in China, it has become required reading.