🏢 Beyond Banking

The Unique Power Ecosystem

Healthcare is the most complex stakeholder environment you will encounter. Unlike banking where the power hierarchy is mostly legible (front office → middle → back), healthcare has multiple intersecting hierarchies that don't answer to each other.

The Political Cast:

• Clinicians (Doctors/Consultants) — The most politically dangerous stakeholders. They carry implicit veto power over any product touching patient workflows. They did not apply for the job of product reviewer. They resent the imposition.
• Nursing & Allied Health — Day-to-day implementers of any system change, often completely ignored in design. This is political malpractice; they will make or break adoption.
• IT / Informatics teams — Often hold legacy system keys. In many hospital systems, they predate any agile practice by 20 years and have the institutional memory to outlast you.
• Compliance & Legal — More powerful than in most sectors. HIPAA (US), GDPR, clinical governance frameworks create hard walls that cannot be negotiated around.
• Patients / Patient advocacy groups — Increasingly powerful, especially in digital health, where patient experience data now drives procurement decisions.

The Clinical Resistance Problem

Adoption barriers in healthcare are significant — clinicians do not necessarily welcome new tools unless the benefits of using them become immediately evident. This is structurally different from banking, where a new system can be mandated. In healthcare, a consultant surgeon can simply refuse to use a new EHR feature, and there is limited mechanism to compel them.

Doctors and staff members may be resistant to new tools, especially if workflows change. Seamless integration of new products into legacy systems — whether electronic health records or laboratory management software — often proves problematic.

Translation from the Banking Playbook

The AI Product Owner Problem (Healthcare-Specific, 2025–2026)

For AI in healthcare, product owners face unique challenges: they must ensure clean datasets for training, manage vendor selections, balance commercial and clinical metrics, and constantly iterate on performance. The accountability question is now existential — who is responsible when an AI recommendation causes patient harm? This is an unresolved political and legal question that every healthcare PO is navigating in real time.

The Illusion of Meritocracy at Scale

Big tech sells an image of pure meritocracy — data-driven, flat(ish), rational. Practitioners consistently report something different.

One r/ProductManagement thread described FAANG product management as generating: "an endless stream of internal meetings consisting of political infighting, posturing, jockeying for control, and smaller private post-meeting meetings to talk about others."

Another PM from r/ProductManagement, on transitioning from startups to FAANG: "Play the political game. You'll get better at it and learn when to push and when to pull — but you don't get the resources you need or the funding you need if you don't play the game."

The Big Tech Political Structure

• Scope, not title, determines actual power. At Amazon, Meta, and Google, a "Senior PM" who owns a product used by 200 million people outranks a "Director PM" managing internal tooling. But these scope differences are invisible from the org chart.
• The "headcount fight" is the central political arena. Engineering resources are the scarce commodity. Who gets engineers determines who ships products. Political capital at FAANG = engineering allocation.
• The data religion can be weaponised. Data-driven culture means bad actors can manufacture supporting data for predetermined decisions. Learning to interrogate data claims — not just present them — is a survival skill.

Amazon's Specific Political Operating System

AWS PMs communicate with internal stakeholders, collaborate with other product managers and engineers in multiple development teams, and work with sales teams on adoption plans — and while they may not be the most senior people in the room or have the deepest technical expertise, they consistently work to earn trust with all stakeholders, which is one of Amazon's core leadership principles.

Amazon's "Working Backwards" and narrative-document culture (no PowerPoint, written 6-pagers) is not just a process — it's a political equaliser. The quality of your written thinking is visible in ways that banking's deck culture hides. This rewards different political skills.

Amazon's performance reviews now formally evaluate Leadership Principles, making the connection between cultural fit and career advancement explicit. The updated process increases the granularity of ratings, strengthening the connection between performance and culture.

Translation from the Banking Playbook

The Most Honest Description of the PO Role — Anywhere

Deloitte's analysis of government POs produced what may be the most honest job description ever written for this role: a good PO has to be part business analyst, part technologist, and full-time diplomat — a communicator who commands respect throughout the organisation while often operating without a large staff, extensive authority, or a lofty title. The PO role may be even more challenging in the public sector than elsewhere, for key structural reasons.

Critically: a government product owner must have enough "political capital" to guide the project team through the inevitable challenges and to maintain the focus of senior leadership in light of competing agency priorities.

The Structural Differences from Banking

Bureaucracy as Architecture: In banking, bureaucracy is an obstacle. In government, it is the operating environment. A layered bureaucracy can hinder the application of agile methods. Agile transformation in government requires a dual commitment — implementing agile methodologies while simultaneously challenging underlying ideologies and assumptions.

