Designing a Fair Hybrid Working Policy

Welcome to our hybrid working discussion on October fourth. I am Aisha from People Operations, and Mina will represent the employee feedback process. Tom joins from Engineering, Yuna from Client Services, and Felix from Workplace Support. This Sunday session is an exceptional planning workshop for our company, with attendance arranged in advance. We need a policy proposal that supports collaboration without equating physical presence with performance. Please confirm that you have the employee survey and the manager comments. We are not deciding individual employment arrangements today. Our task is to identify the default expectations, a fair way to handle exceptions, and evidence we can use to evaluate the policy after it begins.

I have both documents. Engineering currently uses two shared office days, but the practical value varies. A design review with a physical whiteboard can benefit from being together, while an afternoon of individual code review often does not. My concern is that a fixed attendance quota will encourage people to travel merely to join video calls from different desks. I can support planned in-person collaboration, but I want teams to explain its purpose. We also hire colleagues outside the commuting area. If the policy quietly assumes that everyone lives nearby, those colleagues could become less visible in decisions even though their employment arrangements were accepted before they joined the company.

I have the materials too. Client Services has a different constraint because customers sometimes request onsite workshops with little flexibility in timing. Some of our staff already spend three days a week at customer locations. If we add two compulsory office days, their practical flexibility disappears. On the other hand, newer colleagues need access to experienced staff, and fully separate schedules have made coaching difficult. I do not want a policy that looks equal on paper but produces unequal burdens across roles. We need to distinguish customer-site work from internal attendance and ensure that coaching is scheduled deliberately rather than depending on whoever happens to be in the office on a particular afternoon.

Workplace Support has the same documents. We can provide room bookings, equipment, and accessibility support, but our capacity is not unlimited. When every team chooses Tuesday, there are more requests for quiet spaces than we can accommodate. When schedules are spread thoughtfully, the office works much better. I would like the policy to include planning notice rather than treating desk availability as someone else's problem. We also need a route for colleagues who require a suitable workspace at home or in the office. Those requests should not be mixed with performance judgments. A person asking for an adapted chair or a quiet room should not have to prove that they deserve flexibility before we discuss practical support.

The survey includes responses from one hundred and twenty employees, representing about three quarters of our workforce. The strongest theme is predictability, not a demand for unlimited remote work. People want to know when they must travel and what collaboration will happen when they arrive. Several respondents said office days are announced the evening before. Others said they miss important discussions because decisions happen informally after a meeting ends. We should be careful with the headline preference for two remote days. Different people meant different things by that answer, and the survey did not distinguish client travel from office attendance. I recommend follow-up conversations before we interpret that number as a mandate for one identical weekly pattern.

The original draft required three office days every week. Managers supported it because they wanted a simple rule they could explain consistently. I still see the value of clarity, but the examples suggest that equal treatment is not necessarily equitable treatment. Could we replace the quota with two planned collaboration days for teams whose work benefits from regular in-person contact, while allowing client-site work to count toward the planned location requirement? Teams with established remote contracts would need a separate arrangement. I am concerned that too much discretion will lead to manager favoritism, so we would need published criteria rather than simply telling managers to use their judgment.

I would challenge the assumption that two days should be the default for every team with some in-person work. Our platform team might need one concentrated workshop every other week, while our hardware group needs regular lab access. A default can be useful, but it should not become a disguised minimum that people cannot question. Could each team publish a collaboration charter explaining the activities that require physical presence, the notice period, and how remote colleagues participate? People Operations could review the charters for consistency. That would let us compare the reasons behind different arrangements rather than compare attendance counts that say very little about whether the work is actually coordinated well.

I like the charter idea, but we should make sure a team cannot simply write whatever its manager prefers. Client Services could say that customer needs require complete flexibility, leaving employees with no predictable home days at all. We need a company-level floor for notice and schedule stability. I suggest publishing ordinary location plans two weeks ahead and treating shorter notice as an exception that requires a reason. Customer emergencies will still happen, but repeated late requests should trigger a workload review. Otherwise, the exception becomes the operating model. The policy should also explain that employees can raise a schedule conflict without that being recorded as a lack of commitment to customers or colleagues.

Two weeks of notice will help room planning, and I can provide a weekly capacity view so teams can choose suitable days. However, I do not want us to solve space pressure by asking employees to compete for desks each morning. Teams should reserve the spaces they need when they publish the plan. If a workshop requires accessible equipment, we need to know that early enough to prepare it. For individual support requests, Workplace Support can coordinate practical arrangements with People Operations while keeping personal explanations restricted. Managers need to know the agreed arrangement, not every detail behind it. That boundary will make colleagues more willing to ask for help before a problem becomes disruptive.

I want to add a concern about proximity bias. Employees described managers praising colleagues they see regularly while overlooking remote contributions that are less visible. A new location policy will not solve that by itself. We need performance discussions to use agreed outcomes, documented collaboration, and feedback from the people affected by the work. Attendance should not be a proxy for contribution. At the same time, remote work should not mean disappearing from shared responsibilities. The charter can specify response expectations during working hours and how decisions are documented. We should hold everyone to those expectations regardless of location, instead of using office presence as an easy substitute for evaluating whether the team is functioning.

