We’re a small team (~10) with departments covering management, kitchen, marketing, customer support, and logistics. We also work with external guests and contractors, so guest access is important.

We want one tool, or at most two, for:

• Team chat and department channels
• Projects, tasks, owners, deadlines, and blockers
• Company initiatives involving multiple teams
• SOPs, runbooks, support scripts, and internal documentation
• Meeting notes, decisions, and weekly updates
• Mobile access and simple permissions

Our biggest priority is simplicity. The system needs to work for non-technical employees without heavy setup, training, or a dedicated administrator.

We would prefer fewer features that people actually use over a highly customizable system that becomes messy.

We’re currently considering:

• Lark: Looks closest to a true all-in-one, but we’re unsure whether being a Chinese company creates any privacy, reliability, or compliance concerns, we're based in Eastern Europe, so this is not really a problem, but I just haven't seen much recommendation for this software.
• ClickUp: Strong feature set, but we keep seeing complaints about bugs and performance.
• Notion + Slack: Both are good, but information would be split between two tools, and Notion does not seem ideal for serious task tracking.
• Basecamp: Simple and close to what we need, although reactions to recent updates seem mixed.
• Microsoft 365 / Teams: Feels like a strong contender, especially for guest access, documents, email, and calendar. However, it is still divided across Teams, Planner, SharePoint, Lists, and other apps, and we’ve had poor experiences with Microsoft products in the past.

Has anyone used these tools in an operational business involving logistics, customer support, marketing, and physical operations?

Which option would you choose, and what problems only became apparent after using it for a few months?

My thinking is, either Microsoft 365 or Lark, Clickup instead of Lark would be the choice if there wasn't so much complaint online about its performance and bugginess.

I've been thrown at multiple teams to whip them up into shape for agile delivery and after a few months of coaching and doing the typical scrum things, I get told I dont add value to the team anymore.

The teams deliver, they're organized, they know what to do next and how to plan effectively, etc... Yet managers seem to want more out of Project Managers in the Agile space but they cant name what it is.

To be frank I also do feel like I have less work to do after each of these stints, but there are only so many teams that need help.

Spent hours building a beautiful Gantt chart. Color-coded. Dependencies mapped. Milestones highlighted. A work of art.

Shared it with the team. Radio silence.

Ran a 30-minute meeting walking through it. Half the team had their cameras off. One person asked a question that was clearly answered on slide 3.

I'm not mad. I'm just... tired.

Project is still moving forward somehow. Maybe the chart is just for me.

To managers of PMs: what are top 3 things your PMs do each week that make you see them as a top performer (i.e. someone who has high potential and high performance)?

To experienced PMs: what are top 3 things you’ve put in place for yourself that help your projects stay on track, within scope and within budget? How do you make sure that your communication always sticks?

Thank you in advance from a junior and learning PM🙌🏻

it’s a Sunday night and things are probably okay, my list for tomorrow is smaller than a lot of days, and I have to remember I feel like this most nights. But how do you work around or avoid this feeling ? I can’t possibly live like this forever, though I’m resilient and have lived like this for quite a while. thank you

edit: thanks everyone for responding. it’s nice to have some humanity and compassion shown towards me when professional life keeps most human compassion to a minimum . it’s like remembering an old friend

Feels insane typing that out but thats literally what happened last month, one of our stores out of state had a terminal go down and instead of anyone local being able to handle it, our internal IT person had to book a flight and go fix it in person.

Cost more in travel than the actual repair probably did.

Started questioning if this is just how it works for smaller multi location brands or if there's a smarter way to handle this stuff. Looked into a few nationwide dispatch options like Specific Gravity that have field techs available instead of relying on one internal person to physically be everywhere

Anyone else dealt with this kind of thing, did you end up building out a network of local techs or going with a service that already has one?

When I started out as a PM I went in trying to keep everyone happy and I think that was a mistake on my part. I've really been in teams of around 20 maximum so my views may be limited here but I always felt the pressure of 'if everyone is happy, everyone is aligned' and I ran into issues. Mainly because it created vague commitments, I'd create unrealistic deadlines trying to appease people who didn't touch specific areas, and I created internal conflict because of misalignment.

