Translation table Your proof supports four rows, so there are four. | What you did | How a hiring manager says it | |---|---| | Led the EHR rollout on your ward | Owned the launch and adoption of a clinical software product in a live, high-stakes environment | | Trained 40 staff | User onboarding and enablement, plus change management across a mixed-skill user base | | Two workflow documents adopted hospital-wide | Process specification that earned buy-in without authority, the same skill as writing requirements and getting stakeholders to adopt them | | 9 years on a surgical ward | Deep domain expertise and direct knowledge of the end user's daily problems | I did not assume adoption numbers or feedback loops from the rollout. If you have real figures, add them. Otherwise leave them out. Gaps, ranked by how often they block interviews 1. No shown product decision-making: prioritizing, trade-offs, success metrics. 2. No experience working inside a software team (engineers, sprints, tickets, specs). 3. Thin technical fluency: how health data moves between systems (FHIR basics), reading simple data. 4. No formal product training. This rarely blocks anyone and sits last. Route **Bridge role: Clinical Informatics Analyst**, at a health system or a healthcare software vendor. It is a paid job where you sit between clinicians and a software team, so it closes gap 2, your biggest structural gap, which no side project can fake. It also gives you real product exposure, and your rollout experience is the proof that gets you hired into it. Projects close gaps 1 and 3 while you apply. - Same-company move: your hospital is not a software company, and nothing in your proof shows a path to a product role there. - Direct application: three gaps remain, and the rule allows one. - Credential first: PM roles are not routinely gated by a credential, so you would spend 150+ hours on something employers don't require. Time check The deadline is about 43 weeks away. 6 hours × 43 weeks = **258 hours available**. Needed: gaps 1 and 3 are project-closable at about 60 hours each (120). I budget another 60 for the bridge-role search that closes gap 2. That is **180 hours needed**, so the hours fit. The calendar is the soft part. Hiring timelines are outside your control. A bridge-role offer by week 36 is realistic on these hours. The PM title itself inside 10 months is not something I can promise, and it more likely lands after the bridge role. My recommendation is to set the 10-month target as "in the bridge role or in PM interviews" and review the title date at week 43. Plan Weeks 1–2: the test (12 hours) - Have one 20-minute call with the PM you know (message 1 below). - Turn one of your workflow documents into a one-page requirements doc: the problem, the user, and how you'd measure success. - Read five healthcare product or informatics job postings. Mark what you already do and what feels foreign. - At the end of week 2, ask yourself whether the work and the call made you curious or drained. If drained, stop here and you've lost 12 hours, not 10 months. Milestone 1, week 12 (60 hours, weeks 3–12): a published case study - Publish a "rollout teardown": the problem, who the users were, what you decided, how you knew it worked, and what you would change. Add a full requirements doc for one improvement. - Put it on LinkedIn or a public Notion page. This closes gap 1. Milestone 2, week 24 (72 hours, weeks 13–24): a referral - Complete a short written explainer, "how a patient record moves between systems", using FHIR terms. Have your PM contact review it. About 36 hours, and this closes gap 3. - Hold at least three informal conversations with informatics or product people. About 36 hours. - The deliverable is one person submitting you as a referral for a Clinical Informatics Analyst opening. Milestone 3, week 36 (72 hours, weeks 25–36): an interview - The deliverable is at least one first-round interview for a bridge role, built on the case study and the explainer. - Weeks 37–43 (42 hours) are a buffer for interviews, a second referral, or the date decision. Biggest-blocker countermeasure (outsider, no credibility), done by week 4 - By the end of week 2, write five sentences describing your rollout in the table's language, for example "I led adoption of an EHR for [N] users and trained 40 staff." In your week 1 call, ask the PM to correct the wording, then use those sentences in every later conversation. - Attend one live nursing-informatics or healthcare-product webinar or meetup by week 4. Ask one question from the clinical side that an engineer would not think to ask. That makes you the person with the knowledge in the room, not the outsider. Outreach (send in weeks 1–4) Message 1, to the PM you know (week 1): "Hi [Name], I'm exploring a move from surgical nursing into healthcare product management. I led our ward's EHR rollout and trained 40 staff. Could I have 20 minutes in the next two weeks to ask how you'd describe that experience in PM terms? Happy to work around your schedule." Message 2, to a healthcare PM you don't know (week 3): "Hi [Name], I'm a surgical nurse (9 years) who led an EHR rollout and I'm learning product management. I rewrote one workflow as a one-page requirements doc. Would you glance at it and tell me the one thing a PM would change? Two minutes of feedback would help a lot." Message 3, to a nurse who moved into informatics or product (week 4): "Hi [Name], I saw you moved from nursing into informatics. I'm a surgical nurse who led an EHR rollout and I'm exploring the same path. What was the one thing you wish you'd known before your first interview? A two-line reply is plenty, and I'd be grateful." Check: route chosen 1 | hours needed 180 vs available 258 | milestones 3 | outreach messages 3