When the Referee Has Skin in the Game

Here's a question that popped up on the site this past week, and I'm genuinely still figuring out what to make of it: what happens when the person deciding whether to give money to a company is also the person hired to lobby for that company?

That's the situation the Ohio Capital Journal flagged this week with Josh Rubin, the chairman of JobsOhio's board. For context, JobsOhio is the state's economic development agency—basically the outfit that decides where Ohio puts big incentive money and grants. According to the reporting, Rubin is a registered lobbyist who's been representing Intel while simultaneously sitting on the JobsOhio board that handed Intel over $150 million in grants and incentives for a chip manufacturing project near New Albany. And he kept lobbying on Intel's behalf even after committing to avoid conflicts of interest when he joined the board back in 2023.

Now, I'm a full-time student at Stark State College studying web development and design, and I work as a Cloud Solutions Architect using AWS architecture through my own small company—I built this whole site this past week partly as a real project to show off those skills. So I'm not exactly a regulatory-conflict expert. But even from where I'm sitting, the awkwardness here is pretty obvious. If you're the person deciding whether your state writes a $150 million check to Company X, and you're getting paid to convince politicians that Company X is a great idea, you've got an incentive structure that doesn't exactly point toward impartial judgment.

The tricky part is that this kind of thing isn't always black-and-white. Economic development is legitimately complicated—states do need to attract big manufacturing projects, and yeah, sometimes the people involved in those decisions have business connections to the companies they're evaluating. But there's a reason we usually try to at least pretend there's a line between the people making the decision and the people being paid to influence it. The line doesn't have to be a brick wall, but it probably shouldn't be invisible.

What makes this one interesting to track is that it raises a question about how we structure these agencies in the first place. If you're building an economic development system, you probably want smart people who actually know the industries involved—so it's tempting to pull in people with real connections to those companies. But the smarter you get at your job, the more likely you are to have financial reasons to push a particular deal through, which creates exactly this kind of mess. There's no clean answer, which is probably why these conflicts keep happening.

For now, this is the kind of thing the site is designed to catch and flag. I started building Stark Civic Monitor this past week because I heard data centers were coming to the area and realized I knew almost nothing about how that actually works locally—no permits, no meetings, nothing. It seemed like a useful project: build a tool to track what's actually happening instead of digging through filings manually, show off some real architecture work for my portfolio, and figure out what everyone's actually upset about while I'm at it. Turns out there's a lot to figure out.

This JobsOhio thing isn't directly about the local data center conversation, but it's part of the same machinery—state-level incentives, economic development decisions, and the question of who's actually calling the shots. If you're going to understand what's happening in your county, you've got to see how it connects to what's happening at the state level. So that's what the site's here to do: find these things, pull them together, and make it so you don't have to spend three hours digging through government websites to know they exist in the first place.