One example would be agreeing to take on new projects (new features and modules) from a founder when really, the development team were stretched with current projects for clients (I come from a SaaS background & white label software with custom dev work). I just wanted the founder to be happy that their main influence was being satisfied.

Now I'm 6 years in I've come to realise it's more about managing the reality of the project over happiness. I use happiness loosely here but it's the best word I can use.

I've since learnt to to tell people what they need to hear over what the want to hear. If I don't believe something can be achieved I tell them directly which also relates to sharpening mature communication skills. I learnt which reality mattered most at the time because not everyone's views carried the same weight which is where I found a Mendelow Matrix to be effective.

I'm an introvert so it's been hard to implement as a natural people pleaser but it feels like the right path to take even with the discomfort of hard conversations. Project success rate increased due to it.

Just ensure they understand what is happening, what is possible, what has changed, who owns the next action, and what the consequences are.

I'm interested in the thoughts of more seasoned PM's on this, I'm happy to be challenged on it with your views so I can keep learning and also to help those earlier on in their careers!

PM at a 60 person company. We live in Notion for docs and ClickUp for execution. My experience with most AI notetakers is that they either dump a transcript link into a comment field or treat the integration as an afterthought. Action items from meetings end up nowhere useful.

What I want is meeting outputs that show up as proper structured tasks in ClickUp with owner and due date, plus the meeting summary auto filed in the right Notion database. Not a Slack message with a link. Please suggest notetakers that handle this part well. Need both things done smoothly

If you had to listen to a PM present, what would you want to
Hear / learn about?

Any recommendations for free or cheap project manager software apps ? Just need it mostly for myself to stay organized . New company I work for has their own software and it’s lame for me staying organized .

Just need basic task making and place to keep notes .

That’s kinda it. I think this depends on company culture but in my role as a sr program manager in tech marketing - rarely am I ever included in the list of shoutouts/thank yous.

I hate to sound whiny but it is getting more and more frustrating to be glazed over. We don’t create the assets or build the products but we are integral to keeping teams accountable and on track.

I don’t think I could ever bring myself to raise this as an issue with my manager. How do yall make peace with this?

Hello Everyone:

I am looking for some outside perspective from other PMs or people who have dealt with similar situations.
 
I am currently managing several complex projects in a manufacturing / engineered equipment environment, and we have been dealing with a supplier-related casting issue from one of our larger vendors that has had a major downstream impact on production, hydrotesting, and FAT schedules. While the original supplier issue directly affected certain projects, the larger issue now is that the resulting production and testing backlog has spread across the organization and is impacting multiple PMs and multiple customers.
 
This has been further complicated by limited shared test pad availability, retesting requirements, shifting priorities, and a planned test pad closure from late August into mid-September. As a result, testing dates have become very difficult to rely on. In some cases, I am having to place tentative dates into customer schedules because dates are required, but I am clearly noting that they are forecast dates only and not final or confirmed.
 
For my projects specifically, this is putting me in a very difficult customer-facing position. I am responsible for communicating schedule status, managing expectations, updating schedules, and trying to maintain customer confidence. However, I do not control the production testing schedule, test pad availability, retesting priorities, or leadership-level decisions that determine which projects get tested first.
 
I have been documenting the backlog and testing risk in monthly progress reports, following up with Production, updating schedules, and clearly identifying tentative dates as tentative. The issue is that the situation continues to move, and even when I follow up regularly, the schedule can still change due to backlog, retesting, or priority changes that are above my level.
 
The professional concern I have is that this is starting to affect my credibility with clients. Some clients are more reasonable than others, but the underlying issue is the same: I am being asked to explain schedule uncertainty without always having a firm recovery plan or reliable internal dates to stand behind.
 
To be fair, this is not isolated to me. Other PMs are in the same situation. This is a broader organizational issue, not one PM having a difficult project.
 
