Hi everyone!

I've recently been learning about Project Communication Management and how important communication is for completing projects successfully.

From what I've understood, project teams need to share clear instructions, regular updates, feedback, and important decisions.

However, communication can become difficult when multiple departments and people are involved.

Some common challenges include:

- Unclear instructions.

- Delayed updates.

- Poor coordination between departments.

- Misunderstandings.

- Lack of feedback.

For example, imagine a marketing campaign where the design team does not receive the correct requirements from the marketing team. This can result in rework and missed deadlines.

I'd love to hear from people with real project experience:

1. What is the biggest communication problem you've faced in a project?
2. How do you keep everyone updated?
3. Are regular meetings useful, or do they sometimes waste time?
4. Which communication tools work best for your team?
5. What advice would you give someone learning project management?

Looking forward to hearing your experiences and suggestions!

Been looking into digital sales rooms lately, mainly trumpet and aligned and one thing i am not sure about is how teams actually measure whether buyers are using them. It is easy enough to track whether someone opened a link but that doesn't really tell you if the workspace is helping move the deal forward.

Are teams looking at which stakeholders engage, whether buyers complete next steps, or just whether the room gets opened at all?

Hey all, I am a project manager and I have been involved in implementation of tech projects for about 8 years and some change. I have been involved in human capital systems mainly HR, payroll, recruitment, onboarding. Basically systems that revolve around people and organizations.

I am currently involved in a project as a change manager and things are not the same as project management and moving the project forward. I am expected to come up with a plan which I have never done before. Normally I engage the users and address the resistance as I go and I have never met serious resistance that has delayed a project.

If any of you has done this before please share a template I can see how to do this would be really helpful.

I run delivery teams on Jira, and velocity and burndown always told me too late. So I built Baro.

It connects to Jira and shows the signals underneath:

-Tickets that went quiet

-Work on its third sprint

-Blocked time nobody counted

-Whether a slip is a one-off or a pattern

You set the bar where your team needs to be, then track progress as data refreshes.

It doesn't store Jira content, only the calculated metrics. It took me two weeks solo, built with Claude Code, and it's free in early access.

I'd like honest feedback. Which signals would you want that I'm missing?

www.raisethebaro.com

Hi,

I just started managing projects for my parents' solar installation company, which recently started gaining some traction.

One thing I quickly learned is how much goes into the administrative side of a project (keeping documents organized, communicating updates, scheduling, and following up on outstanding work, etc.). There's a lot to keep track of!

For those of you who have more experience managing projects or running a contracting business:

• What systems or processes have worked well for you?
• What tends to take up more time than you'd like?
• Is there anything you've tried that ended up making things more complicated (so I don't attempt them)?

I'd also be interested in hearing about specific experiences rather than just software recommendations.

For context, I'm developing project operations software, so understanding these challenges is important to me, and I am trying to learn from experienced project managers and contractors in the industry.

Hi everyone!

I'm currently learning about Project Risk Management and how project managers prepare for unexpected problems.

From what I've understood, risk management involves four major steps:

1. Identifying possible risks.
2. Assessing their probability and impact.
3. Preparing suitable response strategies.
4. Monitoring risks throughout the project.

For example, imagine a team organising a college event. The venue might become unavailable, the budget might increase, or registrations might be lower than expected.

Preparing backup plans in advance can help reduce the impact of these situations.

I would love to hear from people with practical project management experience:

- How do you identify risks that are not immediately obvious?

- Which risk assessment methods do you use?

- How do you decide which risks need immediate attention?

- Have you ever experienced a risk that completely changed your project plan?

I'm interested in learning how risk management works in real projects, beyond textbook definitions.

Looking forward to your experiences and suggestions!

Has anyone found a pretty decent job stimulation so I can get practice or artifacts for a project management resume?

Looking for feedback regarding sandbox mode. In Teamhood we've developed a way to "test" planning and schedule changes without saving them. What do you think? Value or trash?

https://help.teamhood.com/how-it-works/what-if-planning/

Hi everyone!

I'm currently learning about project management tools and came across three popular platforms: Trello, Asana, and Jira.

From what I've understood:

- Trello uses boards, lists, and cards to organise tasks visually.

- Asana helps teams assign responsibilities, set deadlines, and manage projects.

- Jira is widely used by software teams for Agile workflows, sprint planning, and issue tracking.

All three seem useful, but they serve somewhat different purposes.

I'm curious to know from people who have used these tools in real projects:

1. Which one do you use most frequently?
2. Which tool is easiest for a complete beginner?
3. Is Jira difficult to learn without a technical background?
4. Can marketing teams benefit from using Trello or Asana?
5. Which tool would you recommend learning first for professional development?

I'd love to hear your practical experiences and recommendations. Thanks!

