Comprehensive Guide to Digital Project Management Fundamentals

• Current Role: Digital Project Manager.

• Experience Duration: Almost $5$ years in the industry.

• Career Progression: Started as a Project Assistant around $2020$ or $2021$. Following a period in this role, the speaker was promoted to Project Manager.

• Specialization: Focuses on managing digital assets, specifically for platforms like social media (Instagram, Reels, etc.). Deliverables include:

  • Videos.

  • Display ads.

  • Teasers.

    Speaker Profile and Career Evolution

• Background: The speaker entered the field during the $COVID-19$ pandemic. Initially, they had no specific intention of becoming a Project Manager ($PM$) and had little prior knowledge of the role's requirements. They joined the company "Dataword" (referred to by the speaker as Data words).

Professional Training and Certifications

• External Certifications: The speaker currently does not hold external professional certifications.

• Internal Training: The company provides robust internal training programs to shape management approaches, including:

  • Service Excellence Training.

  • Advanced Service Excellence Training.

  • Client Negotiation Training.

The Nature of IT Project Management

• Technical vs. Non-Technical: While the role of a $PM$ does not require active coding or programming, a $PM$ must understand technicalities to communicate effectively with the development team.

• Role as Mediator: The $PM$ acts as a critical link between the client and the technical team. This involves:

  • Assessing client briefs.

  • Performing Quality Assurance ($QA$) on technical assets before delivery.

  • Translating business requirements into technical instructions.

• Project Duration: The speaker primarily handles long-term projects rather than short-term Service Level Agreements ($SLA$) of, for example, $3$ months.

Stakeholder Management and Internal Hierarchy

• Key Internal Stakeholders:

  • Account Manager: Initiates the project and handles the initial proposal to the client.

  • Sales Manager: Involved in financial aspects, such as total cost and budget negotiations.

  • Project Management Director: Oversees the project management department.

  • Team Lead ($TL$): Focuses on people management and supervising the $PM$s.

  • Traffic Manager: A role within the $PM$ function focused on dispatching requests and assessing ticket scopes.

• External/Counterpart Stakeholders: The company headquarters is located in Paris, France. The speaker often collaborates with counterparts in the France office who deal directly with the end clients.

Project Methodology and Management

• Agile Methodology: The speaker utilizes the Agile model for project management because of its inherent flexibility, allowing the team to iterate and return to previous stages if necessary.

• Project Lifecycle Stages:

  • Kickoff: Initial start and alignment.

  • Planning: Organizing resources and schedules.

  • Analysis: Checking master files and identifying elements needed for production.

  • Production/Development: Technical creation of assets.

  • Quality Assurance ($QA$): PM reviews output to ensure alignment with the client brief.

  • Delivery: Final dispatch to the client.

Key Challenges and Negotiation Strategies

• Unexpected Challenges:

  • Tight Deadlines: Handling complex requests within short timeframes (e.g., delivering $100$ videos within $5$ days).

  • Technical Specifications: Unfamiliar or complex specs, such as specific "safe zones" for logos in TV commercials.

• Change Management: Handling change requests without compromising team morale or deadlines.

• Negotiation Tactics:

  • Proposing partial deliveries (delivering a subset of assets first) to satisfy immediate client needs while buying time for the technical team.

  • Negotiating extensions based on the feasibility of the request and resource availability.

  • Issuing "Quality Warnings" if a deadline is so tight it risks the integrity of the final product.

Tools and Technology Ecosystem

• Communication: Microsoft Outlook (client communication), Slack, and Microsoft Teams (internal coordination).

• Task and Ticket Management:

  • Jira: Used for ticketing, dispatching requests, and tracking progress via dashboards (e.g., tasks due today vs. tomorrow).

  • Trello and Asana: Used for general organization and task management.

• Documentation and Scheduling: Google Suite (Google Sheets for trackers, Google Docs), and Gantt charts for monitoring project schedules.

• AI Integration: Use of tools like ChatGPT or Gemini to assist in drafting professional emails and ensuring correct grammar for international clients.

Career Advice for Students

• Communication is Key: Strong communication skills (especially in English) are vital, as much of the job involves writing emails and mediating between parties.

• Leadership and Organization: A successful $PM$ must be organized, a problem solver, and a confident decision-maker.

• Starting Small: Do not be afraid to start as a Project Assistant or Junior $PM$. The learning curve includes onboarding, training, and "shadowing" senior managers.

• Work-Life and Setup: The industry often involves shift work. The speaker's shift is a mid-shift from $02:30$ PM to $11:30$ PM. Many roles are currently hybrid or work-from-home ($WFH$).

Compensation and Market Rates

• Entry Level (Project Assistant/Starter): Approximately $16,000$ PHP to $24,000$ PHP.

• Experienced PM ($5$+ years): Salaries can range from $60,000$ PHP to $90,000$ PHP, with potential to reach six figures depending on company and performance.

Questions & Discussion

• Q: How do you track project progress?

  • A: We use internal weekly meetings and tracker tools like Google Sheets. We categorize tasks as "In Progress," "Under Validation/QA," or "On Hold." Jira dashboards are also used to visualize workload and deadlines.

• Q: What is the difference between a Team Lead ($TL$) and a Project Manager ($PM$)?

  • A: The $TL$ focuses on people management and supervising the group of $PM$s. The $PM$/Senior $PM$ focuses on operational management, traffic management (dispatching), and ensuring specific project delivery.

• Q: How does the workflow start when a client sends a request?

  • A: The request arrives (often via a brief in Excel). The $PM$ assesses the scope (e.g., localization or design). A ticket is created in Jira and dispatched to the technical team. The technical team reviews it for missing information. After development, the $PM$ performs a $QA$ check to ensure the output matches the original brief before final delivery.

• Q: What happens if there are limited resources for a deadline?

  • A: The $PM$ must check the visibility of upcoming requests and the availability of the technical team. If the deadline is not feasible, the $PM$ negotiates with the client for an extension or warns them about potential quality compromises.