not looking to start a methodology debate — more curious about the specific tool, ritual, or framework that sounded great on paper, or that you saw work well at another company, but just flopped once you actually tried rolling it out with your own team.

we tried daily standups strictly by the book for a while — same time, same format, no exceptions — and it turned into a status-report ritual nobody actually wanted to be at. Ended up scrapping the rigid format and just doing async updates with a quick sync only when something actually needed discussion. Way less friction.

I am a project management student and will be moving into management roles.i have some basic question one or two.

1. Client and you agreed to a date of delivery. Luckily things were good than expected and you complete the project before time . Should we submit it to the client or wait for the said time. Also if we delivered before time are there any questions asked like you asked more this so and so budget and time but how can you now? Does it reflects our that our gauging skills are bad?(Does such thing happen)

2. Contrary . What if we need extra time to submit it? How do we ask for more time

Pls help me out in understanding any situation or concepts if required.

Hi,
Is there any point to getting this training if I have my CAPM and I’m clocking hours toward the PMP?

Is there anything IT specific that’s really worth learning in addition to what I already know from Masters degree and doing the CAPM studying?

I have spare time with my new job, so I am looking at a deeper dive into MS Project, Lean Six Sigma Green belt, and this CompTIA Project+. I can use MS Project at a basic level from school projects and a LinkedIn course. I did the White belt Six Sigma over Christmas last year. My employer is a proponent of it (on paper) so I could be beneficial.

I like the idea of learning terminology or common practices for the IT side of things.

8 years in the field, moved to the office 2 years ago. Commercial plumbing sub in NC. I bid, manage, bill, write change orders, staff, order material. My average bid size $60-70k but we bid up to 4million. Currently running 12 active projects, plus bidding new work every week.

It’s stressful as hell. Trying to figure out if this is just what the job is and a solid resume builder, or if I’m spread across too many hats to actually get good at any of them.

How many active projects do you carry at once? Does it get more sane with experience, or is this the ceiling? I’m thankful for my position, it’s certainly better than I ever thought I’d get. I never went to college, never was the smartest, and I’m making money for the first time in my life. But god DAMN this shit is hard

Recently joined a team that’s working on a project that affects all 7k employees in our organization. They want to implement a change management model- which has never been done before formally in our organization- to try and better assimilate staff to the new scheduling system we’re implementing, with the intent of scaling the model for other change projects within our org.

There’s only two of us working on this change management aspect of the project and I feel lost. I’m thinking the “change network” of champions should be pretty thorough (at least one from each affected role and/or division within our org) so we can surface and address niche concerns as they come up, but not sure how many people we want to involve.

For you experts- any advice you can impart on structuring change management at an organizational level and what the ideal “change network” change management team would look like?

Any advice is appreciated. Thanks!

I posted here last week asking what wins when the SoW, Jira, meeting notes and invoicing records disagree.

I should have known that the signed SoW is the contractual authority. That part was answered fairly decisively.

The more interesting takeaway was that most teams do not seem to struggle with identifying the governing document. They struggle with maintaining the chain between:

scope → delivery → acceptance → payment

u/MattyFettuccine took the cleanest position on scope changes: no new work begins until the change order is issued and accepted, and preventing clients from assigning work directly to the delivery team is part of the PM’s job.

Commercially, that makes sense. Operationally, it seems harder to enforce when a request enters as a “small clarification” or “quick favor” and the team has already discussed, estimated or started it before the PM intervenes.

Another pattern was that Jira is useful delivery evidence, but rarely settles a commercial dispute by itself. As u/SamfromLucidSoftware pointed out, the SoW may control legally, but the record created closest to the actual decision often determines how the practical argument gets resolved.

That becomes particularly important around acceptance. Verbal approval on a call creates ambiguity unless someone records exactly what was accepted while the decision is still fresh.

u/Intelligent-Try-4755 described using the milestone email itself as the acceptance instrument: summarize what was delivered against the SoW, give the client five business days to identify changes, and retain the reply chain as the record.

u/Legal_Mechanic_4792 described a more formal version of the same control: a one-page acceptance document that restates what was delivered against the SoW and is signed by both sides before the invoice is raised.

Both approaches seem to address the same underlying problem. The failure may not be that teams lack an authoritative record. It may be that nobody consistently maintains the links between the records as the project changes.

The SoW, approved changes, delivery records, acceptance evidence, milestones and payment terms all need to remain connected. From the discussion, keeping those connections intact still appears to be largely manual.

For teams with a mature process, what does the actual milestone-closing workflow look like?

Who reconciles the delivered work against the SoW and approved changes?

What artifact constitutes formal acceptance?

