Class Handout – Project Management / Management

Topic: Initiation Phase, Project Mandate, Goal Definition, Stakeholders, Risks, Communication Logic

1. Importance of the Initiation Phase

The initiation phase determines the long-term success or failure of a project. Most issues that later appear during execution originate here — when goals, boundaries, stakeholders, and risks are still unclear.

The initiation phase provides:

• clarity
• alignment
• direction
• structure
• legitimacy for later decisions

If this phase is weak, the project becomes unstable. If it is strong, execution becomes significantly easier.

2. From Project Idea to Project Mandate

Project Idea

A project typically starts with an unstructured idea:

• “We should digitalise this process.”
• “We need automation.”
• “Customer experience must improve.”

Ideas express intention, not clarity.

Project Mandate (Project Order)

The mandate transforms the idea into a defined mission. It answers:

The mandate is the first structured output of the project. It creates a shared understanding for everyone involved.

3. Goal Definition – Beyond SMART

SMART offers a basic structure but is insufficient for complex projects. Effective goals must go deeper.

Effective goals have three essential qualities

1) Observability

A goal must describe a visible change:

• “Reduce onboarding drop-off by 20%.”
• “Automate 30% of manual validation steps.”

2) Shared Understanding

Every team member should be able to describe “done” in the same way.

3) Stability Under Pressure

A strong goal remains a reliable compass even in stressful phases.

Examples

Weak goal: “Implement CRM.”

Strong goal: “Provide sales teams with an integrated customer profile by consolidating data from systems X, Y, Z into CRM.”

4. Purpose – The Reason Behind the Goal

Purpose explains why the project exists. It answers:

• What problem disappears?
• What opportunity emerges?
• Why is this needed now?
• What happens if it is not done?

Purpose creates meaning, alignment, and resilience. Teams that understand purpose can navigate uncertainty better than teams that only understand tasks.

5. Stakeholder Analysis

Stakeholders define the environment in which a project operates. Aligning them early prevents friction later.

Stakeholder analysis includes:

1. Identification – who is affected or involved
2. Classification – power, interest, influence
3. Understanding – expectations, fears, incentives
4. Anticipation – conflicts, barriers, political dynamics
5. Communication planning – targeted, structured dialogue

Different groups require different forms of communication:

• Decision-makers → concise, outcome-focused
• Users → practical relevance
• Regulatory functions → compliance clarity
• Technical teams → detailed requirements

Early alignment is essential because it cannot be created retroactively once the project is in motion.

6. Risk Analysis

Risk analysis stabilises the project by addressing uncertainty early.

Typical risk categories:

• legacy constraints
• regulatory requirements
• conflicting stakeholder expectations
• dependencies across teams
• unclear data availability
• vendor performance
• unrealistic timelines
• resource bottlenecks

Why teams often skip risk analysis:

• desire to start quickly
• fear of appearing negative
• assumption that issues can be handled later
• missing systematic approach

Most later crises are early risks that were never addressed.

7. Communication Logic – “Communication Is Unlikely”

Communication does not work automatically. By default, communication tends to fail unless it is deliberately engineered.

Reasons communication fails:

• different backgrounds and mental models
• inconsistent terminology
• fragmented information
• time pressure
• selective listening
• assumptions and implicit expectations

Therefore, communication must be structured:

• clear messages
• shared vocabulary
• repeated reinforcement
• adapted detail level for each audience
• one source of truth
• simple escalation paths

Without deliberate communication design, misunderstandings accumulate and slow down the project.

8. Communication During Execution – Rhythm, Structure, and Standardisation

Communication becomes operational during execution and must be defined and enforced by the project manager.

1) Establishing a Regular Communication Rhythm

Define predictable routines:

• weekly team meetings
• weekly or bi-weekly workstream check-ins
• bi-weekly steering committees
• monthly stakeholder updates

Consistency prevents surprises and ensures alignment.

2) Defining Communication Methods

Clarify how communication occurs:

• synchronous vs. asynchronous
• written vs. verbal
• dashboards vs. narrative reports
• summary vs. detail
• escalation channels

Standard methods reduce friction.

3) Standardising Status Reporting

Workstreams must not report in different formats. The project manager defines a single template covering:

• progress
• achievements
• risks
• issues
• decisions required
• next steps
• dependencies
• timeline status

Uniformity enables fast consolidation and transparency.

4) Standardising Planning Artifacts

Planning must follow a unified structure:

• same terminology
• same level of detail
• same milestone logic
• same dependency categories

Consistent formats allow synthesis into a coherent master plan.

5) Purpose of Communication Standardisation

Effective communication during execution ensures:

• comprehensive overview
• comparability across workstreams
• early detection of risks
• faster decision-making
• reduced ambiguity
• reliable steering

Standardisation increases clarity and control without limiting creativity.

9. Why the Initiation Phase Is the Hardest Phase of the Project

The initiation phase requires exceptionally broad skills under high pressure. It is often described as the “Superman/Superwoman phase” of project management.

Reasons for its difficulty

1) Multiple activities in parallel

Goal definition, stakeholder analysis, scope, risks, communication design, and structure-building all occur simultaneously.

2) Extreme time pressure

Stakeholders expect momentum, yet clarity requires time.

3) No established team

The project manager frequently works alone:

• no roles
• no routines
• no execution support

4) Incomplete and inconsistent information

Requirements and expectations may conflict or be unclear.

5) Political dynamics

Stakeholders try to influence scope and direction.

6) Mistakes multiply later

Gaps in initiation become costly during execution.

10. Integration of Management Techniques

11. Summary

Key principles of management techniques:

• Projects fail early, not late.
• Clarity is more valuable than speed.
• Purpose strengthens resilience.
• Stakeholder alignment prevents conflict.
• Risk analysis prevents escalation.
• Communication must be designed and standardised.
• Initiation is the hardest phase — execution becomes easier when structure is strong.
• Professional project managers think before they act.