vault backup: 2026-07-23 14:57:54
This commit is contained in:
@@ -1,103 +1,98 @@
|
||||
# Prioritization
|
||||
Duration: 30–40 minutes
|
||||
|
||||
Duration: 30--40 minutes
|
||||
|
||||
## Definition
|
||||
|
||||
Decide what should be worked on now when everything appears important.
|
||||
|
||||
This lesson is part of the Project Management track and builds on the concepts learned in the previous lessons.
|
||||
Prioritization is the deliberate decision about which work receives
|
||||
scarce capacity first. A priority is meaningful only if it changes what
|
||||
the team does.
|
||||
|
||||
## Simple Mental Model
|
||||
|
||||
The goal is not to add project-management bureaucracy. The goal is to make the project easier to understand, predict, and manage.
|
||||
**Priority means what wins when two important things compete for the
|
||||
same capacity.**
|
||||
|
||||
## How It Works
|
||||
|
||||
We will examine this concept through four levels:
|
||||
If ten projects are all High, you have not prioritized them.
|
||||
|
||||
1. What the concept means.
|
||||
2. How a project owner should use it.
|
||||
3. How you should review or challenge it as the manager.
|
||||
4. How it should eventually appear in your project-management system.
|
||||
Useful factors include business value, urgency, risk reduction, fixed
|
||||
deadlines, strategic alignment, dependencies, effort, and cost of delay.
|
||||
|
||||
## Example
|
||||
Priority is relative:
|
||||
|
||||
The exercises for this lesson should use real projects from your environment such as Umami, Mogador, QA automation, data governance, website/Product initiatives, or projects dependent on DevOps and Security.
|
||||
|
||||
The objective is to move from theory to a repeatable management practice.
|
||||
|
||||
## How It Fits Into the Bigger Picture
|
||||
|
||||
The course builds progressively:
|
||||
|
||||
- Project vs operations establishes what kind of work we are managing.
|
||||
- Outcomes and Definition of Done establish what success means.
|
||||
- Scope establishes the project's boundaries.
|
||||
- Milestones establish meaningful progress.
|
||||
- Dependencies, estimation, prioritization, capacity, risks, and health make delivery more predictable.
|
||||
- Status reporting, meetings, ownership, and portfolio management make the system scalable.
|
||||
- Closing and the final PM system turn the concepts into an operating method.
|
||||
|
||||
## My Company / Real-World Context
|
||||
|
||||
Your team works across departmental projects, Product work, operational incidents, tickets, data, QA, SEO/WCAG, and dependencies on IT teams such as DevOps and Security.
|
||||
|
||||
The lesson should therefore be applied to an environment where:
|
||||
|
||||
- Project owners are usually members of your own team rather than dedicated PMs.
|
||||
- Operational work regularly interrupts project work.
|
||||
- Product and IT are important cross-functional partners.
|
||||
- You need portfolio-level visibility without personally maintaining every task.
|
||||
- Project owners should increasingly draft and maintain their own project plans while you validate, challenge, prioritize, and escalate.
|
||||
|
||||
## CTO Perspective
|
||||
|
||||
The leadership objective is to move progressively from personally coordinating work toward building a management system that produces reliable outcomes.
|
||||
|
||||
The expected progression is:
|
||||
|
||||
```text
|
||||
Contributor → manages tasks
|
||||
Project Owner → drives milestones and delivery
|
||||
Manager → manages projects, priorities, risks and escalation
|
||||
Technology Leader → manages portfolio, capacity, outcomes and organizational trade-offs
|
||||
``` text
|
||||
1. Production incident
|
||||
2. Supabase migration
|
||||
3. Umami
|
||||
4. QA automation
|
||||
5. RAG POC
|
||||
```
|
||||
|
||||
A new top priority should force the question:
|
||||
|
||||
> What is no longer the top priority?
|
||||
|
||||
### Strategic vs Urgent
|
||||
|
||||
Urgent work can consume all capacity while important strategic work
|
||||
never progresses. Some capacity may need protection from recurring
|
||||
urgency.
|
||||
|
||||
### Example
|
||||
|
||||
Product requests an urgent website enhancement while an integrator is
|
||||
committed to an Umami milestone. Do not silently add it. Decide whether
|
||||
it outranks Umami and, if so, record which milestone moves.
|
||||
|
||||
### My Company / Real-World Context
|
||||
|
||||
Your team receives work from your roadmap, Product, operational
|
||||
incidents, Jira requests, IT/security needs, vendors, and leadership.
|
||||
Without explicit prioritization, the loudest request can become the real
|
||||
priority.
|
||||
|
||||
### CTO Perspective
|
||||
|
||||
The leadership question is not merely "Is this valuable?" Most portfolio
|
||||
items are valuable. Ask:
|
||||
|
||||
> Is this more valuable **now** than the work it will displace?
|
||||
|
||||
### Questions to Ask
|
||||
|
||||
- What information do I need to make a management decision?
|
||||
- What should the project owner be responsible for maintaining?
|
||||
- What requires my intervention?
|
||||
- What can be standardized across every project?
|
||||
- Is the process helping delivery, or merely creating administration?
|
||||
- What happens if we do not do this now?
|
||||
- Is there a fixed deadline?
|
||||
- What business outcome does it support?
|
||||
- What does it unblock?
|
||||
- What will move if this becomes priority?
|
||||
- Who can change the priority?
|
||||
|
||||
## Meeting Scenario
|
||||
### Key Takeaways
|
||||
|
||||
**Situation:**
|
||||
- Prioritization allocates scarce capacity.
|
||||
- Everything cannot be High.
|
||||
- Priority must resolve conflicts between work.
|
||||
- New urgent work should expose what it displaces.
|
||||
- Constant reprioritization damages predictability.
|
||||
- Managers should resolve cross-project priority conflicts rather than
|
||||
leaving contributors to choose.
|
||||
|
||||
A project owner gives you an update, but the information does not make it clear whether the project will achieve its intended outcome.
|
||||
## How It Fits Into the Bigger Picture
|
||||
|
||||
**Possible response:**
|
||||
|
||||
> Let's bring this back to the project plan. Show me where we are against the next meaningful checkpoint, what is at risk, and what decision or help you need from me.
|
||||
|
||||
## Key Takeaways
|
||||
|
||||
- The purpose of project management is predictable delivery, not documentation for its own sake.
|
||||
- Project owners should own increasingly more of the planning and maintenance.
|
||||
- Your role is to challenge assumptions, establish priorities, remove/escalate blockers, and manage the portfolio.
|
||||
- Every concept learned should eventually contribute to one lightweight common project template.
|
||||
- The final system should make exceptions and problems visible without requiring you to inspect every task.
|
||||
This lesson builds on \[\[Projects vs Operations\]\], \[\[Outcomes and
|
||||
Definition of Done\]\], \[\[Scope and Scope Creep\]\], and
|
||||
\[\[Milestones vs Tasks\]\]. It prepares the project system to become
|
||||
more predictable and scalable.
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Projects vs Operations]]
|
||||
- [[Project Outcome]]
|
||||
- [[Definition of Done]]
|
||||
- [[Scope]]
|
||||
- [[Milestone]]
|
||||
- [[Dependencies]]
|
||||
- [[Capacity]]
|
||||
- [[Risk]]
|
||||
- [[Project Health]]
|
||||
- [[Portfolio Management]]
|
||||
- \[\[Milestones vs Tasks\]\]
|
||||
- \[\[Dependencies\]\]
|
||||
- \[\[Estimation and Forecasting\]\]
|
||||
- \[[Prioritization](#prioritization)\]
|
||||
- \[\[Capacity and WIP\]\]
|
||||
- \[\[Risk Management\]\]
|
||||
- \[\[Project Health\]\]
|
||||
- \[\[Portfolio Management\]\]
|
||||
|
||||
Reference in New Issue
Block a user