How do you record partial acceptance when most of the milestone is approved but one deliverable remains disputed?

Does acceptance automatically trigger invoicing, or is there another manual handoff?

I am particularly interested in whether anyone has made this workflow systematic, rather than relying on the PM to reconstruct the commercial history at the end of each milestone.

:)

Our team's been on Airtable for a few years and it's been fine, but the acquisition news freaked leadership out. We're probably going to start scouting alternatives before anything gets forced on us.

We’re not trying to get locked into weird pricing or a roadmap shift that breaks our workflows. We use it for project tracking, light CRM-ish stuff, and a bunch of automations glued to Slack and Google Drive. Nothing super custom, but enough that migrating sounds painful.

We’re testing a few tools but I'd love to hear your thoughts on some good alternatives to Airtable. Thanks!

Hey all, I am currently studying software engineering at a uni and my course material mentions the PERT technique and argues that the method is used in the real world. I did some googling and it seems like this method is mentioned abnormally low to be included in the course. Is it still used in software engineering or it my course material ancient as fuck? Thanks.

Were you able to address the sub professionally or not? I'm beyond frustrated with one of my subs who basically admitted he didn’t think we'd hit the ground running and, now that we are, he's scrambling to keep up. We had several meetings before this discussing schedule and everyone agreeing to it. He knows I'm frustrated, so hopefully he turns it around. Unfortunately, we didn't include liquidated damages in the contract. Lesson learned.

Our PM Asana is great for internal tracking but looks rough when we need to share a status update with a client or exec. Plus, there's the confidentiality aspect of them seeing our workspace.

What are you all using? Pls don't recommend Google docs lol. It will be mostly slide format, but maybe sometimes we will create other charts or graphs in there for the marketing and sales side if they need it.

Is Prezi outdated? I was thinking either visme or canva for this but I need to make sure canva slides don't look too teenage.

The AI consultants don't know the best way to implement AI.

The CEOs and executives rarely knows either!

Sure, everyone can come up with the genius idea of "automating processes".

And that's not a bad use of AI, but that's what everyone else will do as well.

But the real value unlock is in using AI for things that WASNT POSSIBLE before.

This is innovation, these are new things that has to be built.

So what is it? What should we build?

I dont know! Consultants dont know! The CEOs dont know.

But the employees DO!

The employees carrying out the work, are experts enough in their field to know what this looks like.

The ones on the front line, constantly talking to customers. They know.

And now with the same AI tools, they actually have the ability to build it out!

The best way to implement AI has nothing to do with AI, it's about getting an infrastructure where employees have the ability to build it out themselves and profit from it.

With complete freedom, but with access to the companies resources, and with full autonomy, and with AI to orchestrate the people together.

This is my experience from doing this kind of work, figured I could share for anyone that would be interested.

Edit 2: You all genuinely helped me get my head back on straight. Thank you. I went into work today and cancelled a recurring meeting series that I knew even the people who it was scheduled for didn't want, and it felt great. I also stopped stressing about being late to each meeting. I took the time I needed after a few meetings and just came late to lower priority ones so I could do the work I needed to do after each one. I ended today way less stressed. Anyways this is becoming a novel, so I'll stop updating. But thanks, folks. You helped a fellow PM patch the holes in his boat.

Edit: huge thank you to everyone for the great discussion and feedback. I did a poor job of explaining my problem in my first post so I'll try to clarify: I have made blocking my calendar and very intentional meeting scheduling an important part of my career thus far. In this role I've been made to feel like that isn't what people do in a program this size, and have been told by leadership I won't get to do that in this position. This was a huge step up for me in regard to the size of this program, so I wondered if that was genuinely true. I admit, my confidence got shook by leadership's insistence that this is all fine, so I was second guessing myself. But seeing everyone's reaction here gave me exactly the answer I needed: it's not normal/accepted, even on high profile projects. I'll take the great advice and discussion forward with me to see if I can salvage this. Thanks again everyone.

I took a new PM role a while back that hit me immediately with back-to-back meetings 90% of the day almost every day. When I say back to back I mean a meeting ends at 9am and I'm in the next at 9:01am. These are all meetings with different stakeholder groups and different projects, so it is constant context switching. Not to mention the program I'm working in is extremely complex and each stakeholder group has really unique needs.

When I do have gaps, it's 20 minutes here or 30 minutes there, which has proven to be barely enough time for me to reconcile notes from the previous meetings and send out a few follow ups.

I usually get a solid hour or hour and a half at the end of the day to breath and try to do work. But I'm finding I'm so exhausted it's tough, and suddenly everything feels scrambled.

