Timeline for How do you expose your need for team interaction without sounding like a slacker?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 26, 2014 at 11:05 | comment | added | Aaron Digulla | @RemcoGerlich: +1 That's an important point which I completely missed :-) | |
| Mar 26, 2014 at 10:39 | comment | added | ravemir | Nice answer and comments. Also, yesterday I found out a document I partially wrote back in January might actually be useful again, as someone managed to convince my manager to take an approach I proposed to him back in January. Finally, finding someone who wants to take this with me might be challenging on my environment, but it's definitely a good idea. | |
| Mar 25, 2014 at 20:57 | comment | added | RemcoGerlich | I agree 100% with your assumptions, and I'd add to the list of things he can do: actually kickstart the project. Find out who actually wants this project and why, and make those people your "team mates" (just talk to them every chance you get). Think of what would really need to be done to get the project off the ground, and get them in motion. Write down more than you normally would so you have documentation to point at. At worst you may find out why it's necessary to start with documenting stuff. | |
| Mar 25, 2014 at 16:55 | history | answered | Aaron Digulla | CC BY-SA 3.0 |