5 ms·
I started a new role 2 weeks ago. My general strategy: * Read all the things. For me as a technical writer that means reading most if not all the docs on our d
by kaycebasques 4y ago
I started a new role 2 weeks ago. My general strategy:
* Read all the things. For me as a technical writer that means reading most if not all the docs on our documentation website. Also means org strategy docs. Also means doing a lot of tinkering (try out the code samples etc).
* Record first impressions / friction log as I go. Beginner's mind has real value!
* Meet & greet everyone on my immediate team (~20 people) for 30 mins. More focused on work stuff.
* Also meet & greet people in the wider org (~10 people) for 15 mins. This meeting is less focused on work stuff. I'm approaching it with the mindset that it's plain nice to meet new people. But I'm sure the "rapport building" will also make work easier eventually.
* Talk w/ manager and skip manager about medium/long-term projects and eventually get written confirmation via email. My manager has a very helpful framework where you think of 3 levels of projects. First level is immediate value (what the post calls "easy wins"). Second level is medium-term with substantial complexity (these will take lots of meetings and research to find the right problem/solution to work on). Third level are stretch projects that will eventually get you promoted (if that's what you want).
* All the mandatory corp onboarding stuff. Benefits, mandatory training, etc. Just block out focus time and get it done.
* We don't have an onboarding guide for our immediate team so I'm creating one as I go. Will be a nice way to connect with any new teammates after me.
- daniel-cussen 4y agoDid your boss try to get you to read things on your own time? If the work requires reading something, it has to pay me to read it. If it's my own time, for my own benefit, reading for free, flat-out cannot read anything other than the Bible, which I haven't finished. And if your boss doesn't like it he can literally go to hell. Which is both more and less metaphorical than is widely believed.
- solveit 4y agoThis comment is terrific even though I'm not sure I quite agree with the sentiment. Upvoted.
- loloquwowndueo 4y agoWhen I onboard someone I fully expect them to spend a good chunk of their first days / few weeks reading and not being tremendously productive - absolutely within working hours.
- kaycebasques 4y agoNope, I am not expected to read work stuff outside of working hours.
- honkler 4y ago
- jimmont 4y agoDuring the first 2 to 6 weeks on a job (it probably varies more than this) most corporate US environments expect significant amount of time to go to processing/onboarding. When providing status updates in meetings just state as much, usually with little to no specifics. I've yet to see anyone respond at all within the first month. What's remarkable to me is the amount of overhead/cost associated with these institutional mechanics, despite tools like Workday, which frankly I don't see as actually being effective. Staff counts of 2 and more (in addition to the new person) with these tools still can't manage to communicate with new staff where to go, where to send equipment, etc which reveals a significant need in the market.
- daniel-cussen 4y agoYeah a Stanford professor told me you need 6 months to be productive in a coder job. 3 months, others have said. To pull your weight, and then pull more than your weight. Of course where I've worked the firing threats start on day 1, and they obviously expected (Unholster for one) that I work at home. Those guys wanted the whole install to be done at the end of day 1.
- deleted 4y ago[deleted]