Most engagements
start with a solution.
Ours start with a
conversation.
A few patterns come up
almost every time.
We've sat with a lot of organizations. This is what we hear.
These are patterns we've seen across organizations of every shape and size. And we've learned that one good question — asked at the right moment — changes not just the conversation, but everything that follows.
Before we recommend anything,
we ask questions.
Two kinds, actually.
The first kind helps us understand the work — what happens, when, and how. The second kind goes deeper — the people, culture, strengths, and challenges. Both kinds are designed less to get answers and more to get people thinking.
The most important discoveries in an engagement aren't ones we bring to the table. They're ones the organization makes about itself — with the right questions creating the conditions for that to happen.
Reliable, automatic, invisible.
Some parts of your work have a right answer. A step that should always happen the same way. A report that builds itself. A notification that never falls through the cracks. We make those parts disappear into the background so your team's energy goes where it's actually needed.
- Automations that execute without variation
- Notifications, approvals & status updates
- Reporting that builds itself
- File organization & project setup
Judgment, nuance, human context.
Other parts of your work require thinking that no rule can fully capture. For those parts, we bring in tools that assist your team's judgment rather than replace it — including, where it genuinely helps, AI-powered assistance designed around your specific needs.
- Research & discovery assistance
- Drafting, summarizing & reviewing content
- Pattern recognition across your data
- Decision support — not decision replacement
The question we always ask: does this step need a rule, or does it need judgment?
Technology changes what's possible.
People bring it to life.
Adoption
- Often treated as a separate workstream rather than part of the design
- People need to understand why, not just how
- Change can feel like loss — or opportunity. How it's framed makes all the difference
Process
- New capabilities require new ways of working
- Those workflows have to be designed as carefully as the technology
- The best results come from involving the people doing the work
Mindset
- Some solutions change not just what people do, but how they think about their work
- This rarely happens automatically
- It has to be a design goal from the beginning
The solution is only part of what we're building.
Frameworks, not rigid systems.
We build frameworks, not rigid systems. Because the one thing we know for certain about your organization's future is that we can't predict it — new people will arrive, priorities will shift, opportunities will emerge that neither of us can see today. So we don't build for the problem in front of you. We build for adaptability. Our clients tend to call that sustainable. We'd call it honest.
The work.
Every engagement is different. But a few stories capture what working with Hallpass and Friends actually looks and feels like.
Daily status reports
Replacing a legacy system
An encryption crisis
Building for every player
A workflow for The Tech Girls
Every one of these started the same way — with someone telling us about their organization. Not the project. The organization.
A small practice built around
thinking carefully together.
The “Hallpass”comes from a teaching background. Years in education shape how you see problems. You learn that the most important part of any lesson isn't what you say — it's what the other person understands. That a well-asked question is worth considerably more than a well-prepared answer.
The “and Friends”is a philosophy as much as a description. The most important friend in any engagement is always the client. The thinking we do together — the questions, the discoveries, the moments where something that seemed obvious turns out to be more complicated than anyone admitted — that's where the real work happens.
We use “we”deliberately. Before Hallpass and Friends there was a stint at NASA's Jet Propulsion Laboratory — an experience that had less to do with rockets than with learning to navigate complexity without pretending to understand things you don't.
None of our clients hired us because of our certifications or credentials. They hired us because of how we work. Because we show up as listeners rather than experts.
The most important part of any lesson isn't what you say — it's what the other person understands. That shapes every conversation we have.
Not as a methodology to deploy but as a disposition to bring. Build, listen, adjust — then build again. Never so rigid we can't pivot.
Full-stack capability across web, data, and workflow systems. Technology is always in service of the outcome — never the other way around.
Tell us about your organization.
Not the project.
Every engagement we've described started the same way — with a conversation. No agenda, no formal requirements document, no prepared presentation. Just someone telling us about their organization and us asking questions.
That first hour is genuinely our favorite part of the work. It's where we hear things that surprise us, where we ask things that surprise the client, and where the interesting stuff almost always begins to emerge.
There's no obligation and no sales pitch. Just a conversation. Those tend to go somewhere interesting.