Come to the office, pass your germs around for the sake of having lunch with the team and risk everyone being unwell
Firstly, it's not just for the sake of a lunch. As I mentioned, it's a day when all the DEV, Product, and Design teams come together for collaboration. We work on large-scale products that involve various teams in design, management, and development.
Additionally, our junior members don't learn remotely; they shadow senior members to learn. If they encounter difficulties, have questions, or blockers, they can easily seek help by approaching their mentors directly. This direct interaction fosters strong team dynamics, mentorship, and learning.
Moreover, we utilise our digital white boards where we brainstorm ideas.
If you're unwell, call in sick. Taking care of your health is important. Rest up, relax, and return when you're fully recovered.
WFH, maybe miss out on some potential collaboration but spend seven hours chipping away at the to-do list, getting deadline work over the line, or catching up on admin.
They have 4 other days to do that.
Call in sick, even though you're more than capable of putting in a day's work. Cost your company money, cost yourself money if you're on SSP, negatively impact productivity, risk impacting project timelines
We work in sprints using the Agile methodology, which means we have contingencies in place for situations where team members might be unwell.
Our DEV teams are quite large, so work can easily be reassigned.
I don't see how having a sick employee could possibly improve productivity; it sounds counterintuitive to me. Allowing someone to work while they're unwell risks mistakes and suboptimal work.
Statutory Sick Pay isn't a major concern for us. I'd much rather my team members take the time they need to rest and recover fully. Considering the value of just one feature, which is typically worth over £250k, SSP is insignificant for us.