The Foundational 'How': Distilling What We Actually Do

If you've ever spent time with a toddler, you know the power of the word "Why?" But in the professional world, especially in technical fields like engineering, the more revealing question is "How?"

I recently sat down to distill what I actually do on a daily basis. It’s a useful exercise for anyone trying to understand where their time goes. When you peel back the layers of a career, you eventually hit the bedrock of productivity. It looks something like this dialogue:

"What do you do?"
I work at an engineering firm.

"How?"
I design bridges.

"How?"
I have AASHTO code reference, software programs, spreadsheets, experience, and colleagues.

"How?"
Well, I open the software, the spreadsheets, the code, and I do the calculations.

The Foundation of the Stack

Notice what happens at that final "How." We move from the high-level mission (designing bridges) to the physical interaction with digital tools. At the most foundational level, my job is to access and utilize resources.

Before the first calculation can be run, before the first line is drawn in CAD, I have to find the right spreadsheet, the specific AASHTO section, and the previous project's design notes. This is the "hidden" layer of engineering—the friction of retrieval.

What is the most fundamental thing AI could do for you?

When we talk about AI, we often jump to the "big" things: autonomous design, generative drafting, or predictive failures. But if we look at the foundation of what we actually do, the answer changes.

The most fundamental thing AI can do for me is help me get to the resources I need more efficiently.

At the foundational level of my professional life, this is the "small" thing that would provide the most value. If I can collapse the time between "I need to check this code" and "The code is on my screen," I haven't just saved a few seconds. I've removed the friction that leads to errors and reclaimed the mental space needed for the high-level work—the bridge design itself.

Intent Over Navigation

This is precisely why we built GrabThat. We didn't want to replace the engineer’s expertise; we wanted to remove the "tax" they pay to access their own resources. By allowing an engineer to call for a spreadsheet or a code section via natural language intent, we are supporting the foundation of their stack.

Sometimes, the greatest revolution isn't a new way to do the big things, but a much faster way to do the small things that hold the big things up.