Onsite or Hybrid? Decide Role by Role with a Presence Matrix

Decide presence role by role, based on what the work requires: physical or restricted access, decisions made in person, and meetings that cannot be replaced. Keep or schedule onsite time where the work genuinely needs it, and solve the rest with better access, decision and meeting rules rather than a desk.

Nextwo ·

This guide is for technology and HR leaders at Saudi companies deciding which roles genuinely need to work from the office.

“We need the team here” can mean three different things. It can mean we need answers quickly. It can mean we need to see that work is moving. Or it can mean the role itself cannot be done anywhere else. The first two are usually collaboration problems. The third is a real requirement, and it deserves a straight answer.

The short answer: decide role by role, not with one rule for the whole team. Keep a role onsite, or schedule onsite time for it, only where its work needs presence and no substitute meets that need. Where the real need is faster answers or visible progress, fix the collaboration rules instead.

Three needs that can require presence

  • Access: the role works with physical equipment, a restricted environment or data that your own security policies or client contracts keep onsite.
  • Decisions: the role depends on stakeholders who decide in person, such as business users in workshops or leaders who prefer to decide in face-to-face meetings.
  • Meetings: some events are worth being in the room for, such as onboarding, major planning workshops, user research or site visits.

A fourth reason can come up: reassurance, the wish to see people working. It is understandable, but it is not a requirement of the role. It is better met by making the work visible, through tickets, pull requests, demos and short written updates, than by moving desks.

The role-presence matrix

For each role, rate the three needs on a simple scale and record why.

  • None: the need does not arise.
  • Occasional: a few times a quarter, predictable and plannable.
  • Regular: weekly or more, but not all day.
  • Continuous: most of the working day.

Then apply a first rule of thumb. Continuous physical or restricted access points to onsite work. Regular in-person decisions point to onsite days or a hybrid pattern. Occasional needs point to planned in-person sessions. None across all three points to remote work with clear collaboration rules.

Here is a hypothetical matrix for a product team:

RoleAccessIn-person decisionsMeetingsFirst reading
Product managerNoneRegular, with business stakeholdersOccasional workshopsHybrid, with regular onsite days
Business analystNoneRegular workshops with usersOccasional user researchHybrid, onsite for workshops
Backend developerNoneNoneOccasional planningRemote
Frontend developerNoneNoneOccasional planningRemote
QA engineer for a hardware deviceContinuous, physical devicesNoneOccasionalOnsite, unless devices can be provided elsewhere
DevOps engineer for on-premises systemsRegular, restricted environmentNoneOccasionalDepends on whether remote access can be approved
Data engineerNone, if remote access is approvedNoneOccasionalRemote

The first reading is a starting point, not the decision. The next step tests each need.

Test every “needs presence” with substitutes

For every rating above none, ask whether the need can be met another way:

  • Remote access: can the environment be reached remotely under your security policy, with the controls your security team requires?
  • A shared working window: would a fixed daily overlap for questions and decisions meet the need?
  • Planned in-person time: would scheduled onsite days or periodic sessions cover the meetings that matter?
  • Written decisions: can the decision move into a short written proposal with an owner and a deadline?
  • Equipment: can the devices or tools be provided where the person works?

If none of these works, presence is a genuine requirement for that role. Keep the role onsite, and say so clearly in the role profile. If one works, record which one and who owns it.

Make the remote part work

Remote roles do well when the arrangement is designed rather than tolerated:

  • Access before day one: accounts, environments and permissions are ready when the person starts.
  • A named decision contact: every remote role knows who decides product and technical questions.
  • Response expectations: the team agrees how quickly questions are answered during shared hours.
  • Visible work: progress lives in the team's tools, not in status meetings.
  • Planned in-person time: where your matrix shows occasional needs, schedule them in advance.

Avoid two classes of team members

Mixed teams carry a specific risk: decisions made in the office may not reach the people outside it. A few rules reduce that risk:

  • One remote, all remote: if one participant joins remotely, everyone uses the same call and shared screen.
  • Written outcomes: decisions taken in a corridor or a meeting room are summarized in the team's channel the same day.
  • Same information: remote members receive the same documents and context as onsite members, at the same time.

When onsite is the right answer

Some roles do need presence: work with physical equipment, environments where remote access is not approved, and roles centered on in-person work with stakeholders. For those roles, onsite is not a compromise. It is the right design.

For roles that come out remote, a dedicated team can work from another location under your direction. Nextwo's Jordan page explains that its dedicated teams work from Amman and collaborate with client teams remotely. It also notes that placing engineers in a client's Saudi offices is a separate service from the dedicated team.

Next step

Fill in the matrix with the hiring manager for each role you plan to add this year, and run the substitute tests before deciding. For roles that can work remotely, Nextwo's Jordan dedicated team page explains how a team in Amman works on your products under your technical direction.

Frequently Asked Questions

Should one rule apply to the whole team for fairness?

Consistency matters, but the fair rule is that presence follows the work. Apply the same matrix and the same tests to every role, and explain the result to each person.

How often should we revisit the matrix?

Review it when a role changes, when systems or access policies change, or when a recurring problem suggests that a need was rated wrongly.