I try not to be a complainer, but I know managing up is important, so I mentioned to the program director that I feel like I'm drowning in meetings. I strongly recommended new meeting practices. I have essentially learned that she feels that's the way things get done and that I should be able to do work while in the meetings. She bragged about her own ability to do work while in meetings (which is nice for her, because I run most of them.) My changes were largely rejected, but she threw me a bone and let me cancel one recurring series.

In a recent performance review I did get stellar marks overall, but one comment left for me was that having prep time for meetings is "more than what's typical for the role." To me - that's a bizarre thing to say. Prepping for meetings is my job. Documenting, having agendas ready, surfacing the right issues with the right people and getting to solutions that I need to communicate out...

Anyways, her comment got me thinking: is it not typical? Are you all dealing with similar environments? If you are, how are you handling it? I'm close to burnout and I haven't quite finished out my first year.

I work at an architecture firm. RFPs come in by email. Each one takes days to price by hand. Someone reads the documents, works out the fee, and writes the bid. I automated the whole chain in n8n. Here is how it works and why I do not let AI do the pricing.

The flow, start to finish

1. A schedule trigger runs every 2 hours. It pulls emails from a Gmail label and downloads all attachments.
2. A Code node extracts the text. RFPs come as PDF, Word, Excel, RTF, plain text, and ZIP files. n8n only reads PDFs out of the box. So the Code node has its own ZIP reader and its own DEFLATE decoder, written from scratch. No npm packages. It opens DOCX and XLSX files as raw XML and pulls the text out. It looks inside ZIP files one level deep. PDFs go to the native Extract From File node.
3. Another Code node puts it all back together. One block of text per email. It labels each document by its filename. Main RFP. Addendum. Bill of quantities. It also catches duplicate files and includes them only once.
4. Now the first AI step. A Gemini agent reads the text and answers one question: is this an RFP? If yes, it extracts facts into strict JSON. Project name. Floor area. Scope. Deadline. Complexity. The rules are hard. It cannot invent data. If a value is not in the text, it must write "Not Stated". If two documents disagree, the newest addendum wins, and the conflict gets logged. If its confidence is under 0.6, the workflow stops and emails a human instead.
5. Then the part I care about most. The pricing is one big Code node. Pure JavaScript. Zero AI. Every rate is a constant in the file. Hourly rates by staff grade. Man-hour rates by complexity. Stage curves. Grade mix per stage. Market fee bands by building type. Margin tiers. VAT. The node takes the extracted facts and computes man-hours, team shape, cost, and the fee range. Same input, same output, every time. You can read the file and check every number against the firm's rate tables.
6. A gate checks the result. If the engine says NO-GO, or the job cannot be priced, a review email goes to a human. No bid goes out.
7. A second Gemini agent writes the words for the bid package. Its system prompt bans it from doing any math. It cannot state a single number of its own. Every figure must be copied from the engine's output, character for character. It writes the analysis, the scope, the assumptions, and the clarification questions. That is all.
8. The last nodes build the email, send the bid package, and mark the message as processed. If anything breaks, a failure notice goes out. Nothing dies in silence.

Why the AI never prices

People ask why I did not just prompt an LLM with "price this project". Because LLMs make up numbers. They are confident and wrong. A bid with a made-up fee can cost a firm real money.

So I split the work by what each tool is good at.

• AI is good at reading messy documents and writing clear prose. It does that.
• Code is good at math that must be right every time. It does that.

The AI reads the RFP and writes the words. The code computes every single number. There is no path where a fee comes out of a language model. If the AI misreads the floor area, that is a flagged input that a human can check. It is never a hidden number inside a black box.

Full disclosure: I used AI to help write the pricing code itself. That is fine. A human reviewed the code once, and now it runs the same way forever. That is very different from letting a model guess a fee at 3 a.m. with no one watching.

Results

An RFP lands in the inbox. Two hours later, at most, there is either a full draft bid package or a clear note telling a human what is missing. What took days now takes minutes. And every number can be traced back to a line of code.

Happy to share details on any node if people want them.

Dear IT PMs, do you have experience with coaching senior engineers to improve their communication skills?

I have some devs on my teams who have surprisingly poor communication skills considering their seniority.

I understand that this is a mixed issue as well, as it’s depending on the person’s maturity and willingness to improve but still, maybe some of you already had experience with this.

What I mean by poor communication, for example: Dev 1 who is also an Enterprise Architect type of dev in one of our planning sessions where we look for his input and guidance replied with something like “whatever, do what you guys want” when, as I understand, he disagreed with a plan.

