I’m generally less interested in rigid process and more interested in figuring out what will actually work for each project. After doing this for a long time, I’ve found that the best results come from a clear understanding of what matters most, and a willingness to adjust as we go.

I like to work in small, practical steps. We start by identifying what’s most important for your organization and your users, then build toward that piece by piece. That keeps the work focused and avoids spending time and energy in the wrong places.

At every stage, the goal is to have something complete and usable. That way, progress is always real, and decisions about what to do next are based on something concrete.

Once we’ve clarified the scope, we can decide how to structure the work. Some projects make sense hourly; others are better as a fixed scope. We can talk through what you’re trying to do and decide what approach fits best.

Budget is always part of the conversation, but it’s not the only factor. A well-scoped project, even a modest one, can be far more effective than a larger one that tries to do too much at once. My role is to help you make those decisions so the end result is solid, useful, and built to last.