The Procurement Political Layer: Every technology decision in government goes through procurement. This creates a political dimension that simply doesn't exist in private sector: vendor relationships, contract structures, and public accountability frameworks all constrain what you can build, buy, or change.

Tenure = Power: Unlike banking where tenure can be disrupted by a bad quarter, government has career civil servants who will outlast every political appointee, every external consultant, every agile transformation programme. The long-serving programme manager who has survived seven different digital transformation initiatives is the most important person in the building. They know where all the bodies are buried.

No P&L Frame: The "frame in revenue/risk terms" rule from banking doesn't work here. The frame that works in government is citizen outcomes, cost per service, and ministerial/elected official priorities. Political cycles matter — a project that doesn't show visible results before an election is politically dead regardless of its actual merit.

Translation from the Banking Playbook

The Liberating Inversion

The startup experience is the closest thing to a pure meritocracy that actually exists. From r/ProductManagement practitioners:

"You can never fully avoid politics, but startups have way less of it. At big companies, politics and bureaucracy were the full-time job of many employees. At a startup the goal is to grow the business and for the most part everyone is aligned on that goal."

Less bureaucracy is chaotic, but can make rapid career growth much easier — and creating a role specifically for yourself becomes possible. The startup environment trades depth for breadth.

But Startups Have Their Own Political Terrain

It's not politics-free — it's politics differently configured:

• Founder authority is absolute and emotional. In banking, the MD's authority derives from revenue and institutional position. In a startup, the founder's authority derives from vision, ownership, and often sheer force of personality. Disagreeing with a founder requires a fundamentally different political approach than disagreeing with an MD.
• Equity and comp opacity create hidden resentments. In banking, comp structures are known (at least by band). In startups, nobody knows what anybody else makes or holds in equity. This generates simmering political dynamics that periodically explode during funding rounds or exits.
• Speed kills strategy. At a startup you have more autonomy, less existing market share to defend, and fewer stakeholders to manage — but there's nothing nimble about large companies in comparison.

The Startup PO/BA Role Reality

In startups, the product owner often wears multiple hats, acting as product manager, business analyst, or even scrum master. Title inflation is real — "Head of Product" at a 15-person company has completely different scope and political weight than at a 500-person Series C.

Translation from the Banking Playbook

The Billability Game Is the Political Game

In consulting, utilisation rate is the revenue equivalent of banking's P&L. A consultant who is 80%+ billable is politically safe. One who drops to 60% is visible, in a bad way.

For BAs and POs embedded in or adjacent to consulting:

• Client relationship ownership is the senior partner's most jealously guarded asset — do not ever appear to be building an independent relationship with the client that bypasses your partner.
• The deliverable is the political artefact. In consulting, the deck is the product. Who authors it, who presents it, whose name appears on it — these are political decisions as much as creative ones.
• "Up or out" is explicit and codified. Unlike banking where it's informal, consulting firms formally manage staff against promotion timelines.

Product management in consulting requires skills that directly translate to client engagement — including pricing analytics, demand forecasting, and strategic revenue optimisation — but the political context means everything must be framed around client outcomes rather than internal product development.

Translation from the Banking Playbook

The Regulatory Authority Is the Shadow Government

In pharmaceutical and biotech, the FDA (US), EMA (EU), MHRA (UK), and equivalent bodies have more actual power over your roadmap than any internal executive. Understanding this reshapes every political calculation.

Today's FDA operates at the intersection of rapidly evolving science, political intervention, deregulation mandates, and digital transformation — requiring regulatory affairs and quality leaders to remain highly agile and forward-thinking.

The Pharma-Specific Stakeholder Stack

• Medical Affairs / KOLs (Key Opinion Leaders) — physicians with influence over prescribing and clinical adoption. Their endorsement is worth more than any marketing budget.
• Regulatory Affairs teams — the internal compliance function with de facto veto over launch timelines. Build this relationship or face perpetual delay.
• Commercial / Market Access — the P&L owners who will eventually determine whether your product lives or dies post-launch. Loop them into roadmap decisions early; they will override you later if you don't.
• R&D / Clinical teams — the scientific authority. In pharma, "the data" from clinical trials carries authority that no business case can override.

Employers are looking for professionals who can lead across departments and geographies — with skills in strategic planning, stakeholder alignment, and budget oversight being increasingly important, especially in the context of M&A integration or global product launches.

Translation from the Banking Playbook