# Ownership and Delegation

Duration: 30--40 minutes

## Definition

**Project ownership** means one person is accountable for driving a
project toward its agreed outcome. The owner does not need to perform
every task.

**Delegation** transfers responsibility and appropriate authority while
keeping enough management visibility to ensure the outcome.

## Simple Mental Model

> **One project, one clearly accountable owner.**

The owner manages the project. You manage the owner, priorities,
escalation, and portfolio.

## How It Works

A project owner should increasingly:

-   Draft the project brief
-   Clarify outcome and DoD
-   Propose scope and milestones
-   Identify dependencies and risks
-   Coordinate contributors
-   Maintain status
-   Surface scope changes
-   Escalate blockers
-   Drive closure

Your role:

-   Approve and prioritize
-   Challenge the plan
-   Confirm commitments
-   Coach
-   Resolve priority/authority conflicts
-   Escalate organizational blockers
-   Review outcomes

Delegation can increase progressively:

1.  Research and report
2.  Recommend a plan
3.  Act after approval
4.  Act and inform
5.  Own the outcome within agreed boundaries

Accountability must come with enough authority to coordinate and
escalate.

## Example

Instead of writing the Umami plan yourself:

> Draft the outcome, DoD, scope, milestones, dependencies, risks, and
> proposed forecast. We'll review it together Friday.

The owner proposes eight weeks. You challenge assumptions and agree on a
commitment. They maintain the project afterward.

## How It Fits Into the Bigger Picture

Everything learned so far becomes information the project owner manages.
This is the transition from:

> Amadou manages every project

to:

> Amadou manages a system in which people can own projects.

## My Company / Real-World Context

You do not have a PMO assigning PMs to your work. Integrators, analysts,
QA, or other team members can own projects depending on capability and
subject matter.

Project ownership also develops employees beyond ticket execution.

## CTO Perspective

Broader technology leadership requires an organization that can operate
without you personally coordinating everything.

The goal is:

> I know the portfolio and intervene where needed.

not:

> Nothing moves unless I chase it.

### Questions to Ask

-   Who is the single owner?
-   What can they decide without me?
-   What must come back to me?
-   Are they maintaining the project or am I?
-   Are they escalating early?
-   Am I coaching or taking the project back?
-   Does accountability match authority?

## Meeting Scenario

**Situation:** An owner finds a Product request that changes scope and
immediately asks you what to do.

**Possible response:**

> You've identified the scope change correctly. Before I decide, tell me
> the impact on the milestone and what options you recommend. Bring me
> the trade-off, not only the problem.

## Key Takeaways

-   Every project needs one clearly accountable owner.
-   Owners drive outcomes; they do not perform every task.
-   Owners should draft and maintain the project brief.
-   Managers validate, challenge, coach, prioritize, and escalate.
-   Delegation increases with capability.
-   Accountability must match authority.
-   Developing owners makes the system scalable.

## Related Concepts

-   \[\[Portfolio Management\]\]
-   \[\[Meetings and Follow-up\]\]
-   \[\[Status Reporting\]\]
-   \[\[Project Health\]\]