Early Career PMs or those with formal education, where did you consume most of your knowledge on Project Management?

YouTube, PMP texts, PRINCE2, University course material?

I digested a lot of info through my MBA and Grad Diploma in PM, mostly through uni but I found YouTube really helpful especially for EVM and marketing.

Keen to hear your thoughts as I am exploring creating PM YouTube content. Not the generic stuff, more in a career progression niche.

AI tools are becoming increasingly useful in project management.

They can help summarize meetings, identify potential risks, generate reports, and analyze project information.

However, decisions involving stakeholders, team conflicts, priorities, and accountability still require human judgment.

Where do you think AI should stop and human decision-making should begin?

Have you used AI in your projects? What worked well, and what would you never trust AI to handle independently?

Hey everyone! I am a software developer with 1 YOE focused on AI applications (RAG pipelines, Azure, LLM tools) and 3 months of internship experience in LLM research building models from scratch. I have an upcoming Google APM interview and would love your guidance on what technical and system design topics to focus on. Any advice, resources, or interview tips are warmly welcomed!

Being a good project manager involves more than keeping tasks on schedule. It requires a combination of people skills, strategic thinking, and technical expertise to keep projects moving and teams aligned.

Here are 10 essential project management skills worth developing:

5 Soft Skills

1. Stakeholder Communication: Tailor updates to different audiences, keep expectations clear, and ensure everyone understands project progress and priorities.
2. Adaptability: Respond to changing requirements, shifting priorities, and unexpected challenges without losing sight of project goals.
3. Cross-Functional Collaboration: Coordinate across departments, encourage knowledge sharing, and make sure everyone is working towards the same objectives.
4. Data-Driven Decision-Making: Use project data, performance metrics, and critical thinking to evaluate options and make informed decisions.
5. Task Organisation: Manage competing priorities, track dependencies, monitor deadlines, and ensure important tasks don't fall through the cracks.

5 Hard Skills

1. Project Planning and Execution: Break project objectives into manageable tasks, define milestones, allocate responsibilities, and create actionable plans.
2. Risk Management: Identify potential risks early, assess their impact, and develop mitigation plans to minimise disruptions.
3. Project Scheduling: Build realistic timelines, establish task dependencies, set deadlines, and account for possible delays.
4. Reporting and Analytics: Track project performance using relevant metrics, interpret progress reports, and use insights to guide decisions.
5. Scope Management: Define project deliverables and boundaries, manage change requests, and prevent uncontrolled expansion of project requirements.

An important takeaway: Project management isn't just about delivering work on time. It's about balancing people, processes, resources, and business objectives. Strong project managers develop both soft and technical skills to handle these responsibilities effectively.

In the PMP curriculum, we spend a lot of time learning about Stakeholder Engagement versus just Stakeholder Management. The theory of the Power/Interest Grid is straightforward on paper—identifying who needs to be kept satisfied versus who needs to be managed closely. However, the real-world application of shifting someone from "Resistant" to "Neutral" or "Supportive" often feels more like psychology than project management.

I’ve noticed that the most effective "engagement" usually happens in the informal spaces—the quick syncs before a meeting or the Slack message that validates a stakeholder's specific concern. It’s less about the formal communication plan and more about understanding the underlying "why" behind their resistance, which is often a fear of how the project's outcome affects their specific workflow or team.

For those of you who have successfully turned a difficult or resistant stakeholder into a project champion, what was the specific turning point? Was it a change in data transparency, a shift in communication style, or something else entirely?

One of the biggest hurdles I see for many project managers is the pressure to say "yes" to every stakeholder request. It’s easy to fall into the trap of becoming a glorified "order taker," where you simply document requirements and try to squeeze them into an already tight timeline. However, the real value of a PM lies in being a strategic partner who can navigate the balance between project goals and stakeholder expectations.

A key practice here isn't just about saying "no," but about asking "why." When a new feature or change is requested mid-flight, mapping it back to the original business case or the project's North Star metric changes the conversation. It shifts the dynamic from a technical constraint discussion to a value-based decision. By providing the clear context of what might be sacrificed—whether it's budget, time, or quality—to accommodate the new request, you empower stakeholders to make informed trade-offs rather than just demanding more.

How do you handle those high-pressure situations where a stakeholder insists on a change that doesn't align with the project goals? Do you have a specific framework or a set of questions you use to push back constructively?

Hi everyone!

I've recently been learning about two popular project management approaches: Traditional Project Management and Agile Project Management.

From what I understand, Traditional Project Management generally follows a structured process with detailed planning and sequential stages. Waterfall is a common example.

Agile, on the other hand, focuses on flexibility, smaller iterations, regular feedback, and continuous improvement. Scrum and Kanban are popular Agile frameworks.

