Industry-specific patterns matter — generic PM advice has limits

Generic PM advice gets you 70% of the way. The last 30% is industry-specific.

PM curricula and certifications optimize for transferability — the disciplines they teach are designed to apply across industries. There is a real benefit to that: a PM who learned the craft in software can move to construction with most of their skills intact, and vice versa. The downside is a kind of generic-ness that misses the particular shape of any given industry's project work.

The particular shape matters more than the curricula imply. A healthcare project's regulatory burden is not just more regulation than software; it is a different kind of regulation, with different surface conditions, different escalation paths, and different failure modes. A marketing campaign's relationship to its sponsor is not just more sensitive than a software project's; it is structured differently, around brand and audience considerations that have no software equivalent. The generic playbook does not surface these differences.

This piece is the long-form anchor for the Industry-Specific PM pillar. It walks six industries — healthcare, construction, software, marketing, manufacturing, financial services — with the dominant PM pattern in each, the failure mode that most distinguishes that industry, and the cross-industry transfer tips that hold up when a PM moves between sectors.

§1 — Healthcare PM

Dominant pattern: Regulatory primacy. Almost every meaningful decision on a healthcare project either starts with a regulatory question (HIPAA, FDA, state-level licensing) or runs into one before the project ships. The regulatory layer is not a constraint on the project; it is the frame within which the project exists.

Distinguishing failure mode: The regulatory surprise at launch readiness. The project has been built; the team has been calling out we need legal and compliance review for months; the actual review happens at launch readiness; the review surfaces issues that should have been caught at design. The launch slips by 6-12 weeks while changes are made.

The fix: Compliance is not a review gate; it is a continuous discipline. The compliance team is part of the project's regular cadence (weekly or biweekly), participates in design decisions, and signs off incrementally. The launch-readiness review becomes a confirmation, not a discovery.

Transfer tip for PMs new to healthcare: The compliance team's no is not opposition; it is the system functioning. Treating compliance as adversarial is the most-common PM-coming-from-software error. The compliance team's job is to keep the org out of regulatory trouble; the PM's job is to deliver the project; both jobs are aligned with cooperation.

§2 — Construction PM

Dominant pattern: Sequence rigidity and physical constraints. Construction has a true critical path in a way software rarely does — pour the foundation before framing, frame before drywall, drywall before paint. The sequencing is not a planning preference; it is dictated by physics. The schedule's failure modes are more concrete (literally) than software's.

Distinguishing failure mode: The trade-stack collapse. A delay in trade A pushes trade B's date; trade B has another job booked starting on the original date; trade B does not wait. The project loses two weeks not from the original delay, but from the cascading rebooking of every trade downstream.

The fix: Buffer between trades. The construction PMs who hit dates plan one or two days of slack between every trade handoff. The buffer absorbs small slips without cascading; without it, the first slip propagates through the entire schedule.

Transfer tip for PMs new to construction: Site visits are not optional. A PM who manages a construction project from a desk loses information that the field is constantly transmitting — weather, materials condition, trade morale, sub-quality. The weekly site visit is the equivalent of the software PM's standup; both are about catching small things before they grow.

§3 — Software PM

Dominant pattern: Requirements evolution. Software requirements are rarely fully knowable upfront. The act of building reveals what the right thing to build was, and the methodologies (Scrum, Kanban, hybrid) all exist to absorb that evolution. This is the industry that forced the biggest revision to traditional PM practice in the last 30 years.

Distinguishing failure mode: Silent scope absorption. The team absorbs scope changes without surfacing them through change control. By month three, the project is delivering something materially different from what was chartered, and the steering committee has lost the audit trail of how it got there.

The fix: Written change log above a stated threshold (often one engineer-week). Every change above the threshold goes through the named decision-maker in writing. The discipline catches drift while it is small.

Transfer tip for PMs new to software: Resist the impulse to plan the entire project up front. Software work that is planned in detail beyond the next 8-12 weeks tends to invalidate that plan as the team learns. Plan in detail for the next phase; outline at low resolution for everything beyond it; re-plan at every phase boundary.

§4 — Marketing PM

Dominant pattern: Brand alignment and creative judgment. Marketing projects answer to a brand, not just a brief. Decisions that look small to a non-marketer (the headline copy, the photo selection, the channel mix) are not small; they ladder up to brand consistency that takes years to build and weeks to break.

