Detailing of alteration work around existing conditions requires careful consideration of said existing conditions - not even the best detailer can just whip out a pen and sketch a detail off the top of his head, and the time required for research is very dependent on the quality of information provided about the existing conditions.
When it's already afternoon on Wednesday, assigning someone 60+ hours of work to be done "by the end of the week" creates certain potential difficulties.
When someone mentions to you that he has just been assigned 60+ hours of work to complete in the next 20 working hours, dropping one 1-hour item, claiming one other item "can't possibly take that long", and advising him to prioritize and reduce distractions doesn't really solve the problem.
Telling someone he should only spend 1/2 hour each on the items he was just assigned directly by YOUR boss, the SVP, to try and save a sinking major project might, just might, have some repercussions...
Chad Miller
Sep 29, 22 3:43 pm
phase of project is expected to take 300 hours based on the fee
only one person is scheduled / able to work on the project phase 50% of the time
adding one fresh grad to assist you with the work will not enable said phase to be completed in 3 weeks.
Chad Miller
Sep 29, 22 3:49 pm
It's probably not a good idea to go after a project when:
The client is known for only caring about the cost
The client doesn't actually know much about the building type
The clients owners rep doesn't actually know much about the building type
The owners rep doesn't understand that doing design build with a guaranteed maximum price doesn't actually save the owner any money
The owners rep is vague to the point of dishonesty
Stasis
Sep 29, 22 6:39 pm
Good topic even though the OP provided more of complains rather than actual pro tips. Venting is fine, but it's also good to brainstorm together how we can improve the project management at our workplace. Here are some of my suggestions.
Clear Work Plan Management on both sides - PM should create a work plan mapping out the work hours for each team members for next 3-4 weeks. Then, PM to go over the work plans on a recurring weekly call with the team members to set the expectation. On the flip site, team members need to review the work plan and provide feedbacks to the PM on weekly basis. They cannot just wait for the half of the week and suddenly there are too much work for them. It takes two to Tango and two way communications can avoid working 60 hours a week. If a PM originally assigned 20 hours on a given week and suddenly ask you to do 60 hours in the middle of the week, then you can definitely push back for not doing his job on planning and execution. I believe there are two sides to every story.
Pay attention to SOW and Fee Proposals. Both PMs and team members review carefully what they are selling on a proposal - Scope, Resources, Schedule, etc. Once the proposal is accepted by the client, then the project resource is pretty much set. You cannot come back later saying that you need another 200 hours, unless there is a legitimate ground for a CO. If scope is unclear or complicated with the existing building conditions, then make sure to add disclaimers in the proposal, so you can cover yourself. Lack of As-built drawings can be a good reason that you can push back on a client and ask for more hours.
Be upfront about your weekly workload - If you run into issues and problems meeting the timeline, Be proactive and bring it up to the PM or line managers at the beginning of the week. This is one reason why a weekly team call is very important to forecast any workload and potential bottle necks. Sometimes firms have multiple deadlines in a week. Team members can use that time for their advantages too. Give a PM the maximum time and availability per given week and anything more than that will need to be picked up a week after. Draw a line in the sand early on, so that you wouldn't get ambushed by additional works. I went back many time to my supervisors that I have competing priorities and ask them to help me what to focus on. This sometimes led to PMs fight with each other for my time, but in the end, it helps me to sort out the workload on that week.
Chad Miller
Sep 29, 22 6:47 pm
The short version of above: clearlycommunicate with everyone on your team.
Also I think the OP was using the thread to vent. ;)
Stasis
Sep 29, 22 6:59 pm
Thanks Chad, that's exactly the point. you can't assume another person understands what you are going through on weekly basis.
Stasis
Sep 29, 22 8:34 pm
Also, one needs to be proactive in communicating clearly. I'd say also leave everything in writings, so you can point later that 'I told you so'..
atelier nobody
Sep 30, 22 1:05 pm
Yes, of course I was venting and my examples were quite specific to my current situation, but naming the thread as I did was only about half tongue-in-cheek - I actually do think the specific examples are instructive and representative of broadly applicable principles I really wish management understood.
atelier nobody
Sep 30, 22 1:07 pm
Also, I agree wholeheartedly with almost all of the points both of you have added - keep it up.
sameolddoctor
Sep 30, 22 1:37 pm
Another pro tip for PMs:
- One of your basic responsibilities is to be the essential "membrane" between the client and the design team. Your job is to take client's demands, evaluate them against the time/capability of your team and THEN lay it upon your team. The "you heard what the client wants" excuse is lame and stupid.
It's probably not a good idea to go after a project when:
Good topic even though the OP provided more of complains rather than actual pro tips. Venting is fine, but it's also good to brainstorm together how we can improve the project management at our workplace. Here are some of my suggestions.
The short version of above: clearly communicate with everyone on your team.
Also I think the OP was using the thread to vent. ;)
Thanks Chad, that's exactly the point. you can't assume another person understands what you are going through on weekly basis.
Also, one needs to be proactive in communicating clearly. I'd say also leave everything in writings, so you can point later that 'I told you so'..
Yes, of course I was venting and my examples were quite specific to my current situation, but naming the thread as I did was only about half tongue-in-cheek - I actually do think the specific examples are instructive and representative of broadly applicable principles I really wish management understood.
Also, I agree wholeheartedly with almost all of the points both of you have added - keep it up.
Another pro tip for PMs:
- One of your basic responsibilities is to be the essential "membrane" between the client and the design team. Your job is to take client's demands, evaluate them against the time/capability of your team and THEN lay it upon your team. The "you heard what the client wants" excuse is lame and stupid.