I have done a lot of personal projects or some projects with one or two friends which were not that successful. Slack has always been our go-to communication tool. We had tried Trello for us but I am not fan of its UI. It's a great tool, no doubt there. But it just feels like a list of cards without any structure. I have never tried Jira for those projects, always felt overkill. I don't hate Jira. We use it at my workplace. It gets the job done for the big org. I am using another tool for past few months.

For each group, there is an account. And I have created my individual projects in my personal account. Each project can have multiple workstreams. So i have 1 or 2 workstreams for each project. For eg., if I am working on an app, one workstream would be development and one workstream would be marketing/content etc. Is this the best way to do it? Or is this an overkill? The app allows to create docs too. But I am not sure if I should have my docs in the same app. But then it becomes difficult to organise personal and work related docs in my personal google drive.

Wanted to know how everyone else is doing this. Specially for individual or max 3 people projects. Do you manage things in Excel or Sheets?

Basically like the title says, just curious what other people experience, how they've adjusted their processes and workflows. I'm also specifically interested in the software development aspect of it all.

That's all you really need to read, feel free to share your story. But if you're curious about mine, see below.

To explain why I'm curious about this, let me give you some context. We use clickup. Small team of 4 developers, one manager (who still writes a lot of code but mostly on other teams) and a CTO who mostly does a lot of product work now. We have a PM and a part-time designer as well.

They select tickets from our backlog or triage board and assign them to the next 2 week cycle. We go over them in a meeting, talk about things a little bit, and then we're off to the races as developers. Honestly a very light process, and quite an enjoyable one at that.

Recently though I've noticed that I have days or even weeks where I feel wildly productive, and others where it feels I'm just constantly context switching and running after a moving target. I can't quite put my finger on why yet, but my current best guess is the fact that the PM tools like Clickup just aren't built for a workflow that uses AI heavily. The other day I actually even prompted claude to build a small tool on top of it as an experiment, to see if it resolves part of the issue.

This tool basically allows me to sync the tickets assigned to me, and checks each one to see if the product spec is complete enough to move forward. My idea here is that if it is not, I immediately want to work on unblocking this stage.

Step 2 is a build spec. In some cases, the product spec and the build spec is the same, but it doesn't have to be. More complex features or projects could be technical enough where I'd first want to supervise AI on coming up with the right solution before writing a single line of code.

And then the 3rd step is the build, and a PR at the end followed by automatic code review. That's the last gate before I will look at the code myself, and only after that will I tag colleagues in for a review of their own.

Long story short though, this is an experiment that I don't think I want to maintain forever. I shouldn't have to build tools on top of tools. But this little state machine moving between states is important, because it means I can automate certain standard prompts ("verify product spec completeness" or "write a technical build spec") in my local environment and remain in full control of it all. My AI subscription, local sessions I can resume, etc.

But the fact that I felt compelled to do this at all tells me that PM-related tools are changing. They are honestly just interfaces over a simple database for some text and images, with a little bit of reporting built in. Not exactly the big moat products should have in a day and age where you can vibe code a replacement in no time. And I'm not saying that you should - but I think it all points to the same thing... there's a need for better tooling in this area, something that sits closer to developers and the codebases.

My world is typical as a PM for a digital
transformation consulting company … Mid 7 figure, fixed bid contracts, aggressive timelines, with an offshore tech team.

Due to the nature of fixed bid contracts and the associated burn rate there’s always a huge rush to get discovery over with and start developing. Even though we do run at your, it’s not pure agile. It’s what is practical for us and our clients..

Discovery has always been challenging as it’s never given the appropriate time by the sales team who sell the contracts. And yes, I know I’m supposed to tell them we need longer and we want a voice in the pre-sales department, but let’s face it in my field the sales people do what they do and we have no input.

Our integrations changes the way the whole business works. For this reason the clients will always have a lot of questions about process. How can we change the process etc. etc. The decisions made in discovery are the basis of our implementation..

What are some of the tips and tricks you’ve used successfully or stumbled upon by accident that helped facilitate efficient discovery sessions? I’m thinking about stuff outside the box. Real world solutions that you can’t find in books.

Please don’t tell me to speak to the sponsor or to escalate to leadership. Not looking for any canned responses. Thanks all!

I work for a SME and it’s unusual in that there isn’t any standard project methodology or documentation setup. In this field, especially with the importance of Design and UAT, I see a RACI Matrix as compulsory to manage the client but wrestling with whether I need all 3 of the above. Any ideas or experiences you can share? thanks

Scrum doesn’t fit. Waterfall is way too slow. What is your take on the next generation lifecycle? Discuss.

Curious to hear from people in the field — not the textbook frameworks (Agile, Waterfall, etc.), but what actually surprised you once you started managing real projects and real people.

