While more companies are going fully remote, nearly all of them have been forced to consider the potential that remote working can have for the health and safety of their team.
Our founder, Irma, has been working remotely since 2017. Here's how she successfully handled bringing her boss on board with the idea:
Taking your first step towards remote work.
I was working for a company in Miami and wanted to move. But, I didn’t just want to quit my job because I valued the people I worked with and the impact I was making. So, I sat down one day and started researching remote work. Who were the big companies working remotely? How were they making it work for them?
Step 1. Take a look at your responsibilities.
You first need to make sure that your role is a great fit for remote working. When I was transitioning, I was a Product Manager and I knew that my work could easily be done over Slack for async communication, through tools for face to face video calls, and platforms to track engineering and design work.
If you'd like to have a coffee chat about your current responsibilities and whether they could be suitable for remote work, email/DM them to me and I can work with you on figuring that out.
Step 2. Reflect on the impact you’ve had at the company.
The more value you’ve provided to your team before pitching to go remote, the easier it will be. Let’s say, for example, you’re always the leader on your team that picks up those “not fun” projects or tasks that nobody else wants. That makes you memorable and people (your boss) will notice your proactive attitude. Think about this like when you negotiate a raise at your company, since you’re essentially listing out the major impacts you’ve had on your team’s performance.
Step 3. Find your biggest “why” or motivator pushing you to work remotely.
The one question your boss or manager will ask you, is why? Why do you want to leave your in-office team to go work from home? This reason will differ from person to person. Maybe it’s more time with your kids or the cost of living being better suited in a different city. The most important thing to remember is that you convey that you still want to work for them.
Struggling on your why? Reach out via email/DM. Lets schedule a coffee chat.
Step 4. Draw up a plan that will make working remotely work for you.
This is where you’ll want to map out the pros, the cons, where you’ll work remotely, how flexible your schedule will be, your communication plan with your team, software tools you’ll use to work/communicate, the equipment you have to enable you to work from home, and any equipment you’ll need to work with your company to buy.
Step 5. Schedule a meeting with your boss.
For me, I looped my CTO and CEO into a 45-minute meeting but it could be different for you. Leading up to the meeting you may want to create a pitch deck (I did).
Step 6. Go fully remote! (Or experiment with a trial period).
Depending on how the meeting went with your boss or manager, it’s time to start planning the date you’ll either go fully remote or the date you’ll start experimenting with a few WFH days during the week.
This process may seem scary or nerve-wracking but the worst your leadership team can say is “no” or “let’s give it a shot by starting with 1 WFH day a week and take it from there”.
If you're just looking to go remote check out this article (www.meetcafecito.com/posts/how-to-find-remote-software-development-roles)