1. Home
  2. Docs
  3. People Ops
  4. All-Remote Guide

All-Remote Guide


Lovia wants to be an all-remote company in order to increase effectiveness and efficiency. (proof that GitLab’s culture works)


GitLab’s Guide to All-Remote [Manifesto]

The Remote Manifesto

All-remote work promotes:

  1. Hiring and working from all over the world instead of from a central location.
  2. Flexible working hours over set working hours.
  3. Writing down and recording knowledge over verbal explanations.
  4. Written down processes over on-the-job training.
  5. Public sharing of information over need-to-know access.
  6. Opening up every document for editing by anyone over top-down control of documents.
  7. Asynchronous communication over synchronous communication.
  8. The results of work over the hours put in.
  9. Formal communication channels over informal communication channels.

Collaboration Tools

As described in GitLab’s All-Remote Handbook, tools should be formalized and be specific with clear purpose and workflow for each tool. These tools are managed by Technology team.

👥 Intranet PortalAbout Lovia
✉ Email (server + webmail + mobile app)Most users use: Gmail Personal setup with forwarder + SMTP (TODO: how to? ask Tech)
Some users use: G Suite
Email domains: @lovia.life / @miluv.app / @soluvas.com
📄 General Documents
📆 Calendar/Events
G Suite / Google: Calendar + Drive + Docs + Sheets + Slides + FormsGoogle Drive folders must be shared from a G Suite account.
✅ Task ListGeneral tasks: Notion
Proprietary software: GitLab Issues – Lovia | Miluv | Soluvas
Open source software: GitHub – Soluvas
💬 ChatRocket.chatInstall Rocket.chat client on your desktop & mobile device
⚙ General WorkflowCamunda

Department-specific Tools

📈 Google Analytics
Google Search Console
Google Ads
Facebook Business Manager
Google Data Studio
👀 Sales & Marketing Handbook
💲 FinanceZoho Books👀 Finance Handbook

Processes and Continuous Improvement

As an all-remote company, Lovia is also document-intensive. With it comes processes as first-class members of documentation. To make this formal and scalable, we adopt the Camunda BPM life cycle. (yes, this is a meta-process 😎🤘)

(reference: Real-Life BPMN book)

All-Remote Meetings

How can we help?