About Loud Trumpet
Meet Ryan Haugh and learn how Loud Trumpet brings engineering experience, curiosity, and care for people to organizational change.
Good work takes people who care, decisions they can act on, and room to get things done. When those pieces stop fitting together, even a capable team can struggle to make progress.
Loud Trumpet helps organizations work through those challenges. We bring engineering experience and practical guidance to the places where software, decisions, and people meet. That might mean improving delivery planning, untangling a workflow, or helping a team put AI to useful work.
The starting point is your situation. We'll get curious together.
Hi, I'm Ryan
I'm Ryan Haugh, a founder of Loud Trumpet. I'm a software engineer, an engineering leader, and the person who leads every paid engagement here.
My career has taken me from writing code and working as a contractor to serving as a Director of Engineering, Director of Software Strategy, and VP of Engineering. I've worked on both the technical details of building software and the organizational decisions that shape whether a team can deliver it.
In one organization, I led a company-wide change to delivery planning. Engineering, product, and executive leadership worked toward a shared approach to discovery, estimates, technical debt, and delivery commitments.
As an internal consultant, I worked with acquired-company teams, learning unfamiliar systems and helping them improve development practices, architecture, and coordination. The work called for empathy, especially when people were skeptical of another change. It also meant adapting to each team's circumstances and revising processes when their overhead outweighed their usefulness.
I've stayed close to the code, too. I've architected and implemented design systems and component libraries at multiple companies, and built AI-assisted workflows for recovering specifications and planning changes to existing software.
That mix of experience shapes how I work: understand the technical problem, listen to the people living with it, and make room for both perspectives in the solution.
Change should fit the people doing the work
Your team knows things an outside consultant can't learn from a dashboard. Where a handoff breaks down. Why a workaround exists. Which meeting helps, and which one everyone quietly dreads.
Those details matter. We work with the people involved to understand what's happening, choose a manageable improvement, and agree on how to evaluate it. The people who know the domain stay involved in decisions and retain responsibility for the work.
Sometimes the useful change is a clearer decision or less process. Sometimes it's automation or AI. We choose the approach together and let what we learn guide the next step.
Evidence-informed. Human-guided. Built to adapt.
For us, that means looking at results alongside people's experience, keeping consequential decisions in human hands, and being willing to change course.
Pull up a chair
You don't need a polished brief to start a conversation. Bring the delivery problem that keeps resurfacing, the AI experiment you're trying to make sense of, or the workflow that seems harder than it should be.
We'll spend 30 minutes talking about your situation and whether working together would help. No commitment required.