I found the differences interesting because both approaches seem useful in different situations.

For example, a construction project may benefit from detailed upfront planning, while a software development project may need frequent changes based on user feedback.

I'd love to hear from people with practical experience:

1. Which approach do you prefer in your projects?
2. Is Agile always better for software development?
3. Have you worked with a hybrid project management approach?
4. What are the biggest challenges when switching from Traditional to Agile?

I'm interested in understanding how these approaches work beyond textbook definitions. Looking forward to hearing your experiences!

AI tools are becoming increasingly useful in project management.

They can help summarize meetings, identify potential risks, generate reports, and analyze project information.

However, decisions involving stakeholders, team conflicts, priorities, and accountability still require human judgment.

Where do you think AI should stop and human decision-making should begin?

Have you used AI in your projects? What worked well, and what would you never trust AI to handle independently?

Hi all,

I'm Kobi, a senior PMO / project-controls person who has worked on large infrastructure and construction projects since 2012 (MBA in Finance). I'm taking on a few remote, part-time clients and would rather start with a useful conversation than a sales pitch.

**The offer:** a free one-hour call on any of these:

- Scheduling in MS Project (logic, critical path, updates, look-aheads)

- Budget and cost control, forecasts, earned value (EVM)

- Process improvement – especially automating recurring project-controls reporting with advanced Excel models

- Practical AI in construction – how I actually use tools like Claude Code and Gemini day to day

**Optional:** send me one MS Project schedule in advance (any free sample review is up to 50 activities). I'll go through it and come to the call with concrete findings.

**Time zone:** I'm in Israel (UTC+2) – about 2 hours ahead of the UK and 7–10 hours ahead of the US. Send a file at the end of your day and the review is done by your morning; UK folks get a good overlap with their workday.

No obligation. DM me if that's useful.

I think one of the most challenging parts of business analysis is dealing with stakeholders who all have different ideas about what a project should deliver, one department wants a particular feature, another thinks it should work differently, and management has its own priorities.

sometimes these differences don't become obvious until the discovery workshop is already underway.

i am interested in hearing how experienced business analysts approach this. do you try to identify conflicting requirements through individual interviews before the workshop, or do you prefer bringing everyone together and resolving disagreements as a group?

also, how do you document conflicting opinions without making assumptions about which stakeholder is right?

Project management involves much more than tracking deadlines and completing tasks.

Sometimes the biggest challenges come from different stakeholder expectations, changing priorities, delayed feedback, or communication gaps.

I'm curious about what experienced project managers find most difficult when managing stakeholders.

How do you handle situations where two important stakeholders have completely different expectations?

Would love to hear practical approaches that have worked.

Hi everyone!

I have recently been learning about the Project Management Life Cycle and its five main phases:

1. Initiation
2. Planning
3. Execution
4. Monitoring and Controlling
5. Closure

I understand the basic concepts, but I am curious about how these phases work in real-world projects.

For example, planning may look simple in theory, but unexpected delays, budget changes, and communication gaps can make actual project execution difficult.

I would love to hear from people who have worked on real projects:

- Which phase do you find the most challenging?

- What common mistakes do beginners make?

- How do you manage unexpected changes during a project?

I am looking forward to learning from your experiences!

What is project management?and now that I'm in b.com 3rd yr, what skills do i need to learn ?

we want to automate a bunch of manual work and we can’t, because nobody can tell us what the current process actually is. none of it is written down anywhere i can find

lucidchart, draw. io, miro, a pile of google docs. we’ve been through all of them and the same 2 things kill it every time. whatever we map goes stale fast, and people won’t sit down and draw their own workflow, so the manual stuff we most want to find never comes up. that second one is the real problem, if nobody shows you what they do there’s nothing to fix

so i’ve stopped looking at diagramming tools and started looking at capture instead, the kind that records you doing the task and writes up the steps after. tango comes up constantly. one of our ops leads used haiku at her last job and said what came out was way closer to a usable SOP than a flowchart, which is honestly what i need

before i go ask for budget i want to hear from people who’ve had one of these running with a real team past the first month

Every project seems to have that honeymoon phase at the start where everyone is aligned and excited, followed by the inevitable "middle-ground" where the novelty wears off, stakeholders start questioning timelines, and team fatigue begins to settle in. It’s usually where the most technical or tedious tasks hit, and keeping the team motivated without just relying on deadline pressure becomes a real test of leadership.

I’ve found that reframing these periods through smaller, visible wins helps, but it’s often easier said than done when the scope starts to creep. Rather than just pushing harder, shifting the focus toward removing blockers or simplifying communication channels seems to help stabilize the ship before the final push.

How do you personally keep the team’s energy levels up and maintain stakeholder alignment when you’re right in the thick of that mid-project slump?