Successful engineers know how to negotiate within the constraints of the project management triangle: adjust the project scope, optimize the timeline, and allocate resources effectively
This is an interesting method, I have definitely been the shy engineer most of my career, I should have a chance to negotiate soon, so I can report back
I find the negotiation actually builds trust. If you always say yes, no matter if you can realistically achieve it or not, then that "yes" is not too credible (depends on your success/failure record)
But being someone who is known to push back when things are not feasible, then when you commit to something people will trust you'll deliver it!
From my experience it's a process to get confidence. And the only way to become confident is having a track record of experiences where you negotiate and find the best solution!
Yeah, I think in my early days I was afraid to say no in case I didn't seem like I could deliver, but with time I have come to realise people prefer an accurate answer to just "yes".
Yeah I agree, the best way to overcome impostor syndrome is to have done it so many times you aren't phased
And also it's fine when you don't know something and say that you don't know! If you don't give any answer at all, people will worry (in the absence of information, people imagine the worst possible outcome).
it's typical in my work to give DFAD (dates for a date). You don't know how much time it will take, but you commit to take a look and come back to the person later. So you give a DFAD for Friday, it means you'll provide the real date on Friday :)
Nice one Fran! I would add as a negotiation point to highlight potencial impact towards tech debt and how that could affect the triangle of upcoming projects. 🙏
How do you negotiate if the other party only insists on meeting their constraints and doesn't budget and inch inspite of all logical arguments being provided to them ?
Escalation might also backfire if it comes across as too aggressive, or if higher mgmt is also obstinate. Allowing ourselves to be setup to fail isn't an option either.
How would you deal with this type of situation Fran ?
Breaking down the requirements into smaller ones and their prioritization as must-to-have and nice-to-have are crucial.
Great article, Fran!
Not all requirements are created equal! :)
This is an interesting method, I have definitely been the shy engineer most of my career, I should have a chance to negotiate soon, so I can report back
I find the negotiation actually builds trust. If you always say yes, no matter if you can realistically achieve it or not, then that "yes" is not too credible (depends on your success/failure record)
But being someone who is known to push back when things are not feasible, then when you commit to something people will trust you'll deliver it!
From my experience it's a process to get confidence. And the only way to become confident is having a track record of experiences where you negotiate and find the best solution!
Yeah, I think in my early days I was afraid to say no in case I didn't seem like I could deliver, but with time I have come to realise people prefer an accurate answer to just "yes".
Yeah I agree, the best way to overcome impostor syndrome is to have done it so many times you aren't phased
Yes!!
And also it's fine when you don't know something and say that you don't know! If you don't give any answer at all, people will worry (in the absence of information, people imagine the worst possible outcome).
it's typical in my work to give DFAD (dates for a date). You don't know how much time it will take, but you commit to take a look and come back to the person later. So you give a DFAD for Friday, it means you'll provide the real date on Friday :)
People know then what to expect!
Yeah, I had learn to say when I don't know a long time ago,
I haven't done DFAD, so the idea is that by Friday you will have a better estimate in mind?
Yes, exactly. If you leave people saying only "I"ll get back to you", they don't know if it's in 1 day or 1 week.
if you give a DFAD(or DFD - date for date, I have seen both acronyms), you are managing expectations and they know when they can expect to hear back.
Most times people won't complain about the date you provide, but they'll feel uneasy if they don't know what ot expect!
Yeah this makes so much sense, you are giving them some clarity, thanks for the tip!
Nice one Fran! I would add as a negotiation point to highlight potencial impact towards tech debt and how that could affect the triangle of upcoming projects. 🙏
That's a fair point, Alejandro!
We can't be so short-term sighted that we impact the future capacity of the team because of tech debt
How do you negotiate if the other party only insists on meeting their constraints and doesn't budget and inch inspite of all logical arguments being provided to them ?
Escalation might also backfire if it comes across as too aggressive, or if higher mgmt is also obstinate. Allowing ourselves to be setup to fail isn't an option either.
How would you deal with this type of situation Fran ?
Great read, Thanks!