UX Design Services or IT Team Extension: What You Get From Working On the Ground

By the Phenomenon Studio product team

Time spent where users work produces different results for designers and for engineers. Knowing what each one brings back helps you plan in-person time where it matters.

What you’ll learn

• Designers on site bring back workarounds and constraints that interviews miss.
• Engineers on site bring back integration details and adoption problems that tickets never describe.
• Most projects need only a few well-timed visits, planned around research and rollout.
• A partner that combines design and engineering can spread those visits across both goals.

A user described her job in a remote interview as five clean steps. On site, the same job involved a spreadsheet and a sticky note on the monitor with a password reminder. Nothing in the interview was false. It simply left out everything she no longer noticed.

That gap is the reason on-the-ground work exists. It shows what people do, which is often different from what they say. Both user experience design services (https://phenomenonstudio.com/ui-ux-design-services/) and IT team extension benefit from it, though they bring back very different results.

This article looks at what each model gains from in-person time, how the outputs differ, and how to plan visits so the time pays off.

What designers find on site

Designers on the ground look for behavior. They watch people use the current tools and ask about the workarounds they see.

Workarounds are the richest finding from any visit. When staff keep a spreadsheet next to the official system, the spreadsheet usually holds something the system can’t do. That missing capability often becomes the most valuable feature in the redesign.

The physical environment is the second finding. A warehouse screen gets read from two meters away with gloves on. A clinic tablet gets passed between staff in a hurry. Those conditions change button sizes and how much text a screen can hold.

Interruptions during the day are the third finding. Office workers switch between tools constantly, and each switch costs attention. Watching a full shift reveals how often people lose their place, which shapes how the interface saves progress.

None of this appears reliably in remote interviews. People describe their work as they think it should run, and the details they’ve adapted to fade from memory.

What engineers find on site

Engineers on the ground look for systems. They sit with IT staff and trace how data moves between tools, finding the constraints that documentation leaves out.

Integration details are the main finding. An internal system may have an undocumented export that everyone relies on, or a nightly job that breaks when a field changes. Engineers who see these in person avoid surprises during the build.

Adoption problems are the second thing engineers find. During rollout, engineers on site see where people get stuck with the new tool. They fix small issues the same day, before frustration turns into resistance.

Trust is the third, and it’s easy to underestimate. Staff who have met the engineers raise problems early. Staff who only see a ticketing system tend to work around bugs quietly, and the problems stay hidden until they’re expensive.

According to Gartner, the average desk worker used 11 applications to do their job, up from six in 2019. (Gartner, 2023)

Every one of those tools connects to others, formally or through copy and paste. Seeing those connections in person is often the fastest way to understand what a new product has to replace or respect.

What user experience design services deliver from the field

When research happens in context, the output of user experience design services changes. It becomes more specific and harder to argue with.

Expect observation notes tied to real tasks, plus a list of workarounds ranked by how often they appear. Those artifacts help stakeholders see the problem the same way the designers did.

Expect flows that match actual work. A redesign based on field research usually removes steps that people had already skipped informally. It also adds support for tasks that the old system ignored.

Expect faster agreement among your stakeholders. When a debate starts about whether users need a feature, a photo of the sticky note on the monitor tends to end it. Evidence from the field carries more weight than opinions in a meeting room.

The limit is that research ends. User experience design services delivered as a project hand over findings and leave. The engineers who build the product may never visit the site themselves, so some of the context stays with the designers.

What an extended team delivers from the field

An IT team extension outsourcing arrangement places specialists inside your team for months or years. On-site time in this model serves delivery more than discovery.

Early visits help the extended team learn your systems and meet the people who run them. Later visits support training sessions and go-live weeks, when problems surface quickly.

The output is working software that fits the environment. Integrations run because engineers saw the edge cases. Adoption goes smoother because the team fixed friction during rollout instead of logging it for later.

The limit of this model is research depth. Engineers notice systems and adoption, but they aren’t trained to study behavior the way designers are. An extended team without design input may build the right integrations for the wrong workflow.

That’s why IT team extension outsourcing works best when designers are part of the extended team, or when field research happens before the build starts.

The two models side by side

The table compares what on-the-ground work produces in each model. Criteria sit in the first column.

Criteria	UX design services on site	Extended IT team on site
Main goal	Understand how people work	Fit software to real systems
Who goes	Researchers and designers	Engineers and team leads
When presence matters most	Before design starts	During integration and rollout
Typical output	Observation notes and redesigned flows	Working integrations and fixes during launch
How long the value lasts	Until the project hands over	As long as the team stays
Risk if skipped	Designs for work as described, not as done	Surprises in integration and slow adoption

Read down the rows and the timing stands out. Designers gain most from the ground before the build, while engineers gain most near launch.

Internal tools and field teams

On-the-ground work pays off most for products used by staff inside an organization. Clinic systems and school platforms fall into this group, and so do most internal dashboards.

These products share one stubborn problem. Their users didn’t choose them and can’t switch away. When the tool is awkward, people build workarounds instead of complaining, and the product team never hears about it.

According to Gartner, more than one-third of digital workers missed important updates because of the number of applications and the volume of information flowing through them. (Gartner, 2023)

Missed updates are a symptom that shows up clearly in person. A designer watching a shift sees notifications pile up unread. An engineer on site sees which system people actually check first, which tells the team where new information should appear.

EdTech platforms show the same pattern inside schools. Teachers juggle a learning platform and messages from parents during a single class period. A designer who watches that class sees why a clean dashboard still fails if it hides the one alert a teacher needs mid-lesson. WCAG requirements add another layer, since students using assistive technology meet the same screens.

Consumer products gain less from field visits. Their users are spread out, and remote sessions with a broad sample usually reveal more than a few site visits would.

How much on-site time is enough

On-the-ground work costs money and staff time on both sides. A few well-timed visits usually deliver most of the value.

Plan a short kickoff visit first. Designers and engineers meet the stakeholders, see the environment, and agree on who to contact for what. One or two days usually cover it.

Plan a research visit next, if the product has a field component. Designers spend time watching real work across a few roles. A focused week tends to produce more than scattered single days.

Plan a rollout visit near launch. Engineers and a designer support staff as they start using the new tool. Problems get fixed quickly, and adoption starts on a better footing.

Between those visits, remote work covers the rest. Shared working hours and a single backlog keep the team connected until the next trip.

Running a research visit well

A research visit needs more structure than most teams expect. Without it, the day turns into polite conversations that confirm what everyone already believed.

Pick the roles to observe before arriving. Two or three roles whose work the product supports most will give you enough contrast. Schedule time with more than one person in each role, since habits differ even within a team.

Observe people working before interviewing them. Ask people to do their normal work while the designer watches and takes notes. Questions come afterward, prompted by what the designer saw. That order produces answers about real behavior instead of the official process.

Capture visual evidence carefully and with consent. Photos of screens and workstations help later, but only with permission. In regulated settings such as HealthTech clinics, patient data must never appear in notes or images, and HIPAA rules apply to anything the team records.

Close the day with a short debrief. The visitors list their top findings while memories are fresh, and the product lead decides which ones need follow-up. User experience design services that skip this step often lose half of what they saw.

Running a rollout visit well

Rollout visits serve a different purpose. The goal is adoption, and the team measures success by how quickly staff stop reaching for the old tool.

Bring engineers and at least one designer. Engineers fix bugs on the spot, while the designer notices where people hesitate and suggests quick interface changes.

Set up a visible place for questions. Staff are more likely to raise problems when they know where to find the team. A corner desk or a shared chat channel both work.

Track the problems found and fixed each day. That list shows which issues were one-off confusion and which point to design gaps. An IT team extension outsourcing arrangement keeps the same engineers on the product afterward, so the fixes keep coming once the visit ends.

Where a Dallas team fits

For companies in North Texas, a nearby partner makes these visits simpler. A web development company Dallas businesses work with can reach the site without long travel, which makes short, frequent visits realistic.

Proximity matters most during the rollout itself. Picture a new tool going live across several locations in the metro area. A web development company Dallas teams can call in the same day shortens the gap between a problem and its fix.

It matters less for research on products with users outside the region. If staff sit in several states, a web development company Dallas firms hire will still need to travel or run remote sessions.

Judge any local partner on what it does during visits. Ask a web development company Dallas clients recommend how it plans field research and who attends. Ask for an example of a finding from a past visit that changed the product. A web development company Dallas companies trust should answer with specifics.

Measuring what a visit produced

Visits feel productive almost by default. People meet, ideas flow, and everyone leaves with a good impression. Measuring the result keeps the team honest about whether the time paid off.

For research visits, count the decisions that changed. A useful visit alters at least one flow, removes a planned feature, or adds support for a workaround. If the backlog looks the same afterward, the visit mostly confirmed existing plans.

For rollout visits, watch adoption over the following weeks. Track how often staff return to the old tool, and how many support requests arrive. Both numbers should fall faster at locations the team visited than at locations it didn’t.

Combining both models

Many products need both kinds of field work. Designers study how people work before the build, then engineers fit the software to real systems during rollout.

Running these through two vendors creates a gap. The designers leave with their observations, and the engineers arrive without them. Some of the context gets lost in a handoff document.

A partner that provides both design and engineering closes that gap. The same team carries field findings from research into development. Engineers know why a flow looks the way it does, because the designers who saw the site sit in the same reviews.

Phenomenon Studio handles both kinds of field work in one engagement. Clients get one embedded group, with our designers and engineers inside their product team. That structure lets us offer user experience design services and IT team extension outsourcing as a single engagement instead of two contracts. As a long-term product partner, we work with SaaS teams and HealthTech companies, along with EdTech and FinTech products. With people in six countries across North America and Europe, the team keeps overlap with client working hours.

Oleksandr Kostiuchenko, Marketing Manager at Phenomenon Studio, recommends judging field work by one output. Ask what changed in the product because of a visit. In his view, a strong visit produces at least one decision that nobody would have made from a remote call. If a vendor can’t name such a change from past projects, its visits are probably closer to meetings than to research.

What each vendor type does during a visit

Vendor titles overlap, and they say little about field work. For on-the-ground work, the useful question is what each vendor actually does during a visit.

A UX design agency usually sends researchers to observe and interview. A second UX design agency may only run workshops with managers, which misses the frontline view. Firms selling UI UX design services often include field research, though some skip it to save budget. Ask whether UI UX design services quotes include site visits by name.

Marketing-site vendors rarely do field work. Website design services and web design services focus on public pages. A web design agency in that space has little reason to visit your warehouse. A second web design agency may offer research for campaigns instead. Website design services quoted for an internal tool deserve a close look, since the needs are very different. Ask how website design services would handle users who work in noisy or crowded places.

Build vendors vary widely in how they treat visits. A web development agency focused on fixed projects may visit once for kickoff. A website development agency offering ongoing teams may visit during every major release. Ask each website development company how it supports rollouts on site. A second website development company may include training for staff. Internal tools often need more rollout support than public sites, so web development services for them should include it. Quotes for web development services priced without visits assume a smooth launch. Field teams need web app development tested in the real environment. Plan web app development schedules with room for fixes found during rollout. Some vendors bill rollout help as a separate line, which is worth knowing before you compare totals with a third website development company. Web app development for regulated settings also needs on-site access reviews.

Mobile vendors face the same question. A mobile app development company building tools for field staff should test on the devices those staff carry. Mobile app development services should include field testing before release. A mobile app development agency that tests only in an office may miss problems with glare or weak signal. Mobile app development services for frontline teams deserve a visit to where the app will be used.

Branding companies rarely need field time. Settle positioning with branding companies before design starts, so internal tools and public products share a consistent voice.

Questions to ask before the first visit

A few questions make sure a visit produces results instead of goodwill.

Ask who will attend and what each person will look for. A visit with a clear goal for each attendee brings back more than a group tour.

Ask how findings will be shared. Notes should reach the whole team within a few days, while the details are fresh.

Ask what happens after the visit ends. Each visit should end with a decision or a change to the backlog. If nothing changes, the visit didn’t earn its cost.

Your browser does not support embedded video.

Frequently asked questions

Is field research worth it for a small product?

It is when the users work in a specific place, such as a clinic or a warehouse. For consumer products used at home, remote sessions with a broad sample usually reveal more.

Should engineers join research visits?

One engineer joining a research visit helps a lot. They notice system constraints that designers miss, and they bring that context back to the build.

How do I prepare staff for a site visit?

Explain that the visitors are studying the tools, not evaluating people. Staff who understand that tend to show their real workarounds instead of the official process.

Can remote research replace site visits?

For many products, remote research is enough. Screen-sharing sessions show a great deal. They miss the physical environment and interruptions, so products used in busy workplaces still gain from some in-person time.

When should rollout support happen on site?

During the first days after launch at each major location. That’s when staff hit problems for the first time, and quick fixes shape whether they accept the new tool.

What should a visit report include?

Observations tied to specific tasks, with the workarounds found and a short list of recommended changes. A report that ends with decisions is more useful than one that only describes the day.