03 Oct 2026 4 min read

HRBP: Inbound or Outbound?

Are you an expensive order taker, or are you creating value?

Are you an expensive order taker, or are you creating value?

I was listening to Decoder, one of my favorite podcasts on how companies are structured and run. The guest was Mike Cannon-Brookes, the CEO of Atlassian, and he described teams as either inbound or outbound. It got me thinking about HR business partners. We’re typically seen as an inbound function, and we need to start thinking of ourselves as an outbound one. Here’s where I landed.

Inbound vs. outbound, briefly

Inbound functions exist to receive. Work arrives at them — tickets, contracts, escalations, requests — and the job is to intake it, process it, and close it. Legal and customer service are the classic examples. Success is measured in throughput and resolution. Historically, you add a person and you clear the queue faster, though that is changing with the AI of it all.

Outbound functions exist to originate. They go into the business and create value that didn’t exist before — demand, product, capability. Sales, marketing, and engineering live here. Success is measured in what got built or won. Add a person and you do more, not just faster.

It’s the cleanest language I’ve heard for a question HR has been dancing around for years.

The argument

HR has been understood as inbound for its entire modern history, and that framing is now an existential problem. If we are inbound, AI eats the queue and the function shrinks. That is the whole story — there is no version of inbound HR that survives this intact.

So we need to think of ourselves, HRBPs specifically, as an outbound function. Not as a hedge, not as a blend — as the operating identity. The question that should govern every HRBP’s week is this: what output, what value, what strategy, what guidance are we proactively giving the business leaders we support?

If we can’t answer that, we’re an inbound function with a strategic job title (ouch, but true).

The real test for any activity: if I doubled this team, would we just be faster — or would we be doing more? Faster is inbound. More is outbound.

We can exist in both places — but not with both mindsets. Payroll, compliance, and parts of ER are genuinely intake and always will be, and HRBPs will keep touching inbound work. That’s fine. The point is which one is the default. You operate outbound, and the inbound work gets handled without defining you. One function, two capabilities, one mindset.

The shift is identity before process. The inbound mindset is what makes HRBPs wait to be invited.

Start here: know the business cold

You cannot originate value for a business you don’t understand. Inbound lets you get away with not knowing — the work arrives pre-framed and you process it against policies and rules. Outbound doesn’t. If you’re going to show up with strategy and guidance nobody asked for, you had better understand the P&L, the operating model, the market pressure, and what your leader is actually being measured on.

This isn’t a nice-to-have on top of the outbound shift. It’s the precondition for it.

Say it plainly: you are not going to be an effective business partner if you do not understand the business. We have all heard this for twenty years. We nod at it in every HRBP training deck and then go back to processing. The difference now is that inbound was survivable when you were slow on the business; outbound isn’t. There is no proactive guidance to give a leader if you can’t speak to what they’re up against.

Change the self-concept

Ask yourself every quarter: what need did I spot and act on that nobody asked for? What value did it add?

If the honest answer is nothing, you’re running an inbound operating model regardless of what your job description says.

This isn’t to say inbound work doesn’t add value. It absolutely can and does. It mitigates risk and drives operational rigor. But protecting value is a different job from creating it, and creating it is the outbound work.

Treat intake as signal, not volume

Five instances of the same manager escalation is not five tickets. It’s a design problem you now have the evidence to go pitch a fix for. Inbound processes each one and closes it. Outbound aggregates the pattern and brings a solution to the business.

Show up with a point of view

Arrive before the business has a question. The outbound HRBP brings the insight to the table rather than waiting for the table to send an invitation.

Quiz yourself — and let AI do the grilling. Ask your AI tool to interrogate you on your client group. How does this business make money? What are the top three goals this year and who owns each one? Who are the critical roles and who is ready to backfill them? Where are the spans and layers problems? You either have it or you don’t, and you’ll find out in about four minutes. No study guide, no prep. Do it quarterly and the gaps become a learning plan.

Block time to form a point of view, not an update. Before any leadership meeting, put thirty minutes on the calendar for one question: what do I think about what’s happening to this business, and what should they do about it? An update reports what already happened. A point of view is outbound.

Keep a running pattern log. Every escalation, every repeat question, every manager who needed the same coaching. Review it monthly. Three instances is an anecdote; six is evidence you can take to a leader with a proposal attached. This is how intake becomes origination.

Change what you lead with in your one-on-ones. Open with something they did not ask for — an observation, a risk you’re seeing, a recommendation. Then get to their list. The order matters more than it sounds: it decides who is setting the agenda.