Timeline for How can I politely tell a fellow contractor that I'm very disappointed in the effort he's put into an assigned task?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 24, 2018 at 14:28 | comment | added | Andrew | "I think it's incredibly important for him to hear that you think he is capable of the work, but you need him to deliver on time and write good code." Could you please add some dialogue options to iterate how such a conversation would go? Especially in the context of a daily stand-up where each person has to explain what they've done. I've already spoken to him about these things, but perhaps I didn't do it the "right" way. | |
| Oct 22, 2018 at 20:30 | comment | added | Chris Stratton | Breaking things down can work sometimes; but it can also be micro-managing in a way that impedes efficient progress, especially if the fine breakdown chosen in advance doesn't turn out to fit how the system being developed actually needs to be put together (which in many cases it will not). To an extent, getting a daily report of what was tried may better fit a complex process pursued by a probably quite experienced resource most likely very capable of finding paths to solutions independently, but who isn't currently doing a good job of persistently digging into those tasks. | |
| Oct 22, 2018 at 18:34 | comment | added | jcmack | @MaigenThomas +1 That's a great suggestion! | |
| Oct 22, 2018 at 18:15 | comment | added | Maigen Thomas | Would also suggest assigning some tasks / breaking down things into 'chunks' of work as deliverables and creating due dates for each deliverable. | |
| Oct 22, 2018 at 18:02 | history | answered | jcmack | CC BY-SA 4.0 |