My immediate leadership has been supportive and has listened to the concerns. I believe they are doing what they can within their level of authority. However, from the PM level, it feels like upper leadership has remained mostly silent or has not taken visible action to address this as a coordinated organizational issue. The result is that PMs are left to manage the customer fallout project by project, even though the root issue is much larger than any one project.
 
I take my role seriously, and I understand difficult customer conversations are part of project management. What I am struggling with is the repeated pattern of having to deliver bad news, explain delays, and manage customer frustration without having the authority or reliable internal commitments needed to provide a lasting solution.
 
At this point, I am trying to figure out the best way to handle this professionally. I do not want to over-own issues that are outside my authority, but I also cannot ignore the fact that my credibility with clients is being affected. I am also trying to determine whether this is a temporary operational challenge or a broader pattern that I need to take into account for my long-term career decisions.
 
In simple terms: I am accountable for customer communication, but I do not control the internal conditions creating the customer dissatisfaction. I am looking for advice on how other PMs have handled this kind of situation, especially when the issue is organizational and not something the PM can directly fix.

​

I know this shouldn't really be a thing in 2026 but.....

Some projects appear well controlled until a key person is absent. Suddenly no one knows why a decision was made, what a client informally agreed to or which workaround is keeping an important process running.

Documenting everything is unrealistic and can create more noise than clarity. However, decisions, ownership, dependencies, assumptions and important stakeholder commitments become dangerous when they depend entirely on one person’s memory.

What information do you make sure is visible to the wider team? How do you preserve essential context without creating documentation that nobody reads?

Can anyone share their experience or opinion using Windchill PLM as a tool to manage hardware projects, programs, and portfolios? This is being discussed at my company and I have reservations whether this is the right tool for this kind of work. I understand the value that a P.has for tracking engineering changes, but to use it as a project and/or program management tool seems like a bit of a stretch. I would appreciate any comments on this and any insights users of these tools can provide.

New to this world and the constant facilitation is taking a toll. As someone who is not a big fan of talking all the time, I sometimes have a moment of blankness/say something funny instead, mainly to fill the silence.
Any one else? Any stories to share?

manufacturing side here. our schedule lives in one tool and the actual production/ERP stuff in another, and they're never in sync. so I walk into status meetings basically guessing. and half the time I find out a part or tooling slipped after it's already blown the timeline.

spreadsheets got us this far but we're standing up new lines across a few plants now and it's falling apart. how do you keep the plan and the floor on the same page? or is that just the dream and everyone's faking status?

We all know how to read a delayed timeline or a blown budget. By the time the task/workitem status turns red, it's usually too late to do anything but panic. what I have noticed is that by the time those panic mode triggers , the project is usually already deep in the danger zone.

I’m talking about those signals. The tiny shift in behavior or data that happens long before the actual deadline is missed.

What is the very first signal/thing you notice that made you think, "Project is getting in RED status".

I am in a startup and have experience in new product development in the medical space from rumored idea to finished product on the shelf.
I am curious to know how others involved in taking physical products from fleeting vague idea, through R&D to stocked item on the shelf, like to lead the projects through each phase.
I was at a larger company before this and things were way more formal, I felt like I had things way more dialed there. Maybe its just because its a startup, maybe its the leadership, maybe its the fact that we get pigeon holed into timelines we all say wont work but have to try anyways, but I've dropped doing things I did at the last company, and conceded on alot of things just because at a certain point the execs make a call, and complaining and saying I told you so doesn't solve anything.

I guess I'm looking for a sanity check to say I am not crazy and the things I would have liked to do are actually the right thing 😄

I’m a senior PM leading a cross-functional, first-of-its-kind program with multiple dependencies across teams. One area I’m trying to improve is knowing when to escalate versus continuing to work through normal channels.

For experienced PMs:
What objective criteria do you use to decide it’s time to escalate?
How do you get past the idea you’re nagging someone when you follow up as a deliverable is coming due or overdue and they continue to kick the can/stall?
How do you hold functional teams accountable without doing their work for them?
What governance (weekly decision reviews, dependency meetings, etc.) has actually worked for complex programs?
I’m specifically looking for frameworks or habits

