The "Fix It" Request That Isn't a Project Yet

No - as stated, this is an operations problem, not a project. A project is temporary, has a defined start and end, and produces a specific deliverable. "Fix onboarding" is ongoing, has no boundary, and has no way to be declared finished.

Dana should resist both failure modes: refusing the request outright, and quietly turning it into an open-ended workstream.

1. Run a short discovery (1–2 weeks of the coordinator's time) to convert the complaint into a measurable outcome - e.g. "reduce 30-day driver attrition from 22% to 12% in the Southeast region within one quarter."
2. Propose a bounded project that can actually close: redesign onboarding for one region, pilot it, measure, then hand the process back to operations for ongoing ownership.
3. Write a one-page charter input for the PMO gate: goal, success measure, in-scope/out-of-scope, rough effort, people requested, and known dependencies (especially IT capacity tied up by the TMS rollout).
4. If no bounded deliverable emerges, say so and keep it in operations as continuous improvement - that is a legitimate answer, not a failure.

The test is whether Dana can name the deliverable, the end date, and the measure of success. If she cannot, she has not yet earned the right to plan.

Recognize what the VP is trading away, then make it a conscious decision rather than an accidental one.

The VP has real authority, but skipping intake costs Dana three things:

• Priority visibility. The PMO gate is where conflicts with the TMS rollout get surfaced. Bypassing it does not remove the conflict; it just makes Dana the one who discovers it late, when IT has no capacity.
• Borrowed authority. Dana has no line authority over the coordinator, IT, or field trainers. A logged, chartered project is what lets her ask functional managers for commitments. An informal favor from a VP does not transfer.
• Reporting legitimacy. Work that is not in the portfolio is invisible when resources are cut.

A good response is neither compliance nor refusal: "Happy to move fast. Let me use the expedited intake - one page, I'll have it to you Thursday - so we're visible against the TMS work and I can pull people without begging." Then document the decision, including the risk the VP accepted, in the charter or decision log. If the VP still declines, note the residual risks (resource collision, no escalation path) in writing and proceed.

PMO type. A supportive PMO provides templates, best practice, and training with low control; a controlling PMO requires compliance with methods and templates; a directive PMO places project managers under PMO control. A quarterly gate suggests some controlling behavior, but for a small operational improvement Dana should argue for a light-touch, supportive path with a single intake form - heavy governance on a first, uncertain initiative produces paperwork, not value.

Structure. With no budget, no direct reports, and only 10% of a coordinator, Brightline is functionally organized or at best a weak matrix. Consequences for Dana:

• She cannot assign work; she must negotiate it, with the sponsor's stated priority behind her.
• She needs a RACI that names functional managers as accountable for delivering their people, not just "informed."
• She should build a small coalition early - the field training lead and one IT contact who can speak to TMS capacity - rather than escalating cold.
• Her influence comes from the charter, a short weekly cadence, and visible progress, not from rank.

Knowing she is in a weak matrix is not a complaint; it is the design constraint her plan has to fit.