Distinguishing failure mode: The brief drift. The campaign brief gets approved at month one; by month three, the creative is drifting in a direction that is more creative-team-aesthetic than brand-aligned. The creative team is not malicious; the creative work has its own gravity. The drift becomes visible only at brand review, by which point recovery is expensive.

The fix: Brand review is a recurring cadence, not a launch gate. Every two to three weeks, the work-in-progress is shown against the brief and the brand. Drift is small at this cadence and easy to correct. By the time it surfaces at launch review, it is large.

Transfer tip for PMs new to marketing: Brand judgment is a real skill, and not the PM's. The creative director or brand lead has it; the PM's job is to surface drift early enough that the brand lead can correct it cheaply. Trying to override the brand lead's judgment is the most common error PMs from other industries make.

§5 — Manufacturing PM

Dominant pattern: Tooling lead time and line-rate ramp. Manufacturing projects depend on physical tooling that takes 6-18 months to specify, build, and qualify. The line-rate (units per hour) is not just a target; it is a constraint of the tooling itself. Once the tooling is built, changing the line-rate is expensive.

Distinguishing failure mode: The tooling-availability surprise. The pilot run scheduled for month nine slips because the tooling supplier missed their delivery date. The downstream qualification, ramp, and launch all push by the same amount. Manufacturing PMs without buffer at the tooling step see this fail mode regularly.

The fix: Tooling vendors are locked in years in advance, with multiple suppliers contracted for critical tools. The contract has explicit lead-time commitments and contingency for slip. The manufacturing PMs who hit dates treat tooling as the project's actual critical path, not as a procurement detail.

Transfer tip for PMs new to manufacturing: The line is the system. A PM who treats the manufacturing project as a sequence of work items rather than as the design and ramp of a continuously operating system loses the ramp dynamics. The line-rate curve from pilot to full production is the project's most-important schedule artifact.

§6 — Financial services PM

Dominant pattern: Audit trail and regulatory permits. Every change in financial services has to be defensible in an audit, sometimes years after the fact. The artifact density is higher than in any other industry; the documentation discipline is not optional.

Distinguishing failure mode: The audit-finding surface in production. The project shipped; six months later an internal audit (or a regulator) reviews the work and finds documentation gaps, control gaps, or process gaps. The remediation is expensive and visible to senior leadership.

The fix: Compliance and audit run parallel to the project, not in series. The audit team is involved in design; compliance reviews are continuous; the artifact set is built incrementally as part of the work, not produced after the fact. The teams that ship cleanly in financial services have an artifact-per-decision discipline that PMs from other industries find intense at first.

Transfer tip for PMs new to financial services: The documentation is the work. A decision that was made and not documented might as well not have been made — there is no audit trail to defend it. PMs from less-regulated industries underestimate how much of their week becomes documentation work, and undertraining the team for that level of artifact discipline is the most-common early misstep.

§7 — When and how to change industries

A PM moving between industries faces a real adjustment. The generic skills transfer; the industry-specific patterns do not. The honest version of cross-industry transition takes about six months of deliberate learning, not six weeks.

The move that works has three steps:

• Read the industry's failure modes before joining a project. Every industry has trade press, post-mortems, and regulatory case studies. Read enough of them that the dominant patterns from §§1-6 above are in your head before week one.
• Pair with a senior PM in the new industry for the first six months. The senior PM's job is to flag the moments where you are about to apply the generic playbook to a situation that has a known industry-specific gotcha. This is the highest-leverage cost in cross-industry transition.
• Resist the impulse to redesign the new industry's processes from your old industry's frame. A software PM in healthcare who tries to agilize the compliance review will fail. The processes evolved for reasons; the reasons are usually visible if you look. Earn the right to redesign them by first running them as they exist.

§8 — How to use this pillar

The rest of the Industry-Specific PM pillar walks each industry in operational detail — the regulatory landscape, the dominant artifacts, the typical schedule shape, the failure modes specific to that sector. If you are working in one industry, read that industry's piece in depth; the others are interesting but not load-bearing.

The meta-rule: industry pattern is application of the generic platform. Both are needed; treating either as sufficient is a mistake. Cross-industry transitions are six-month learning curves, not weeks.