Define & Commit
PM records dimensions, substrate, artwork owner and business-hour restrictions. Client signs artwork; store managers confirm access in writing.
Gate: one approved site packet per store.This is a fictional work sample, not a completed client engagement. The original brief supplies five stores, six weeks, $40,000, stores remaining open and a four-day artwork delay. Store details, prices, schedules and results below are explicit modeling assumptions. Inspect the assumptions.
A batch-based release makes the slowest approval everyone’s problem. The project manager (PM) introduces a site-level readiness checklist, assigns an owner, and tracks the next action.
Release each store independently. A blocked approval stops that store—not the entire rollout.
25 minutes returned to coordination. Assumes a five-store update takes 12 minutes per store before, 7 after. A 42% reduction is a hypothesis to test in a pilot, not an observed saving.
Survey first, approve by Day 14, produce by store, and schedule installations around business hours. Select a location to inspect its constraints.
Broadway corridor
PM records dimensions, substrate, artwork owner and business-hour restrictions. Client signs artwork; store managers confirm access in writing.
Gate: one approved site packet per store.Vendor produces only approved files. PM validates readiness 48 hours before each installation window and escalates missing approvals within one day.
Gate: artwork, materials, access and crew confirmed.Installation lead submits photos next day. PM logs defects, reserves two days for correction and client acceptance, then reconciles costs.
Gate: five signed acceptance records.Adjust the SoHo approval delay and choose a response. Cost, store dates, schedule buffer and the rollout plan update together.
Planned approval Day 14. A two-day buffer between production and installation absorbs a small delay.
02 / CHOOSE THE RESPONSE*Each site allows one inspection day and two correction / acceptance days. Forecasts assume no further defects or access failures.
| Response | Forecast Spend | Acceptance | Buffer to D42 | Primary Tradeoff |
|---|
Costs: $18,000 production + $9,800 installation + $4,200 coordination / logistics + $2,800 inspection / corrections allowance = $34,800 base. The $40,000 cap leaves $5,200 contingency. Incremental recovery costs are drawn from that reserve, not added to the cap.
Dates: Artwork is due D14; seven calendar days of production finish D21; the first installation window is D24, with D22–23 as a two-day schedule buffer. A delay greater than two days triggers recovery. Final acceptance = latest installation day + three days. Schedule buffer = D42 − final acceptance.
Decision rule: Preserve at least five calendar days before D42 where feasible, then choose the lowest incremental cost. This favors resequencing through a six-day delay and rush production at 7–10 days. The five-day guardrail is a planning assumption, not a contractual requirement.
Limits: Fixed hypothetical quotes, one delayed approval, confirmed alternate access, no crew conflict, no holiday calendar and no probability model. This estimates schedule mechanics; it does not estimate the likelihood of delivery.
The selected forecast is a scenario result. A real rollout would need signed records and a pilot before claiming any operational improvement.
| Success Measure | Target | Evidence Required | Owner / Review |
|---|---|---|---|
| Delivery | 5 / 5 accepted by D42 | Client acceptance log, dated photographs, closed punch list | PM / daily in install week |
| Budget Control | ≤ $40,000 total spend | Approved POs + invoices + committed cost forecast | PM / twice weekly |
| Store Continuity | 0 unplanned interruptions to store operations | Store manager sign-off and incident log for every visit | Store manager / per install |
| Readiness Compliance | 100% of crew deployments pass all four checks | Approved artwork, materials, access and crew checklist | Installation lead / 48h before |
| Coordination Time | 60 → 35 min per five-store status review | Time three baseline and three pilot reviews; compare median and completeness | PM / pilot review |
Blocker: SoHo artwork approved D18, four days late. Production now ends D25, after its original D24 installation window.
Decision requested: Authorize $900 resequencing, conditional on Chelsea D24 and SoHo D28 access confirmation.
Next 24 hours: PM secures both written access changes; vendor confirms split release; installation lead reconfirms crew and materials.
Escalation: If the swap is unconfirmed by D19, request rush feasibility and client approval. No unapproved print release.
Fixed example of the default four-day scenario.All suppliers and quotes are fictional. Production quotes cover the same five-store artwork scope; installation is budgeted separately.
| Supplier | Quote / Lead Time |
|---|---|
| Metro Print · Selected | $18,000 / 7 days |
| Value Graphics | $16,400 / 10 days |
| Artisan Display | $19,200 / 6 days |
Why Metro: Assumed site-level release support and a four-day rush option. Value saves $1,600 but misses the first D24 installation window under the standard sequence. Artisan buys one day for $1,200; the default delay still misses D24.
Before selecting a vendor, verify material samples, split-shipment charges, insurance and access capability. Lowest quote alone does not determine the award.
Pilot at Chelsea: Test the readiness checklist at the first resequenced installation. Record coordination time, checklist completeness and any store interruption.
Continue when: All gates are documented, store operations remain uninterrupted and the store manager accepts the installation.
Revise when: Status time improves but missing information or defects increase. Faster updates alone are insufficient.
Handoff: Archive approved artwork, access confirmations, acceptance photos, warranties, final cost reconciliation and lessons learned. Assign any unresolved defect to a named owner and due date.
This portfolio demonstrates how I structure a constrained project. It makes no claim of real client delivery or measured business results.
Make the dependency visible.
Give the next action an owner.
Keep the plan moving.