Chapter 29 / Career Growth, Interviews, and Passing Wisdom Forward / Paid beta preview

Chapter 29: The Senior Project Manager's Personal Operating System

How senior PMs build a repeatable operating rhythm for pressure, priorities, and people. ## A System For Staying Useful After Chapter 28, Lauren Brooks could explain her readiness in an interview. She had examples, metrics, boundaries, lessons, and the confidence to tell the truth without inflation. Then Monday arrived. Two studies needed governance updates. A third needed enrollment rescue support. One vendor had missed a system-release date. Data Management needed decisions before database lock. Safety/PV had a reconciliation question. A site asked for urgent clarification. Finance wanted the latest forecast. Her inbox had sixty unread emails by 8:30 a.m. Lauren stared at the screen and felt the old temptation: answer everything in order and call it leadership. Maggie Chen saw the problem. "A senior PM cannot run a trial out of an inbox," she said. "You need a personal operating system." A personal operating system is a repeatable set of habits, reviews, tools, and decision routines that helps a PM manage complexity. It is not a company standard operating procedure, or SOP. It is not one perfect template. It is the way a senior PM keeps reality visible before the trial forces visibility through failure. A senior PM is not senior because they remember everything. A senior PM is senior because they build a system that does not require memory to do all the work. Common shorthand still matters in a daily operating system. Safety and pharmacovigilance, or PV, manage safety-process discipline. A contract research organization, or CRO, performs delegated trial work. The trial master file [ICH E6(R3)], or TMF, contains essential records [ICH E6(R3)]. Corrective and preventive action, or CAPA, addresses significant or recurring problems. Electronic clinical outcome assessment, or eCOA, systems collect outcome data electronically; interactive response technology, or IRT, may support randomization, dispensing, or visit logic. A statistical analysis plan, or SAP, and tables, listings, and figures, or TLFs, shape analysis readiness. RACI means responsible, accountable, consulted, and informed. ## The RHYTHM Frame Maggie gave Lauren a frame: | Letter | Meaning | Operating Question | |---|---|---| | R | Review Reality | What is actually happening across the study? | | H | Hold Priorities | What matters most now? | | Y | Yield Decisions | What needs a decision, by whom, and by when? | | T | Track Commitments | What was promised, who owns it, and what evidence proves closure? | | H | Help Others Own | What should I delegate, coach, or clarify? | | M | Maintain Yourself | What keeps my judgment sustainable? | The frame is not decorative. It is a control loop. ## Review Reality Lauren's first change was a weekly review that did not wait for governance week. | Review Area | Weekly Question | |---|---| | Participant/safety | Any safety signal, overdue follow-up, consent issue, or participant-protection concern? | | CTQs | Are critical-to-quality [ICH E8(R1)] factors still protected? | | Critical path | Which dependency can move the finish date? | | Enrollment/sites | Which sites are screening, dormant, blocked, or overburdened? | | Vendors/CRO | Which deliverables, tickets, transfers, or owner dates are slipping? | | Data | Query aging, external-data reconciliation, coding, missingness, lock blockers? | | Quality/TMF | Deviations, CAPA, monitoring findings, essential-record gaps, inspection risks? | | Budget | Forecast, actuals, commitments, change orders, pass-throughs, burn rate? | | Decisions | What is needed, who owns it, and what forum has authority? | | Capacity | Is the team staffed to do the work being promised? | Critical-to-quality [ICH E8(R1)] factors, or CTQs, are trial features most important to participant protection and reliable results. The critical path is the chain of dependent work that determines the earliest realistic finish date. The point of the weekly review is not to admire a tracker. It is to notice weak signals before they become emergencies. ## Hold Priorities Everything in a trial can sound urgent. Not everything is equally important. Triage means sorting work by importance, urgency, impact, and needed response. Lauren used a simple priority filter: The team used the decision log [PMBOK] to turn the details into operating choices the PM could assign, monitor, and escalate: Participant protection. ask first Could rights, safety, welfare, consent, or voluntariness be affected? Safety/regulatory timing. ask first Is there a reporting, submission, approval, or ethics clock? Data integrity. ask first Could evidence, source, systems, or analysis credibility be harmed? CTQ impact. ask first Does this affect what must not fail? Critical path. ask first Could this delay the study's real finish date? Irreversibility. ask first Will waiting narrow options or create lasting harm? Governance deadline. ask first Is a decision needed before teams can act? Noise. ask first Is this loud mainly because someone is anxious? Inbox order is not priority order. The loudest voice is not always the highest risk. A senior PM keeps the difference visible. ## Yield Decisions Some work is not stuck because no one has worked hard enough. It is stuck because no one has named the decision. Lauren separated four logs: The team used the issue log [PMBOK]

...