7 ms·

Your handbook says you track work daily in Asana and have two stand ups. Along with an expectation to immediately respond to pings and vacation pre-approval is

by xfitm3 8y ago

Your handbook says you track work daily in Asana and have two stand ups. Along with an expectation to immediately respond to pings and vacation pre-approval is required. How does that fit into “work when you want”?

znq 8y ago
With freedom, comes responsibility. There needs to be some communication and information/knowledge exchange, otherwise it's difficult to coordinate and synchronize in a team of 20 people. Therefore updating other people via Slack/Asana is the minimum anyone should do in my opinion. The two weekly stand-ups, one is actually work related (the team meeting) and people are encouraged to be there and not go surfing just during that specific hour and the other one is the MJ Weekly, where we just exchange personal and professional learnings for about 1 hour, which is a great way to get to know other people being a remote company. That said, making those things "required" is not that bad compared to requiring people sitting 8 hours in an office. Again, my personal opinion.
wgerard 8y ago
I don't work there, but it seems pretty clear to me. Morning slack message (which isn't the same thing as a standup): "Hey, I'm going to do X,Y,Z today but I'm also going to run a few errands after lunch so I'll be MIA from 12-2 CET but available after until 6 CET". "Work when you want" doesn't have to mean "I have no idea when you'll be available today".
- verelo 8y ago
  > "Work when you want" doesn't have to mean "I have no idea when you'll be available today". People confuse the two all the time! Flexibility and reliability have to go hand in hand, if you cannot be reliable when left unsupervised, you need to expect I cannot leave you unsupervised. On the plus side, when people are given this explanation they often self manage into a good routine.
  - 1337biz 8y ago
    But this is the problem. The current mindset is - as long as you are here, I trust you to do something productive. The work-when-you-want is easily leading to a - show me the evidence on why I should trust you to have done something productive today. It forces someone to just push for quick wins and avoid anything that is not leading to directly accountible results.
    - wgerard 8y ago
      You should really know what you're doing all day. If you can't even summarize what you were doing all day, that sounds like a bad thing. The evidence is your story about what you actually did. Here's a perfectly great update that didn't result in a quick win: "I spent all day debugging that null pointer issue like we discussed. I thought maybe it was because the API was sending nulls across, but I looked at the logs and couldn't find any instance of that happening. I thought maybe it was a type coercion issue too, but I wrote a few tests to rule that out and it turned out not to be the case. Then I remembered reading about a memory corruption issue that sometimes happens in our runtime version, so I spent the rest of the day reading about the situations where that occurs and figuring out if it applies to us, but didn't get enough time to finish that up completely."
      - 1337biz 8y ago
        That's the thing - this works only when you have clearly task - solution based jobs. But when it is more creative and abstract this is not feasable.
        wool_gather 8y ago
        You should still be able to recount what you did, past tense. "This morning I sketched out three different possibilities for the new client check-in service. First draft of the spec is in progress, I expect to send it over to Jen and Andy tomorrow for their feedback." "I made a dozen or so mockups for the new landing page. I have a couple more ideas I want to try out tomorrow, then I'll figure out what the best four or five are and show them to the team." "Since we don't have any feature work pending right now, I've been experimenting on a branch with using $TOOL to do $THING better. It looks good because $X, although $Y might be a problem." "We talked a while ago about doing $THING with the user's documents so they can $WHATEVER more easily, and I wasn't sure it was even possible. I've been looking into that today. It looks like there might be a way, so I'm continuing to investigate." "We've wanted to replace $FRAMEWORK for a while now. I've identified the parts of it that we actually use, and I'm putting together a plan for what we can swap in and/or get rid of. It looks like, since we made $CHANGE last month, we can actually do most of it ourselves without much trouble."
- tywheatley 8y ago
  this seems only one degree removed from a 9-5. "work when you want" to me requires more than that. multiply your simple example to 2-4x a week, xN employees, that's a lot of noise

by xfitm3 8y ago

znq 8y ago

With freedom, comes responsibility. There needs to be some communication and information/knowledge exchange, otherwise it's difficult to coordinate and synchronize in a team of 20 people. Therefore updating other people via Slack/Asana is the minimum anyone should do in my opinion. The two weekly stand-ups, one is actually work related (the team meeting) and people are encouraged to be there and not go surfing just during that specific hour and the other one is the MJ Weekly, where we just exchange personal and professional learnings for about 1 hour, which is a great way to get to know other people being a remote company. That said, making those things "required" is not that bad compared to requiring people sitting 8 hours in an office. Again, my personal opinion.

wgerard 8y ago

I don't work there, but it seems pretty clear to me. Morning slack message (which isn't the same thing as a standup): "Hey, I'm going to do X,Y,Z today but I'm also going to run a few errands after lunch so I'll be MIA from 12-2 CET but available after until 6 CET". "Work when you want" doesn't have to mean "I have no idea when you'll be available today".

verelo 8y ago
> "Work when you want" doesn't have to mean "I have no idea when you'll be available today". People confuse the two all the time! Flexibility and reliability have to go hand in hand, if you cannot be reliable when left unsupervised, you need to expect I cannot leave you unsupervised. On the plus side, when people are given this explanation they often self manage into a good routine.
- 1337biz 8y ago
  But this is the problem. The current mindset is - as long as you are here, I trust you to do something productive. The work-when-you-want is easily leading to a - show me the evidence on why I should trust you to have done something productive today. It forces someone to just push for quick wins and avoid anything that is not leading to directly accountible results.
  - wgerard 8y ago
    You should really know what you're doing all day. If you can't even summarize what you were doing all day, that sounds like a bad thing. The evidence is your story about what you actually did. Here's a perfectly great update that didn't result in a quick win: "I spent all day debugging that null pointer issue like we discussed. I thought maybe it was because the API was sending nulls across, but I looked at the logs and couldn't find any instance of that happening. I thought maybe it was a type coercion issue too, but I wrote a few tests to rule that out and it turned out not to be the case. Then I remembered reading about a memory corruption issue that sometimes happens in our runtime version, so I spent the rest of the day reading about the situations where that occurs and figuring out if it applies to us, but didn't get enough time to finish that up completely."
    - 1337biz 8y ago
      That's the thing - this works only when you have clearly task - solution based jobs. But when it is more creative and abstract this is not feasable.
      - wool_gather 8y ago
        You should still be able to recount what you did, past tense. "This morning I sketched out three different possibilities for the new client check-in service. First draft of the spec is in progress, I expect to send it over to Jen and Andy tomorrow for their feedback." "I made a dozen or so mockups for the new landing page. I have a couple more ideas I want to try out tomorrow, then I'll figure out what the best four or five are and show them to the team." "Since we don't have any feature work pending right now, I've been experimenting on a branch with using $TOOL to do $THING better. It looks good because $X, although $Y might be a problem." "We talked a while ago about doing $THING with the user's documents so they can $WHATEVER more easily, and I wasn't sure it was even possible. I've been looking into that today. It looks like there might be a way, so I'm continuing to investigate." "We've wanted to replace $FRAMEWORK for a while now. I've identified the parts of it that we actually use, and I'm putting together a plan for what we can swap in and/or get rid of. It looks like, since we made $CHANGE last month, we can actually do most of it ourselves without much trouble."
tywheatley 8y ago
this seems only one degree removed from a 9-5. "work when you want" to me requires more than that. multiply your simple example to 2-4x a week, xN employees, that's a lot of noise