Re: Should I or shouldn't I?

[Anonymous]

Hi GameGuy……..I spent almost my entire career in an office environment driving teams, and it sounds (if I got this right) like there is an administrative disconnect somewhere within your team, or it’s process(s), not an ADD issue?? If indeed you are not receiving your work “at all”, or receiving it, after the due dates….. that to me is a mechanical or process delivery issue. As team member I too believed my ownership was appropriate, but when others within the team, or a team process/system are problematic….that’s not a personal problem…..that’s typically a process issue, and that needs to be illuminated and addressed as such. I understand the disconnect, and that disconnect should not be a direct reflection on you, but…you seem to be the recipient !!! I have to say…… if you were on my team…….. you have identified an issue, or shortcoming in our “work process”….GOOD FOR YOU………well done!!

So What Next …

In most cases for me, at this juncture, it would be appropriate to raise the issue of the “project notification” process’s shortcomings, and it’s impact, on the customer, and the team productivity. I would be mindful to do it in a non-blaming/non-defensive way….these things usually require a bit of a sell job. I would be sure the principal players were ALL in attendance, and present not only the issue but a ‘potential viable solution” as well. Note….when presenting an issue….I found issues were best received when accompanied by a solution, plus… a tangible list of the benefits the solution will deliver. Providing a solution has a way of keeping the overall perception of the delivery positive!!! So GG as I see it… the issue (boiled down) is to present the issue and a solution to the “project notification” shortfall, both of which will better serve the goals of the team, and the needs of the customer???

Just my thoughts……..hope it helps.

toofat

REPORT ABUSE