Running Remote 2024 took place in Lisbon, Portugal, from April 22–24, 2024. The first day hosted an Enterprise Academy at the Pestana Palace Hotel, followed by the main conference at SUD Lisboa on April 23 and 24. The program brought together leaders working on remote-first, hybrid and distributed organizations.
This article replaces the original pre-event preview with a factual retrospective and an evergreen guide to the operating questions behind the conference: how to design hybrid policies, use asynchronous communication, protect remote access, support employee health and decide whether a workplace event offers practical value.
Running Remote 2024 facts
| Item | Confirmed detail |
|---|---|
| Dates | April 22–24, 2024 |
| City | Lisbon, Portugal |
| Enterprise Academy | April 22 at Pestana Palace Hotel |
| Main conference | April 23–24 at SUD Lisboa |
| Program scale | 28 sessions, 35 speakers and 23 partners in the organizer’s archive |
| Audience | Founders, executives, HR and people leaders, and operators of distributed or hybrid teams |
The organizer’s archive lists speakers from organizations including Atlassian, Google, Mailchimp and Doist. The official attendee guide describes two stages, an event app, livestream access and “Braindate” one-to-one or small-group discussions. Those details are historical records of the 2024 edition; current conference dates, venues and ticket terms should always be checked on the organizer’s live site.
What the 2024 event was designed to address
Running Remote was not a general technology expo. Its focus was management practice for organizations whose work happens across homes, offices, countries and time zones. Conference themes included leadership alignment, company culture, flexible-work policy, asynchronous operations, employee experience, collaboration and the use of AI in workplace systems.
The Enterprise Academy was positioned as a peer-learning program for larger employers integrating on-site, hybrid and distributed work. The main event combined presentations and conversations rather than promising a single universal model. That distinction matters: a two-day-at-home schedule suited to one technology company cannot simply be copied into healthcare, manufacturing or customer-facing services.
One archived session, “Rethinking the Remote Work Narrative,” emphasized that asynchronous work depends on a strong mission, clear values and information that employees can actually find. Async communication is not merely sending more messages at different times; it requires deliberate documentation, decision rights and response expectations.
What research says about hybrid work
A 2024 Nature paper reported a six-month randomized trial involving 1,612 graduate employees at Trip.com. Employees offered two work-from-home days each week had higher job satisfaction and one-third lower quit rates, with no detected harm to performance grades, promotions or lines of code. Managers’ views of productivity became more favorable after the experiment.
That is valuable causal evidence, but it is not proof that every remote or hybrid policy produces the same outcome. The trial involved particular roles, one company, a defined schedule and employees who had passed probation. Results may differ for new hires, jobs requiring physical presence, weak managers or teams without adequate tools and documentation.
Organizations should define the result they want—retention, concentration, access to talent, service coverage or lower real-estate costs—then measure that result. Badge swipes, message counts and webcam presence are activity signals, not reliable substitutes for completed work, quality, customer outcomes or team health.
Build a clear operating model
Remote work becomes confusing when location is the only rule. A workable policy explains which roles are eligible, when physical presence is necessary, how time-zone coverage works, what equipment the company supplies and how employees request adjustments. It should also address travel, tax, employment-law and data-residency constraints with qualified local advice.
Minimum policy components
- Eligibility: role-based criteria applied consistently rather than manager preference alone.
- Location: approved countries or regions and a process for temporary work elsewhere.
- Availability: core collaboration windows, handoff rules and emergency contacts.
- Equipment: ownership, support, replacement, secure disposal and expense reimbursement.
- Performance: expected outcomes, review cadence and promotion criteria.
- Safety: ergonomic assessment, workload, breaks and psychosocial-risk reporting.
The policy should be versioned and searchable. Employees need to know which document controls, when it changed and who can answer exceptions. A buried PDF that conflicts with informal manager instructions creates risk rather than clarity.
Asynchronous communication that actually works
Async-first teams preserve information outside the meeting room. Decisions, owners, deadlines and supporting evidence are recorded in a durable location. Messages include enough context for someone in another time zone to act without starting a long clarification chain.
Use the right channel
| Need | Best default |
|---|---|
| Urgent operational incident | Defined real-time alert and on-call process |
| Decision needing debate | Written proposal followed by a focused meeting if needed |
| Status update | Shared project record with owner and date |
| Reference procedure | Version-controlled documentation |
| Relationship building | Small-group or one-to-one conversation |
| Complex demonstration | Short recording plus searchable written summary |
Response-time norms prevent “asynchronous” from becoming permanent availability. A team can define, for example, that ordinary messages receive a response within one working day while incidents use a separate channel. Quiet hours and notification controls help employees recover from screen-intensive work; our digital-detox guide offers practical boundary-setting ideas.
Meetings should have a job
Distributed teams do not need to eliminate meetings. They need to reserve synchronous time for tasks that benefit from it: resolving ambiguity, making contested decisions, coaching, creative exploration and building trust. Information broadcasts and routine updates are often easier to review asynchronously.
- State the decision or outcome in the invitation.
- Share pre-reading early enough for different time zones.
- Invite only people who contribute or need to decide.
- Assign a facilitator and note-taker.
- Record decisions, owners and deadlines in the shared system.
- Rotate inconvenient times when no schedule is fair to everyone.
For larger online gatherings, accessibility, moderation and platform security require additional planning. See our guide to planning accessible and secure virtual events.
Security for distributed teams
Remote access expands the environments from which company data can be reached. Security should assume that home networks, shared spaces and travel locations are not controlled like an office. That does not mean distrusting employees; it means designing controls that do not depend on a trusted building perimeter.
- Use managed devices, prompt security updates and full-disk encryption.
- Require phishing-resistant multifactor authentication where supported.
- Grant least-privilege access and review it when roles change.
- Protect remote administration behind approved access systems rather than exposing services directly.
- Maintain tested backups and an incident-reporting channel employees can reach when locked out.
- Define rules for public Wi-Fi, confidential calls, printing and storage of sensitive material.
CISA and NIST guidance treats alternate worksites as potentially hostile environments and recommends explicit telework security policies. Employees can reinforce the basics with our home cybersecurity checklist.
Health, ergonomics and psychosocial risk
EU-OSHA guidance says remote-work risk assessment should cover equipment, the physical environment, work organization and psychosocial factors. A laptop at a kitchen table can create neck, back and wrist strain; an always-on culture can create isolation, excessive hours and cognitive overload.
Employers should provide suitable equipment and a process for reporting problems without penalizing the employee. Teams need manageable workloads, breaks, social support and boundaries around surveillance. Monitoring software can produce detailed activity data without showing whether the work is useful, and disproportionate monitoring can undermine trust and create additional psychosocial risk.
Onboarding and career progression
New employees cannot rely on overheard conversations to learn how work gets done. A distributed onboarding plan should identify the first-week setup, essential documentation, role expectations, key relationships and a sequence of increasingly independent tasks. A named onboarding partner can answer routine questions without turning every issue into a meeting with the manager.
Managers should make career criteria visible. Remote employees can be disadvantaged if promotion depends on office visibility or informal access to senior leaders. Review evidence should focus on outcomes, collaboration and skill development using the same standards across locations. Sponsorship, mentoring and stretch assignments need intentional distribution rather than being offered only to people physically nearby.
A practical onboarding record
- Account and equipment checklist with an owner for each dependency.
- Role charter explaining customers, decisions and success measures.
- Team map showing expertise, time zones and escalation routes.
- Thirty-, sixty- and ninety-day outcomes reviewed with the manager.
- Scheduled feedback on the onboarding process itself.
Measure outcomes without creating surveillance
A remote-work dashboard should start with business and workforce outcomes: service levels, quality, cycle time, employee retention, absence, safety reports and customer satisfaction. Segment results carefully to detect unequal effects, but protect privacy and avoid small groups that could identify individuals.
Keyboard activity, online status and screenshots are easy to collect but weak indicators of knowledge work. They can reward visible busyness, encourage people to leave applications open and penalize tasks that require reading, thinking or offline conversation. If monitoring is necessary for security or compliance, explain the purpose, scope, retention period and access controls, and consult workers where required.
Run policy changes as evaluated experiments
Instead of announcing a permanent company-wide rule based on anecdotes, organizations can pilot a clearly defined arrangement with representative teams. Record the baseline, duration, eligible roles, manager training and success criteria. Include both quantitative results and structured employee feedback.
A useful review asks who benefited, who faced new barriers and what supporting practices changed at the same time. If a hybrid pilot adds documentation training and better equipment, outcomes cannot be attributed to location alone. Publish the decision and evidence after the pilot so employees understand whether the policy will continue, change or end.
How to evaluate a remote-work conference
An event is valuable when it helps solve a defined operating problem, not merely because it promises “the future of work.” Before attending, identify two or three questions, review speakers’ practical experience and decide how learning will be shared with the team.
- Separate research findings from vendor case studies and sponsored claims.
- Ask what workforce, geography and time period a success metric covers.
- Prioritize sessions that publish methods, constraints and lessons from failure.
- Schedule a post-event briefing with recommended experiments and owners.
- Measure results after implementation rather than counting contacts or sessions.
Cloud platforms often support distributed operations, but product announcements still need the same scrutiny. Our Google Cloud Next overview provides related context.
Frequently asked questions
When was Running Remote 2024?
The Lisbon event ran April 22–24, 2024. The Enterprise Academy was held April 22, followed by the main conference on April 23 and 24.
Where was it held?
The Enterprise Academy used the Pestana Palace Hotel, while the main conference took place at SUD Lisboa near the Tagus River.
Does research prove remote work is always more productive?
No. A major randomized trial found that a defined hybrid schedule improved retention without harming measured performance in one company. Outcomes depend on role, policy, management, tools and workforce.
Is asynchronous work the same as avoiding meetings?
No. It means information and decisions remain accessible without requiring everyone to be present simultaneously. Meetings remain useful when real-time interaction improves the outcome.
Conclusion
Running Remote 2024 documented an important stage in the shift from emergency home working to deliberate distributed operations. Its most durable lesson is not that every company should become remote-first. It is that location policies work only when they are supported by clear outcomes, documented decisions, secure access, fair management and attention to physical and psychological health. Organizations should test those systems against their own work rather than adopting a conference slogan.
Leave a Reply