So, what do you do?

This weekend we my daughter’s friend’s parents, and of course, “So, what do you do?” came up.

I realized I haven’t been very good at answering “What do you do?”. I’ve had 3 typical responses for the last couple of years and they all suck.

If I’m talking with someone who…

Those answers aren’t wrong, but they sell my work short. They don’t convey my strengths, my expertise, or the real value that I bring. I’ve especially struggled with this since my role has changed to “Architect”. My work changes week-to-week and project-to-project. The results are hard to quantify and when executed well, “no news is good news.” The “work” in the form of planning, discussions, and prototyping quickly fades into the background. And the final deliverable frequently gets passed onto an analyst to be documented, tested, deployed, and carried over the line.

So, what do you really do?

I provide the ability to think about and solve problems holistically, from a system’s core abstractions (underlying data models & processes) to how those are surfaced and interacted with. Clear thinking across technical and functional dimensions creates long-lived outcomes that quietly fade into the background as they get s*** done and scale. My career has mostly been around Workday, but I also dabble in Python and backend web development for fun.