You can get the answer without effort, but you can't get the understanding.
IT Should Support Your Mission
IT departments design most solutions for the person sitting at a desk. Stable Wi-Fi. Big monitor. Quiet room. But half your workforce isn’t there. They’re on a job site, in a truck, on a roof, in a basement with no signal. And they’re using the same tools built for someone who never leaves the building.
Here are 10 ways to fix that. Print this. Hand it to your IT department. Ask them which ones they’ve actually solved.
Build for offline first, not online first.
Field staff lose signal constantly. Every critical app should work fully offline and sync the moment a connection returns. If a form loses data when the bars drop, it’s broken. Ask IT: “What happens to our field tools when there’s no signal for two hours?”Stop forcing two-hand, two-thumb workflows.
Someone wearing gloves, holding a ladder, or driving can’t tap through six screens. Push for voice input, single-tap actions, and big buttons. The test: can a task be done one-handed in under 15 seconds?Make logins survive the real world.
Complex passwords typed on a phone in the rain are a productivity killer. Move to biometric login, badge taps, or single sign-on with long session windows. Field staff shouldn’t re-authenticate five times a day.Pre-load instead of streaming.
Don’t make crews download plans, manuals, or photos over a weak connection on site. Push the files to their devices automatically the night before, over the office Wi-Fi or LTE, while devices charge. They arrive ready.Issue devices that match the environment.
A sleek laptop dies on a dusty, hot, wet job site. Get ruggedized tablets, screen protectors that work with gloves, and cases that survive a drop from a truck bed. Spec hardware for where it actually lives.
Give them a human who answers, not a ticket queue.
A field worker stuck at 6 a.m. can’t wait 24 hours for a ticket response. Set up a dedicated field support line with priority routing and extended hours. Downtime in the field costs more than downtime at a desk.Kill the VPN friction.
Old VPNs are slow, drop constantly, and frustrate people on cellular. Move to modern zero-trust access that connects securely without the spinning wheel. If field staff avoid a tool because “the VPN won’t connect,” you have a bottleneck.Capture data once, at the source.
Stop making crews fill out a form on paper, then re-enter it at the office. Let them capture photos, measurements, and notes directly into the system from the field. Double entry is wasted labor and a source of errors.Plan for the device that gets lost or stolen.
Field devices walk off, get left on tailgates, and break. Set up remote wipe, automatic backup, and same-day replacement so a lost tablet is a minor inconvenience, not a lost day. Ask IT: “How fast can you replace a field device?”Build a feedback loop with the people in the field.
The crew knows exactly what’s broken. Most IT never asks. Schedule a monthly 30-minute session where field staff show IT what slows them down. The fixes are usually cheap and obvious once someone listens.
I’ve been supporting field crews and their IT needs all of my career, one thing is certain, the environment is harsh and unpredictable. Technology solutions have extended to the field with a variety of new capabilities and can unlock form and function for the crews getting the job done. Your IT teams need proximity to the problems they are solving for and getting them in the field is sometimes the only way they can properly develop a solution.
A CIO mindset first applies critical thinking to solve for constraints. When it comes to extending corporate workflows to the jobsite, the constraints are apparent. Let’s support our crews by giving them technology that supports them back.
Until next week,
—Jared
Text Me: 314.806.3912
How To Support Me

Let me send this directly to your inbox every week, subscribers also receive special events and downloads that I don’t publish anywhere else. I enjoy your feedback and respond to every email.
8 levels of context maturity in AI-native engineering
AI shows up in 60% of engineering work. But only about a fifth of it can be handed off without someone babysitting the output. That’s because agents are missing context.
This 8-stage context maturity model gives a real answer on why you haven't seen meaningful productivity gains for all the tokens burned.
Join this live webinar on June 24 (FREE) to learn:
- Why more MCPs provides agents access but not understanding
- What it takes to deploy agents you can trust without supervision
- How a context layer solves for quality, efficiency and cost



