Entrepreneurship.

The word usually brings to mind startups and pitch decks. What actually interests me is the underlying skill: noticing a problem people have stopped questioning, asking why it persists, and building something durable in response. By that definition, a volunteer organization and a small web agency are the same kind of work. And I've learned something different from each.

The common thread I keep returning to is that good ideas are systems. A one-time effort helps once. A system, whether that's a schedule, a partnership, or a process people can follow without you, keeps helping. Most of what I've built started as an attempt to turn a good intention into something repeatable.

The first things I built weren't businesses. Medical Helpers Club started because nursing homes near me couldn't find consistent volunteers after COVID. DFW Cleanup started because the trash along local highways and trails bothered me enough to do something about it. Neither felt like entrepreneurship at the time. But both demanded exactly its lessons: convince people to care about your problem, build the schedules and partnerships that let impact repeat, and design the organization so it can outlive your involvement.

Recruiting members, coordinating with facility staff, and handing off responsibility was the real education. Anyone can organize one event. The hard part is building something that still runs when you're not in the room.

Integrus Web Agency is my first real venture, designing and building websites for local businesses. The surprising part is how little of it is about code. Most of the work is listening until I actually understand what a client needs, translating vague goals into concrete pages, and communicating clearly enough that nobody is surprised at the end.

Building something people pay for teaches honesty fast: the site either solves their problem or it doesn't. Every project has sharpened the same habits: understand the need before proposing the solution, ship, and then keep improving through feedback rather than assumption.

The quiet motivation behind all of this is healthcare. I grew up around medicine, in clinics, around physicians, and eventually volunteering in senior care. What struck me wasn't a lack of care or effort. It was how many problems persist simply because systems are hard to change: scheduling, communication, records, the logistics between a patient and the help they need.

That's the space I find most interesting, where medicine, engineering, and systems-thinking overlap. I don't know yet exactly what I'll build there, but it's the reason I treat entrepreneurship as something worth practicing now, on smaller problems, before the stakes get higher.

School doesn't really teach this, so I read. The Lean Startup changed how I approach new ideas: test the smallest version first, and let evidence beat enthusiasm. The 48-Hour Startup made the whole thing feel less precious: you can just begin. And the biographies of Jobs, Gates, Rockefeller, and Carnegie read like case studies separated by a century. The industries change; the patterns barely do.

I don't read them for imitation. I read them for the recurring shapes: obsession with the product over the pitch, systems that scale beyond their founder, and the long-term thinking that separates building something lasting from building something loud. The older biographies are also honest about the costs of ambition, which feels just as important to understand.

Medicine, engineering, community work, and a web agency look like separate interests from the outside. To me they're one philosophy applied in different places: find a problem that actually matters to someone, build the system that addresses it, and measure success by whether the value lasts.

A placeholder for a favorite line about building things.

Author, Source (placeholder)