Why your site team won’t use another app (and shouldn’t have to)

Vikas runs a design-build firm of twenty-two people in Bangalore. Last year he decided enough was enough with WhatsApp chaos and bought a project management app. He paid for a year. He ran a Saturday training at the office with samosas. He told every site supervisor that from Monday, updates would only count if they were in the app.

Monday went well. Tuesday, mostly. By the second week, three supervisors had stopped logging in. One had uninstalled it because his phone was full. One said the OTP never came. One, a very good supervisor named Manjunath who has run sites for fifteen years, quietly went back to sending voice notes to the PM, because that is how he has always worked and it gets things done.

By week four, the app had the office team’s tasks in it and nothing from site. Vikas was paying for a very expensive to-do list.

If this sounds familiar, it is worth understanding why it happens, because the answer is not “my team is resistant to change.”

Look at the supervisor’s actual day

Most software is designed by people who sit at desks, for people who sit at desks. A site supervisor’s day looks nothing like that. Picture Manjunath’s Wednesday.

• He leaves home at 7 AM and reaches the first site by 8, after a bus or a bike ride through traffic.
• He spends the day on his feet, often on a ladder, often with dusty or wet hands.
• He is managing carpenters, electricians, a tiler and a painter, each of whom wants something from him.
• He takes calls from the PM, the purchase person, a vendor and sometimes the client.
• His phone is a mid-range Android that is also his family’s phone in the evening, with storage full of photos and videos.
• His data pack runs out around the 20th of the month, and the site has patchy signal on the upper floors.
• He reads English slowly, and is much more comfortable in Kannada, Hindi or Tamil.
• He finishes around 7 or 8 PM, after a twelve-hour day, and then has to send an update.

Now hand this man an app with a login, a dashboard, six menus, a form with twelve fields in English, a dropdown for task status and a requirement to upload photos in a particular place. Ask him to do this several times a day. It does not matter how good the app is. It is built for someone else’s day.

Your supervisor is not refusing to change. He is refusing to do a second job, in a second language, on a second app, at the end of a twelve-hour day.

The real reasons apps die on site

When owners ask why adoption failed, the answers usually sound like small complaints. They are not small. Each one is enough on its own.

• Storage and installation. Another app on a full phone means deleting something. Often that something is the app.
• Logins and OTPs. Shared phones, changed numbers and forgotten passwords block people at the door.
• Data and signal. Apps that need to load a dashboard fail on the fourth floor of an unfinished tower.
• Language. Forms in English, with English labels, ask for typing in English. That is slow and embarrassing for many very capable people.
• Typing itself. Typing with dusty fingers on a small screen, standing up, is miserable. Talking is not.
• Double work. If the PM still calls for updates anyway, the app becomes extra, and extra things are dropped first.
• No visible benefit. If the supervisor gets nothing back, no fewer calls, no faster answers, the app is pure cost to him.

Why voice notes win

Watch what supervisors already do on their own. They send voice notes. Long ones, often, in their own language, with the sound of a drill in the background. They send photos and short videos. They do this without being trained, without a login, on an app that is already on every phone and already works on weak signal.

Voice notes win because they match the work. Hands busy, eyes on the job, mouth free. A supervisor can describe a problem in twenty seconds of Kannada that would take five minutes to type in English. And the voice note carries things a form cannot: the tone that says this is urgent, the detail that does not fit a dropdown.

The problem with voice notes was never the supervisor. It was what happened on the other end. A voice note dropped into a group with nineteen people is unsearchable, unowned and easy to skip. The fix is not to stop the voice notes. It is to make sure each one lands somewhere and becomes something.

The two-taps-a-day idea

If you want structured updates from site, ask for as little structure as possible, at the two moments in the day when the supervisor naturally pauses: when work starts and when work ends.

1. Morning: what is starting today. One message or one tap at the start of the day that says which work begins. That tells the office which phases are live and which sites are quiet.
2. During the day: talk, do not type. Problems, shortages, questions and progress go as voice notes and photos, the way they already do. No forms.
3. Evening: what got done. One tap or one short message at the end of the day to confirm what is finished and what is stuck.

That is it. Everything else is the office’s job: turning voice notes into tasks, following up on issues, preparing the client update. The time cost to the supervisor should be a minute or two a day, not half an hour.

Nine hours a month is more than a full working day, per supervisor, spent on site instead of on a phone screen. That is the difference between a system people tolerate and a system people drop.

There is a quieter benefit too. When the supervisor’s updates arrive in a predictable shape at predictable times, the PM stops calling to ask. Fewer calls mean fewer interruptions on a ladder, and the supervisor starts to see the system as something that protects his day rather than something that eats it.

What good firms do, with or without software

• Meet the team on WhatsApp. Do not fight the tool everyone already uses well.
• Accept voice notes in any language as a valid update. Make the office responsible for turning them into records.
• Ask for a fixed morning and evening check-in, nothing more.
• Stop calling for updates you already received. If the supervisor reports and then gets a call anyway, he learns that reporting is pointless.
• Give something back: faster answers to his questions, fewer calls, clear decisions. Adoption follows benefit.
• Keep money out of his view. Supervisors do not need to see rates or vendor payments, and it is safer for everyone if they do not.

How Pakka handles it

Pakka’s Ops Desk was designed around Manjunath’s day, not the office’s. The site team’s entire app is WhatsApp, with nothing new to install. Engineers send voice notes, photos and videos in their own language, the way they already do, and each one becomes a task, an issue or an approval with an owner. AI suggests what a message means, and a person confirms it: nothing is marked done without the engineer’s tap.

The routine is two taps a day: Starting today in the morning, Update tasks in the evening. Engineers can raise an issue or a snag from the chat, and ask the drawings a question and get the page back. And engineers never see money.

Vikas did not need a team that loved apps. He needed a system that asked his team for nothing they were not already doing.