Charles Nwosu PMP · MBA
About

Who I am as a project manager

My work sits where projects tend to break down: competing priorities, unclear scope, shared resources, and stakeholders who each believe something different about what "done" means.

I am a PMP-certified Project Manager with an MBA in Project Management and eight years leading cross-functional initiatives from planning and scope definition through execution, delivery, and closeout. That work has spanned technology implementation, infrastructure, operations, and service delivery.

What I build, more than anything, is visibility. Most projects do not fail because the work was too hard. They fail because nobody could see the problem while there was still time to act on it. Schedules, dashboards, RAID logs, and decision records are not paperwork to me; they are the instruments that let a team catch a slip in week three instead of week eleven.

I have recovered a stalled implementation with $85,000 committed and delivered it inside six weeks. I have run nine concurrent projects competing for one pool of people without losing track of which one was about to slip. I have led a 14-person team through the unglamorous work of standardizing handoffs, and watched the procedures outlast my involvement.

I work across technology implementation, infrastructure, operations, and service delivery, and I am based in San Jose, California.

Charles Nwosu at the United Kingdom Mission to the United Nations, wearing a delegate badge
Charles Nwosu with a cohort of fellow delegates around a conference table
Approach

How I manage projects

1

Define "done" before anything else moves

Most delivery failure traces back to scope that was assumed rather than agreed. I get the definition written down and confirmed by every group that has a stake in it, because a disagreement found in week one is a conversation and the same disagreement found in week ten is a crisis.

2

Make status visible by default, not on request

Schedules, dashboards, RAID logs, and decision records exist so that the health of the work is legible without anyone having to ask. Consistent structure across projects is what makes comparison and early warning possible.

3

Escalate early and with a specific ask

Escalation is not a failure signal, it is a routing decision. I surface blockers that will not resolve on their own while there is still time to act, and I bring a defined request rather than a description of a problem.

4

Sequence the risk to the front

The riskiest dependency should be confronted first, not deferred to the end where it can no longer be absorbed. Comfortable sequencing is one of the most common reasons a plan looks fine until the final third.

5

Build relationships that survive bad news

Delivery depends on people telling you things early. That only happens where surfacing a problem reliably gets it fixed instead of getting someone blamed, and that culture is built long before it is needed.

Capabilities

What I bring to a delivery team

Delivery capabilities

  • Project lifecycle management: initiation through closeout
  • Scope definition, change control and specification alignment
  • Schedule development, milestone and dependency tracking
  • Budget tracking and resource / capacity planning
  • Risk, issue and escalation management (RAID)
  • Multi-project portfolio coordination

Leadership & communication

  • Executive and stakeholder status reporting
  • Cross-functional, vendor and contractor coordination
  • Project review and steering meeting facilitation
  • Team leadership, staffing and workload allocation
  • Process design, documentation and standardization
  • Conflict resolution and expectation management
Contact

Get in touch

Based in San Jose, California. Email is the fastest way to reach me.

Emailcharlesnwosu111@gmail.com→ LinkedInlinkedin.com/in/charlesnwosu→