Hacker News Reader

Comment by teeray | Hacker News Reader

I think this is something I would schedule to use, which is probably the opposite of the intent here. The worst thing is when a team member reaches out ad-hoc and says “oh hey, do you all have a few minutes to look at X?” The answer is likely “no” for most parts of the day. I have a calendar—book time on it and I will probably accept it. If it’s not on there, it doesn’t exist and I am working on other stuff.

View on HN

As someone who struggles with context switching _and_ who likes to help people out and unstick them, I really feel that you're saying. I need to become more like you in that respect.

I think scheduling a time to talk and using this tool for the convo, is not inherently bad. That said though, at that point just use a Slack Huddle or Teams.

We have found that if flowy is used for you and your core team, and only your core team, then it's a place where you remove the death by thousand cuts, trying to get to someone (pinging to go to a huddle, scheduling for a sync meeting) you already know is your core teammate.

Thoughts?

That's a great point! We have found this for more formal teams at big companies where things move slow. The standard is "email me back by end of week, schedule something this week or next."

Hyperactive teams need their main people (3-8 core people, and everyone has a different set of core people) to be a push of a button away. And this changes from week to week depending on the project and priorities.

Mind if I ask, are you on a team which tends towards longer sprint cycles and more waterfall, slower product development? Maybe your company values quality and stability instead of speed?

Reply on news.ycombinator.com