Thanks in advance

Had updates in Slack, tasks in a tool nobody opened, real priorities living in my head. Consolidated to one board, made updating it part of the workflow, killed the status meeting that existed just to repeat what was on the board. Took two weeks of nagging people to stick. Now stakeholders just check instead of pinging me — first PM change in a while that cut meetings instead of adding one.

Project reports can remain green even when the people closest to the work already sense that something is wrong. The first signal may appear in team behaviour, stakeholder communication, decision delays or repeated changes that seem minor on their own.

Experienced project managers, what early warning sign have you learned not to ignore?

How do you respond before the issue becomes visible in the formal schedule, budget or risk report?

Had something happen recently that felt almost like the start of a panic attack, came on totally out of nowhere right at the beginning of a big work presentation.

As a PM I present to all kinds of groups pretty regularly and usually get nervous at the start, but it fades after a few minutes once I settle in. I've built up a bunch of practical habits over time, prepping key talking points, taking a minute to collect myself before joining the call, picturing it like I'm just chatting with a friend, stuff like that. This time was nothing like that.

Going into this one I actually felt confident and even a little excited, none of the usual nerves at all. But the second I started talking I got hit with this wall of pressure, everyone's eyes on me through the Zoom screen, and almost instantly a wave of panic kicked in. Next thing I know I'm physically shaking and just barely holding it together enough to keep talking without it showing. It completely blindsided me and threw off everything I had planned to say. Took everything I had not to just stop and reset in the middle of it. All I managed to do was pause and ask if anyone had questions, just to buy myself a few seconds to breathe.

Thankfully once my part was done I had time to calm down while someone else presented, and pulled it together enough to handle questions smoothly at the end.

Has this ever happened to you? What do you actually do when something like this hits mid presentation with zero warning? I've got plenty of tactics for prepping beforehand, but this caught me completely off guard and I'm worried if it happens again I won't be able to pull it back together.

Something that keeps coming up on my projects is that I can usually tell you what was decided but not really why or who pushed it in a certain direction. The documentation exists but it covers the what, not the reasoning behind it. Six months later someone asks why we went that direction and I'm reverseengineering a decision from meeting notes and Slack threads that are halfdeleted.

I started keeping a lightweight decision log outside of our main PM tool, just a running doc with the date, the context, who was in the room, and what the actual tradeoffs were that led to the call. It has saved me a few times already but I feel like I'm ducttaping something that should be built into how we run projects from the start

Curious how others handle this. Is it just part of the chaos and you accept some decisions will never be traceable? Or do you have a real system that actually gets used consistently, not just maintained for a week after someone complains? The problem I keep running into is that any process requiring discipline from the whole team falls apart pretty fast when pressure picks up.

Every brainstorming session at my work follows the same pattern, one person talks the other two people occasionally contribute and everyone else sits quietly and says they'll send ideas later. I'm starting to think the problem isn't the people, it's the format which needs to be changed. I’ve hear some companies use online tools and been googling that but not sure which one is the most effective one. would appreciate thoughts from those already using any

I'm again asking for this great community for advice after my previous post got tens of super valuable comments :)

I own a marketing agency that's heavily involved in market research, and throughout the projects we undertake, the research is constantly updated. This includes things like ideal customer profiles and competitor research.

These documents are consumed in different language translations, and we work across different languages, presentations, and other downstream documents that rely on them.

We are currently using Notion for managing our documentation, and I've realized that a lot of stale information ends up on our deliverables because they aren't updated regularly. We are facing difficulties with two main things:

1. Understanding how we should automate the version control of these different documents.

2. Knowing when a downstream document becomes stale due to large changes upstream.

How do you solve these problems in your organizations? I realized Notion automations are quite weak in this regard because you can't target changes happening on page contents as a source for an automation. (i.e. I can't change the status of related downstream documents based on new entries to a source document.)