An analyst who ends processes instead of surviving them.

Matthew Braner Salt Lake City

Nothing in my job description said "write software." Nobody budgeted for it, and there was no developer to hand it to. I wrote it anyway, because the alternative was a week of my life, twice a month, indefinitely. That decision, made once at work and then again and again, is the through-line of everything on this site.

By day I manage federal grants and the data around them. By night I run a card store on an hour a day and build tools that refuse to estimate. The common thread isn't code. It's an allergy to recurring work that a machine should be doing, and a respect for the judgment only a person can supply.

I started as a computer science major in 2016 and left partway through for a full-time job at Vivint, because CS wasn't lining up with where I wanted to end up. That job turned out to be the useful part: auditing call quality meant reporting trends to stakeholders, and doing that is what pulled me toward data.

I went back through the business school for information systems, because I wanted technology blended with the business rather than sitting next to it. Then I struggled to find work in my field, until a peer pointed out that universities offer a real way in. That turned out to be right, and once I was in, the tools started.

Music came first and went furthest. I produce, and the project I ran under an alias grew into one of the largest acts of its kind in Utah, with invitations to play shows around the country, collaborations, paid remix work. The part I'm proudest of isn't the audience, it's that I built it: positioning, promo channels and audience funnel, learned in business classes and pointed straight at my own release schedule. Some of that reach went to environmental outreach and charity events, because a crowd that size is a platform whether you use it or not.

I keep the artist name off my professional work, so take that one on trust or ask me about it. What matters here is the pattern: it's the same marketing and systems thinking I bring to a storefront or a reporting cycle, run on something I cared about first.

Almost every time I've been wrong, the person who caught it had lived a different life than mine. They grew up somewhere else, came in through a different door, got told no where I got told yes. That isn't a nice sentiment to me, it's the mechanism. A team that shares my background shares my blind spots, and shared blind spots sail straight through review. Difference is the only thing I've seen reliably catch what I miss, which is why I'd take a mixed team over a comfortable one every time, and why I go ask the person doing the manual job before I rewrite it. They already know where it breaks. Nobody asks them.

And I've had luck I didn't earn. Someone told me universities were a way in, and it worked. I had evenings free to learn to build things. I ended up with an audience big enough that what I said got heard. When you get handed a microphone like that, pointing it at environmental groups and grassroots organising felt like the obvious thing to do with it, not a cause I picked up for a bio.