Making new tech work for old pros

Making it work for the audience

The project was ambitious. A mobile app used to log every bit of data on the project. There were simple things like coordinates of a fix, but crew leaders also needed to confirm safety protocols were met for the purpose of creating compilation Progress Reports within the web app. Then there were safety reports, and quality reports. And then you had wifi problems in rural areas.

Technically speaking, this was no problem. But strategically speaking, this needed some intense thought. This app would be used by grizzled veterans of pipeline construction, guys who had been doing it the old-fashioned way for decades. We needed this app to make sense to them, or risk alienating them; just because you tell them to use a new app, you can’t assume they actually will.

On the other side of the pipeline, the Latex web app would bring in huge amounts of data for analysis by the corporate team. Our design team needed to find a way to make these huge troves of data simple to view from a common dashboard, and equally simple to sort and export for use.

This was a big project, with a big budget. It also had a big deadline hanging over it.

The task stack wobbles

This was a big project with a big budget. The "simple" Progress Report was the sum of many tasks: We needed to create separate reports for all users in the field, which needed to accept manual data entry while ingesting geographic and weather information, and also connecting to the user’s phone camera. It all needed to go to the right place and be organized into a digestible report.

And then Latex said that it needed a Fuel Tracking function as well.

It’s not an unreasonable ask. After all, any construction company that uses as much heavy machinery as latex does is also spending a truckload on fuel. Using an app such as this to track the use of fuel is logical. So we started looking into the solution.

The problem was we were already well into the six-month project window, and the time it would take to design, develop, and test an entirely new functionality was cutting significantly into the time we spent perfecting the Progress Reports. So we went to Latex and we told them the truth (if not an outright ultimatum): If we add this to the scope of the project, the Progress Reports will suffer.

We can’t afford to push back the deadline, and we never push back deadlines. We need to push back the scope. That isn’t to say that Urbity couldn’t create the fuel tracking functionality later, but it shouldn’t be done now. Basically, we hoped Latex would see the difference between what they wanted, and what they needed. Thankfully, they did.

First impression is everything

This was a big project, with a big budget, and it was only going to get bigger if Latex had its way. Again, there is a lot that goes on during any given pipeline construction process, and the peak function of the app was to collect all of these going-ons into a simple Progress Report for the company to review. That simple report was the sum of many additional complex tasks, however. We needed to create separate reports for all of the users in the field, which in turn needed to accept manual data entry while ingesting geographic and weather information, and also connecting to the user’s phone camera. All of this information needed to go to the right place and be organized into a digestible report. It was one of the most involved projects we’ve ever committed to, already.

And then Latex said that it needed a Fuel Tracking function as well.

It’s not an unreasonable ask. After all, any construction company that uses as much heavy machinery as Latex does is also spending a truckload on fuel. Using an app such as this to track the use of fuel is logical. So we started looking into the solution.

The problem was we were already well into the six-month project window, and the time it would take to design, develop, and test an entirely new functionality was cutting significantly into the time we spent perfecting the Progress Reports. So we went to Latex and we told them the truth (if not an outright ultimatum): If we add this to the scope of the project, the Progress Reports will suffer. We can’t afford to push back the deadline, and we never push back deadlines. We need to push back the scope. That isn’t to say that Urbity couldn’t create the fuel tracking functionality later, but it shouldn’t be done now.

Basically, we hoped Latex would see the difference between what they wanted, and what they needed. Thankfully, they did.