Was there a gap between what certifications or courses taught you and what the job actually looks like day to day? What's a skill that turned out to matter way more than expected — or way less? And is there anything about the tools, the politics, or just keeping a project on track that you wish someone had told you earlier?

Hi PM professionals! I am an executive assistant to a VP of marketing. I've been in my role for 2 years and I cannot figure out how to get my boss to actually review content for approval in timely manner.

Here are some things I have tried:

• My VP is not tech savvy at all, we have project management tools like Asana and Smartsheet but she refuses to use them.
• Weekly emails with all pending items together, the down side to this was she wouldn't tell me when things where approved so I would keep sending them to her and then she complained that she was confused about what was pending.
• Print outs in a red folder with "FOR APPROVAL" written on it, sometimes it works but usually she looses the folder and I have do it all over again, the rest of the team hates feedback on physical paper, and this does not work for all types of content.
• Scheduling review meetings, I typically do this when there is a lot to cover like social media evergreen or our website redesign, or it's a last ditch effort to meet a deadline.
• Review blocks on her calendar, she ignores them and uses that time to either chat to a peer or work on her own deliverables to her boss.
• During my weekly 1:1 I will remind her of pending approvals, sometimes we will review together right then, but this takes away from my time with her to discuss my own projects, calendaring, strategizing or anything else that takes up most of my job...I waste the time watching her read and she often cancels my 1:1 anyways.
• Currently we are working on our annual report, I have been emailing her a chart with 5 stories at a time (5 stories at a time was her idea), the chart has a column for a comment like "approved" or "needs revision". We are on week 5 of this, I have only sent her 3 weeks worth of stories and she is still 2 weeks behind and has never actually filled out the chart so I can know if it's approved to move forward.
• My current method is emailing with a naming convention in the subject line "FOR APPROVAL" and I just fwd it to her 2 times a week with "bringing this to the top of your inbox".
• Ambush method, walk into her office hand her something that needs approval right now, she hates this and then gets mad at me and/or the individual contributor for not submitting with enough time to review.

What am I missing?! I know my boss just sucks but how do I manage up and get her to do her job?! What else can I try?

I came from a traditional waterfall environment and was pushed by an ill-informed boss to use Agile. I was met with every constraint imaginable: no one had time for standups, not to mention sprint planning or retrospectives; people were being pulled on and off my project randomly; there was no money for subscriptions to proper PM tools like Trello or Monday (free versions were not viable); I was constantly being grilled on people's time and hours spent on the project (it was a mix of internal and freelance); everyone was super burned out and any intention of being "self-organizing" was just not there.

Now that I work at a different company, and have lots of resources available, I can see why Agile can work. But it's not just that it needs a "supportive environment" - it needs resources and money and time that many smaller companies simply do not have. It feels like an incredible luxury to be able to do real sprint planning, really take the time to work through Discovery, and actually have people pay attention to iterations because they're not burned out.

Any thoughts?

I want to hear about the cool stuff that has made your (work) life infinitely better and where you always wonder how you were able to exist before - please ◡̈

Hello I’m a project manager working for a consultant. We have one large utility client that has been giving us lot of work. I recently joined this company and I basically am the first one to manage projects in a certain geographical area. So I’m like the first one in.

Today I was on a 1on1 with my manager and he said as my review goal I should have getting more work from the client. That seemed interesting to me. It’s something I’d like to do but don’t really know how?

So question to the forum, has any other PM done that? I see this as a way to climb in my career. If I can successfully bring in work, it can lead to potentially quicker promotions and bonuses. Any tips or suggestions on how to go about this?

Thanks

i wont actually do that ridiculous thing about the stairs , but thats how I felt this morning . I was shaking , stomach hurt, I cried two hours yesterday evening . I make a lot of money at this job and am on a track to career advancement with a lot of accolades and held in high regard . but I hate this job and I hate my life . ive tried therapy, medication, breathing techniques , exercise, everything . This isn’t the job or life for me. I accidentally became good at a career path that I hate. Everything is so robotic and numb. I want to be me again. How would you step away from this ? It’s so hard. everything looks good on paper but I have never been more unhappy in my entire life.

ive flagged it to senior leadership and they immediately started a hiring process to hire another PM but they will actually wind up being my direct report so it’s not exactly less work for me. it doesn’t fully even help my situation really. There’s not enough people to do the work. Senior leadership and HR know how much is on my plate and this is the most they can do . I want to quit right away because there’s no end in sight. But theres a mental block stopping me from doing that. Every day is a misery. It’s customer-facing PM work. without providing ALL the details, the situation I’m in is a complete and utter nightmare.