That is fair, and Engineering needs to improve decision documentation. We sometimes resolve a design question at lunch and forget to record why we chose an option. Remote colleagues then receive a conclusion without context and are expected to implement it. I propose a simple rule: any decision that changes shared work must be added to the team record before it is treated as final. Informal conversations can generate ideas, but they should not bypass the people responsible for the outcome. We can also rotate workshop facilitation so the same office-based colleagues do not control every discussion. That would make collaboration more inclusive without pretending that every activity works equally well in every location.

For coaching, I would prefer scheduled access rather than a rule that junior employees must be onsite more often. That could make flexibility depend on seniority while leaving the actual coaching inconsistent. We can assign each new colleague a mentor and publish weekly coaching slots, some in person and some online. If a task requires supervised practice, the charter should name it and explain the arrangement. We should also ask newer staff whether the sessions are useful, rather than measure success through the number of meetings alone. A calendar full of coaching appointments can still leave someone confused if the mentor is distracted or the discussion never addresses the problems they are encountering.

We have a proposal that is more nuanced than the original quota. Each team will publish a reviewed collaboration charter, ordinary location plans will be available two weeks ahead, and existing remote arrangements will remain explicit rather than being silently overridden. Client-site work will be included in the location plan, and short-notice changes will require a stated business reason. Performance assessment will use contribution criteria, not attendance totals. We will also establish a confidential request route for individual adjustments. Before we implement this policy, we need to resolve any conflicts with current agreements. Our company's authorized reviewers will check the final proposal before implementation, and we will communicate the actual approved wording rather than treat today's discussion as an immediate change to everyone's contract.

I will draft the employee guidance by Wednesday, October seventh, at noon Asia/Seoul. It will explain how to ask for an individual adjustment, what information is needed, and how a decision can be reviewed if the employee believes the criteria were applied inconsistently. We should not require people to disclose sensitive personal details in a team meeting. I will also run follow-up conversations with ten employees across different roles and locations, including client-facing staff and colleagues outside the commuting area. Their comments will test whether the proposal is understandable and whether any group faces an unintended burden. I will report themes without attributing personal circumstances to named employees in the manager briefing.

I will publish the office capacity view and reservation instructions by Thursday, October eighth, at three p.m. Asia/Seoul. The view will show available collaboration rooms, quiet spaces, and accessible equipment without identifying who has requested an adjustment. I will test the booking process with two teams before we make it the standard route. We also need a fallback when a reserved room becomes unavailable. I can provide an alternative space or help move the session online, but teams should receive a clear notice rather than arrive to find no suitable place. The workplace service should support the collaboration plan, not become a hidden obstacle that employees are blamed for failing to navigate.

Engineering will submit three draft charters by Friday, October ninth, at eleven a.m. Asia/Seoul, covering platform, application, and hardware work. Each will name the activities that benefit from physical presence, the participation route for remote colleagues, and the decision documentation rule. We will not use the same schedule for all three simply because it is easier to announce. I will also brief managers on proximity bias and ask them to review whether their feedback includes evidence from remote work. Yuna and I can compare the coaching provisions so new employees receive predictable support across departments. Differences should follow the nature of the work, not the enthusiasm of an individual manager for seeing everyone at a desk.

Client Services will submit its charter on the same Friday deadline. I will include customer-site planning, mentor availability, and how we handle unavoidable late changes. I would like the evaluation to track how often short-notice changes happen and which customers drive them. That will help us address the planning problem with the customer rather than normalize constant disruption for staff. We should also look at coaching usefulness and whether colleagues understand where decisions are recorded. I will avoid collecting detailed movement data. We need evidence about the working arrangement, not a surveillance system that logs every location change while telling employees that the policy is based on trust and responsible collaboration.

For the employee feedback, we can use an anonymous pulse survey after four weeks and again after eight weeks. It will ask about schedule predictability, access to support, and participation in decisions. We should report results by broad role groups only where the group size is sufficient to protect anonymity. If a small team has a specific concern, we can handle it through a confidential conversation rather than publish a table that effectively identifies the speaker. I will also ask whether the exception process feels usable. A policy can look fair while an employee believes that making a request will damage their reputation. We need to test that experience, not merely count how many forms were submitted.

Our next proposal review is Monday, October twelfth, at one p.m. Asia/Seoul, for fifty minutes. We will compare the charters, employee feedback, and workplace capacity before sending the final draft to the authorized reviewers. The intended policy start is November second, allowing time for communication and schedule planning. That date is not permission to skip the review. If a material fairness issue remains unresolved, we will revise the proposal before it takes effect. I will send a decision summary that distinguishes the company-wide expectations from team-specific arrangements. Please check that summary carefully, because people should not have to infer the policy from rumors about what another department has decided to do.

That timeline works for Workplace Support. I will make the practical information easy to find and include a named contact for booking difficulties. If teams see a capacity conflict, they should raise it during planning rather than tell employees to improvise after they arrive. We have moved away from a simple attendance target toward purposeful collaboration with predictable arrangements. That does not eliminate every tension, but it gives us a way to examine the tensions openly. I appreciate that the evaluation will include the employee experience as well as manager observations. With both perspectives, we can adjust the policy based on how work is actually happening rather than defend a rule solely because it sounded clear in the first draft.