In a project a few years ago I had for my agency to create very short notice an offer for a site. The management of the customer had us against the will des Projektteams ins Boot geholt, und ich wusste, dass der Projektleiter auf Kundenseite alles tun würde um uns draußen zu halten (das Projekt endete übrigens genauso krank wie es begonnen hatte, aber das ist eine andere Geschichte...)
Interessanterweise war der Projektleiter nicht komplett unkooperativ. Er setzte eine verbindliche und recht knappe Timeline zur Abgabe des Angebots, Verzug hätte bedeutet dass das Angebot nicht berücksichtigt würde (denn er selber hatte von seinem Management ebenfalls ein knappes Timing für das Gesamtprojekt bekommen). Im Gegenzug hat er uns mit Material zum Angebot geradezu zugekippt und mehrfach nachgefragt ob er denn auch wirklich alle Unterstützung geleistet hat die we need - what we had to confirm in writing. In fact, we were able to accomplish in the time the information is not at all.
He gave us a maximum of this strategy under pressure without making themselves vulnerable. If it subsequently emerged that he has blocked, possibly a second round of bidding the result would have been. You could learn from this: Even in less-charged situations you could get used to as an IT project manager to let all participants a minimum of degrees of freedom, but share the same dates and limits (which also applies to the education of children, if the relevant Literature Guides believe must pay. My children, however, can not read yet):
Example 1: It depends on the project on the supply of materials or releases of the client. , in any case in advance a time limit to keep but not too tight! If the customer fails to comply with them and pointed out that it was ridiculously short, you have very little leverage. Iron insistence on meaningless Time Lines is a service not very good to see. If the customer does not meet the deadline to respond in any case, otherwise the question is to what for the time limit is there, if allowed to pass without consequences.
Example 2: You have to work on customer service with a second (because of the design and makes the own agency, the technical implementation). It is the same as in Example 1, it should also provide for appropriate dates transfers and bug fixes to the customer in case of trouble the other service providers do not even have to take under his protection. In particular, problems of cooperation (not complied with transfers) are not notified too late to the customer. That falls under "the court keep clean," I come back to it in a later post.
a period not to share signaled customers and other project participants, moreover, that the delivery can be in doubt, one day before the deadline. And rightly so.
0 comments:
Post a Comment