The Standard's Blog

When Growth Stalls, Look at Your Standards First

Wed, 05 Aug 2026 20:30:33 GMT

When Growth Stalls, Look at Your Standards First

Growth rarely stalls because people stopped trying. More often it stalls because the same effort quietly stops producing the same results. Orders take a little longer to fill. Two customers with nearly identical needs walk away with noticeably different experiences. A decision that should take an afternoon sits for a week because no one is confident about what "good" looks like without checking first.

The instinct in that moment is to add. Add headcount. Add software. Add another standing meeting. Add a layer of review. It feels productive because it is visible and easy to approve. But capacity poured into a business that has never clarified its standards for growth tends to spread the confusion further rather than contain it.

Hiring more people and buying more tools will not improve execution if no one knows the standard they are expected to meet.

That is the constraint most growth conversations skip past. It is rarely talent or budget. It is the absence of clear business standards for how the company leads, serves, decides, and grows — not the values printed on a wall, but the working definition of what acceptable and excellent actually look like in the day-to-day.

Where the cost actually shows up

Unclear standards do not announce themselves. They show up as friction that looks like ordinary busyness.

The first cost is rework. When "finished" means something different to each person, work gets completed, reviewed, sent back, and redone. That loop is expensive, and it rarely appears on any report as a line item. It just feels like the team is slower than it should be for its size.

The second cost lands on the customer. When quality depends on who happened to pick up the phone or handle the account that day, the experience becomes inconsistent. Customers may not be able to name it, but they feel it, and inconsistency erodes trust faster than the occasional mistake does.

The third cost is the decision bottleneck. When the standard lives only in the founder's head, every meaningful call routes back to the founder. The business cannot move faster than one person's availability, and the person carrying it starts to feel that growth has made their job heavier, not lighter.

When the problem is definition, not effort

It helps to tell the difference between a team that is under-resourced and a team that is under-defined. A few signs point clearly toward definition:

- Your most capable people keep asking questions that all reduce to the same thing: what does good look like here?

- New hires take far longer to become genuinely useful than their experience would predict.

- You regularly correct or redo work that was technically complete.

- Outcomes swing depending on who is in the room.

- The complaints you hear cluster around consistency rather than capability.

None of that is a motivation problem. People are trying to hit a target that was never clearly drawn. Add more people to that situation and you simply have more people aiming at a blur.

What a clear standard makes possible

A defined standard changes what a leader can safely hand off. You can delegate the work without delegating the judgment, because the judgment is now written down and shared. Accountability becomes fair, because you are measuring against something both sides agreed to rather than a moving expectation. Hiring improves, because you know the bar a candidate needs to clear. Training accelerates, because "watch me and absorb it" gives way to a standard someone can learn and repeat. And the customer experience steadies, because it no longer depends on which employee a client reached.

This is the quiet mechanism behind businesses that scale without losing themselves. The standard, rather than the founder, becomes the thing that travels into every room.

Values, goals, procedures, and standards are not the same thing

Part of what keeps this work undone is that "standards" gets confused with other things a business already has.

Values describe what you believe. Goals describe where you are trying to go. Procedures describe the steps for a specific task. Operating standards are different from all three. They define the level of quality and behavior expected regardless of who is doing the work or which task is in front of them. They are the bridge between what you believe and what actually happens when you are not in the room.

One useful way to make a standard concrete is to finish this sentence for the few things that matter most: "We always ___, even when ___." A company might commit to always following up the same day, even when the team is slammed. Always walking a client to the door, even when the lobby is busy. The "even when" is where a real standard proves itself, because that is the moment it is easiest to let slip.

A short way to find your limiting standard

You do not need to define every standard in the business at once. You need to find the one that is currently costing you the most. A few questions surface it quickly:

Which recurring decision still routes back to you or another senior leader for approval?
Where in the customer experience do outcomes vary most depending on who delivers them?
What is the task your team redoes most often?
What would a capable new hire be unable to figure out without asking someone?

Start with the recurring decision that still requires your sign-off. That single answer usually points straight at a standard that was never made explicit, and clarifying it tends to free up more capacity than another hire would have.

From more activity to clearer execution

Stalled growth pulls leaders toward motion, because motion feels like an answer. But more activity layered on top of unclear standards produces a busier business, not a better-led one. The more durable move is to slow down long enough to define how the business is meant to lead, serve, decide, and grow, then let that clarity do the work that headcount and software cannot.

That shift is the heart of the Strategic Executive Advisor work: helping leaders name their non-negotiables, close the gaps where alignment breaks down, and build standards that support growth instead of depending on any one person to hold it all together. It is also how a leader begins to reduce founder dependence and move from reactive operations to clearer leadership .

Start with a clearer standard for how your business leads, serves, and grows. If growth has made your company harder to run consistently, schedule a conversation about the standard that would take the most pressure off first.

Calm Is a Deliverable

Wed, 08 Jul 2026 20:22:04 GMT

Calm Is a Deliverable

At a well-run event, the audience never learns how close things came. A keynote speaker gets stuck in traffic and no one in the room notices the reshuffle. A vendor misses a delivery window and lunch still lands on time. A last-minute request from the C-suite gets handled before it reaches the people it would have rattled. What the guests experience—and what the executives who staked their reputation on the day experience—is something smooth, intentional, and unhurried.

That smoothness is not luck. It is the visible result of a great deal of quiet, coordinated work, and it depends on event leadership under pressure that most attendees will never see. Guests and executives should not have to feel the challenges happening behind the scenes. When they do, something in the leadership chain has broken down.

Calm, in other words, is not a mood. It is an outcome. And like any outcome that matters, it can be planned for, produced, and delivered.

Calm is not the absence of problems

It helps to be honest about what calm actually is, because the word gets misused. A calm event is not an event where nothing goes wrong. Every program of any size carries friction—weather, technology, egos, timing, a room that behaves differently once it fills with people. The question is never whether problems will appear. They will.

The real question is whether the team has someone who can meet those problems without transmitting stress to everyone around them. Panic is contagious. So is composure. When the person leading on site stays organized and steady while solving something difficult, that steadiness spreads to the vendors, the crew, and the internal team who are all watching to see how bad it really is. When that person visibly unravels, the whole room tightens.

Calm is what allows problems to be solved quietly instead of publicly.

What produces calm

Because calm reads as a personality trait, it's easy to assume some people simply have it. In practice, it comes from a handful of concrete disciplines that any experienced operator can name.

It starts with preparation . Most of the calm you feel at a good event was created days earlier, in the run-of-show review, the vendor confirmations, the walk-through, and the quiet cataloguing of everything that could plausibly go sideways. A thorough leader has already imagined the awkward version of the day and decided, in advance, how to handle it. Very little that happens on site is truly a surprise to someone who prepared for the range of outcomes.

Then there's information flow . Pressure builds fastest when people don't know what's happening. An experienced onsite leader becomes the point where information gathers and gets routed—who needs to know what, when, and in how much detail. Executives get the clear headline. The crew gets the specific instruction. Nobody is left guessing, and nobody is buried in noise they can't act on.

Close behind it is ownership . On a complex event, the worst moments are the ones where something falls between roles and no one is sure whose call it is. Clear ownership removes that hesitation. When everyone knows what they hold and who holds the rest, decisions get made instead of debated.

Prioritization matters just as much. Under pressure, three things always seem urgent at once. Part of leading well is deciding, quickly and without drama, which one actually threatens the experience and which two can wait ten minutes. That judgment is hard to teach and easy to spot when it's missing.

Finally, escalation . Calm is not the same as handling everything alone. It's knowing which issues to absorb, which to delegate, and which genuinely need to reach a decision-maker right now. A good escalation instinct protects executives from noise while making sure the one thing they truly need to weigh in on actually reaches them in time.

Absorbing complexity without becoming the bottleneck

There's a failure mode worth naming here. A leader can be so central to the day that every question runs through them, and the effort to stay in control quietly turns them into the thing slowing everyone down.

The stronger move is to absorb complexity without hoarding it. An experienced onsite operator holds the full picture—the risks, the dependencies, the sequence—while still pushing decisions and authority out to the people equipped to act. They're inquisitive enough to catch the overlooked detail and secure enough not to touch everything themselves.

This is also why the senior onsite role works best as an integration, not a takeover. Courtney joins the internal, agency, and production team already in place. The planners, producers, and coordinators who built the program keep their roles and their expertise. What the senior execution layer adds is calm judgment across the whole environment—C-suite awareness, cross-functional coordination, and the ability to make fast, thoughtful calls when live conditions shift. It's the difference between staffing capacity and senior leadership capacity, and strong events often need both.

What confidence looks like to the people around you

Executives, vendors, and internal teams don't measure calm by how relaxed someone appears. They read it in behavior.

Executives relax when they can tell the person running the floor already knows what they were about to worry about. Vendors settle when instructions are clear, respectful, and consistent—when they're treated as partners rather than problems. Internal teams steady themselves when they see decisions being made without theatrics and questions being answered without defensiveness.

None of this is performance. It's the natural byproduct of someone who is prepared, organized, and fast on their feet, and who has seen enough events to recognize where this particular one is likely to bend. That kind of instinct isn't a claim about temperament. It comes from having handled the range of situations before and knowing, from experience, which ones warrant real concern.

Why calm makes the team faster

There's a misconception that a calm approach means a slow, cautious one. The opposite tends to be true. Panic narrows judgment. It fixates on the loudest problem, skips steps, and creates second problems while solving the first.

Calm widens the field of view. It lets a leader see the whole board, weigh options quickly, and act with a steady hand rather than a frantic one. Decisions made from composure are usually both faster and better, because they're made with full information and a clear head. Calm doesn't compete with speed. It's what makes real speed possible.

A readiness checklist before the doors open

Calm is easier to deliver when a few questions have honest answers before the event begins:

Does one person hold the complete picture of the day, including the parts that could go wrong?
Is it clear who owns each major function, with no gaps between roles?
Is there a defined path for how information reaches executives—and a filter for what shouldn't?
Does the team know which problems to escalate immediately and which to handle in place?
Has someone walked the actual flow of the day, not just read the run of show?
If the plan changed in the first hour, would the team adapt smoothly or scramble?

When those answers are solid, the room feels calm because the leadership is prepared. When they're vague, everyone finds out at the worst possible time.

Calm is a deliverable

It's worth treating calm the way you'd treat any other line item on a high-stakes event: something you intend to produce, not something you hope shows up. Guests and executives measure a program by how it felt, and how it felt is decided largely by whether the people leading it were steady when it counted.

If you're planning an event where the room, the reputation, and the details all have to hold, that steadiness is worth designing for on purpose. To bring an experienced onsite event professional into your program — someone who integrates with your existing team and helps it lead under pressure — start a conversation with The Standard . The best time to build calm into the day is before anyone in the room needs it.

What Unreasonable Hospitality Means in Any Business - Not Just a Restaurant

Fri, 05 Jun 2026 20:14:22 GMT

What Unreasonable Hospitality Means in Any Business - Not Just a Restaurant

Every business serves someone. A patient in a waiting room. A client reviewing a proposal. A family walking onto a dealership lot. An attendee finding their seat at a conference. Underneath all of it sits a quieter question than most companies like to admit: when people deal with us, do they feel noticed, or do they feel processed?

That question is what unreasonable hospitality is about, and it has never been a restaurant idea.

What unreasonable hospitality actually means

The phrase was popularized by restaurateur Will Guidara, who used it to describe giving people more than they expect. It took hold in fine dining because that world lives and dies on how guests feel. But the principle was never confined to a dining room. At its core, hospitality is the intentional way an organization shows people that it notices, understands, and cares. Any business that serves human beings is already in that business, whether or not it has decided to be deliberate about it.

I am a Certified Unreasonable Hospitality Coach, and most of the work I do has nothing to do with food. It has to do with helping leaders see that the thing their customers remember is rarely the product itself. It is how they were treated on the way to it. That is also why hospitality belongs on the list of things a company competes on, not off to the side as a nicety.

Care is not the same as spending money

There is a common misreading of hospitality that turns it into a budget line. Send a nicer gift. Add a surprise. Comp something. Those gestures can be lovely, but they are not what makes hospitality an advantage, and they do not repeat well.

Memorable care usually costs very little, because it comes from paying attention. A dental office that remembers a patient hates the overhead light and dims it before being asked has done something more powerful than any waiting-room gift basket. A financial advisor who senses a client is anxious about a decision and slows the conversation down has offered something no discount can match.

This is where the difference between service and hospitality becomes practical. Service is what you deliver. Hospitality is how the person feels while receiving it. You can run flawless service alongside cold hospitality, and people will remember the cold.

The trouble with surprise-and-delight tactics is that they are random by design. They depend on someone feeling generous in the moment. Hospitality that lasts is built on standards, not moods.

What it looks like away from a dining room

Once you stop treating hospitality as an industry and start treating it as a discipline, the openings show up everywhere. This is hospitality beyond hotels and restaurants , and it belongs in places that would never describe themselves as hospitality businesses.

In professional services, it can be a law or accounting firm that explains what happens next in plain language instead of leaving an anxious client to guess. In healthcare, it is the practice that treats the fifteen minutes before an appointment as part of the care rather than as dead time. On a dealership lot, it is a salesperson who reads that someone wants room to think instead of a pitch. In financial services, where trust is essentially the product, it is the advisor who checks in after a rough market week without being prompted.

Events are their own version of this. I have spent decades leading high-stakes events, and the moments attendees actually carry home are almost never the ones printed on the run of show. They are the small signals that someone was thinking about them specifically. None of these examples require a hospitality résumé. They require attention, and permission to act on it.

Standards and permission make it repeatable

This is where good intentions usually fall apart. A leader gets inspired, gives a stirring talk about caring more, and nothing has changed by Thursday. Inspiration is not a system.

Hospitality becomes reliable when two things are in place at once. The first is a clear standard, so a team knows what good looks like rather than guessing at it. The second is permission, so people are trusted to act on what they notice without waiting for sign-off.

Those two have to travel together. Standards without permission produce a script, and a script quietly turns capable people into robots reading lines. Permission without standards produces a coin flip, where one employee is wonderful and the next is indifferent. What you want is a team that shares a clear definition of care and has the latitude to deliver it in their own voice. That combination is what lets hospitality scale past the founder or the one naturally gifted employee everyone secretly relies on.

A simple way to hold this with a team is the sentence, "We always ___, even when ___." We always walk a client to the door, even when we are slammed. We always explain the bill before we send it, even when it is uncomfortable. Standards written that way tend to survive a busy day, which is the only test that matters.

The moments most businesses overlook

Most of what a customer remembers happens in three windows, and companies tend to over-invest in the middle one.

Before the core service, there is arrival. How someone is greeted, how clear the instructions were, what the confirmation felt like, whether the wait respected their time. Impressions form before anyone does the real work, and this is where even strong companies quietly undercut themselves. It is worth understanding just how much the first few minutes shape the whole experience .

During the service, hospitality shows up as anticipation. Removing a friction the person has not named yet. Remembering a detail from last time. Catching discomfort and responding to it before it becomes a complaint.

After the service comes follow-up, and this is the window nearly everyone wastes. A note or a check-in that is not a sales pitch tells people the relationship did not end at the transaction. It costs almost nothing, and it gets remembered for a long time.

Questions worth putting in front of your team

If you want to find your own overlooked moments, the exercise is less about brainstorming grand gestures and more about looking honestly at what you already do. A few questions tend to surface more than a strategy session:

Where do people first feel our attention, or the absence of it? What do we consistently notice about the people we serve, and what do we routinely miss? Which moment do we treat as ordinary that the customer actually experiences as meaningful? And where are we delivering perfectly good service while giving people no reason to feel anything at all?

The answers usually point at small, fixable things, which is the encouraging part. Hospitality as a competitive advantage is rarely the product of a dramatic overhaul. It comes from a business deciding what care looks like and making it the standard everywhere, for everyone.

Here is one worth sitting with before you close the tab: name a single way your business currently shows people it cares beyond delivering what they paid for. If that answer comes slowly, it is not a failure. It is exactly where the opportunity is.

Turn attention into a standard

Hospitality stops being a personality trait and becomes an advantage when a whole team works from the same definition of care. If you want to explore how these principles can strengthen your team and your customer experience, that is the heart of our Unreasonable Hospitality workshops , where teams look at their real touchpoints and turn care into a team standard they can actually keep. When you are ready to talk it through, schedule a conversation and we can look at where your experience is already strong and where it quietly falls flat.

Excellence Is Not Luxury. Excellence Is Consistency.

Wed, 27 May 2026 20:06:39 GMT

Excellence Is Not Luxury. Excellence Is Consistency.

Somewhere along the way, excellence got confused with expense. When a business decides it wants to stand out, the first instinct is often to add something: a nicer welcome gift, a more elaborate event, a gesture designed to impress. Those things can be lovely. They are rarely what earns loyalty.

What earns loyalty is steadier and less dramatic. A consistent customer experience — where people know what they're going to get and receive it every time — builds far more trust than the occasional burst of brilliance. Excellence isn't the most expensive version of what you do. It's the most repeatable version of the thoughtful thing you already know how to do well.

Why a consistent experience beats occasional brilliance

A single extraordinary experience is a nice surprise. The problem with surprises is that no one can count on them. When a customer has a wonderful visit on Monday and a forgettable one on Thursday, the forgettable one carries more weight, because it teaches them that the good version was luck.

Reliability and consistency does something specific: it lowers the customer's guard. People relax when they stop bracing for the version of you that might not show up. That ease is where trust forms, and trust is what brings people back and makes them comfortable recommending you to someone else. Predictability sounds unglamorous, but from the customer's side it feels like calm and confidence — two things people quietly value more than spectacle.

The details that actually shape the experience

Most of what customers feel comes from a handful of ordinary, frictionless moments that repeat constantly. None of them require a budget.

There's acknowledgment — whether a person is noticed promptly or left wondering if they've been seen at all. There's timing, and whether things happen close to when they were promised. There's communication, especially when something changes and the customer would rather hear it early than discover it late. There are handoffs, the seams where one person passes a customer to another and details get dropped. There's recovery, which is how you behave when something goes wrong. And there's follow-through, the quiet test of whether the thing you said you'd do actually gets done.

A business can spend heavily on atmosphere and still fumble every one of these. Another can operate on a modest budget and get them right so reliably that customers assume the whole operation is more polished than it is. The difference isn't money. It's whether those moments are defined clearly enough to happen the same way regardless of who's working or how busy it gets.

Standards turn good intentions into reliable behavior

Most teams already want to do good work. Good intentions, though, don't survive a short-staffed Tuesday or a line out the door. What survives pressure is a clear standard — a shared understanding of what "good" looks like that doesn't depend on someone's mood or memory.

This is usually where consistency breaks down, and it's rarely because people don't care. More often, no one ever defined the expectation precisely enough to repeat. "Give great service" is a hope. "Every guest is greeted within a minute of walking in, even when we're slammed" is something a person can actually meet. When expectations stay vague, your team fills the gap with guesswork , and guesswork produces exactly the inconsistency you're trying to eliminate.

Naming those expectations and making them visible enough that everyone works from the same definition is much of what it takes to define visible team standards people can follow.

Consistency without turning people into robots

There's a real fear underneath this conversation: that standardizing an experience will flatten it into a script, and that customers will feel the difference between a warm interaction and a rehearsed one.

That fear is worth respecting, because scripted service does feel hollow. A good standard, though, defines the outcome, not the exact words. "The customer should feel remembered" is a standard. How a particular person delivers that — the phrasing, the warmth, the read of the moment — is left to judgment. The point isn't to remove the human from the interaction. It's to make sure the human is free to be thoughtful because the mechanics underneath are handled. Consistency covers the floor so people can pay attention to the person in front of them. That's often what a hospitality workshop helps a team sort out together: where the standard belongs, and where individual judgment should take over.

Choose three details customers should never have to hope go well

If you want a practical place to start, don't try to fix everything at once. Pick three.

Look at your customer's experience from beginning to end and find the three moments that matter most — the ones where, if things go wrong, the whole impression suffers. Then ask three questions of each:

Is the expectation defined clearly enough that a new employee could meet it?

Does it happen the same way when you're busy as when you're slow?

Would everyone on the team describe "doing it right" the same way?

Three non-negotiables held consistently will do more for your reputation than a dozen vague aspirations. The exercise also tends to surface something uncomfortable fairly quickly: the detail you most want customers to be able to count on is often the one you're currently leaving to chance.

That's the question worth sitting with. What is the one thing a customer should never have to hope goes well when they choose you?

The quiet advantage of being predictably thoughtful

Being predictably thoughtful is not a modest goal. It's one of the harder things for a business to pull off, because it has to hold up on ordinary days, under pressure, across shifts, with the people you actually have. It doesn't photograph well and it rarely earns applause. It just builds the kind of trust that compounds — the customer who returns, the referral offered without being asked, the reputation that grows quietly because the experience holds.

That version of excellence is available to almost any business, regardless of budget. It starts with deciding what your standards are and making them clear enough to repeat.

If you're ready to make excellence repeatable by defining the standards your team can follow, let's talk.

Why Tech Events Often Need More Human Hospitality

Thu, 07 May 2026 20:06:41 GMT

Why Tech Events Often Need More Human Hospitality

The keynote looked extraordinary. LED walls curved across the stage, the live demo ran flawlessly, and the product reveal earned genuine applause.

Then the session ended.

A few thousand people funneled into a corridor with three ambiguous signs, one overwhelmed staffer, and no obvious path to what came nex t.

The technology worked. The experience stalled.

That gap shows up at technology conferences more often than the production budget would suggest. The staging is ambitious, the event platform is sophisticated, and the content is strong—but the attendee experience can still feel surprisingly thin.

The problem usually isn't capability. It's where attention went while the event was being built.

An impressive stage can't fix a confusing arrival. A polished event app can't replace a person who notices a lost attendee and helps. A brilliant agenda can't compensate for a speaker who is backstage without water, a cue, or a calm answer to a last-minute question.

Content and production earn attention. What people remember is how the event felt.

The Human Layer Gets Less Rehearsal

Technology and event teams are rigorous. They rehearse the demo. Test the platform. Check the AV. Perfect the run of show.

But who rehearses the attendee experience?

Who walks the venue as a first-time guest? Who notices that registration creates a 20-minute bottleneck? Who tests whether someone can find the next session without asking for help? Who thinks about what a first-time speaker needs at 7:30 a.m. when something goes wrong?

These moments rarely appear on the production schedule, yet they shape the experience people actually live.

Arrival. Navigation. Transitions. Breaks. Speaker support. Executive care. The final goodbye.

There is a second event happening between the moments on the agenda—and that is the event attendees experience.

Hospitality Isn't Soft. It's Operational.

For some technology organizations, the word hospitality can sound soft or even off-brand.

In practice, it is anything but.

Hospitality means anticipating where people will get stuck and removing the friction before they feel it.

It looks like:

Clear wayfinding
Humane pacing and breaks
Staff who know the answers—or know who does
Speakers who feel prepared and supported
Executives who have a trusted person looking after the details
Someone empowered to make a thoughtful decision when the plan changes

None of this competes with a sophisticated technical brand. It reinforces it.

A company that creates a seamless, considered human experience is demonstrating the same competence it wants its product to represent.

Someone Has to Own the Whole Experience

The challenge is that the human experience crosses organizational lines.

Arrival might involve the venue, security, registration and event team. Speaker care involves content, stage management and AV. Executive support might involve communications, hospitality and leadership.

Everyone owns a piece. Someone needs to own the whole.

That is where experienced onsite leadership makes a difference. Not another person at the registration desk, and not a replacement for your producer or agency.

It is someone who can step back and read the room: What is about to become a problem? Where is the energy dropping? Who needs help before they ask? What decision needs to be made now?

The best onsite leaders create something every event team needs but rarely puts on the run of show: calm .

And calm is not a personality trait. It is something you can design for.

A Quick Audit of Your Tech Event Experience

Walk your next event as if you've never been there before and ask:

Arrival: How long does it take to go from the front door to feeling oriented?
Navigation: Could a first-time attendee find the next session without asking for help?
Pacing: Are breaks long enough for the lines and crowds they create?
Speaker care: Does every speaker know where to be, when to be there, and who to turn to when something goes wrong?
Executive support: Who is responsible for making a senior leader's experience seamless?
Final impression: Does the way people leave feel as intentional as the way they arrived?

The goal isn't to score perfectly.

It's to discover how much of your experience currently depend s on luck—and how much you could design on purpose.

Make the Technology Land

Human hospitality at a technology event isn't about making a demanding day a little more comfortable.

It is about impact.

When people aren't distracted by confusion, unnecessary waiting, or avoidable friction, they are more present for the content you've worked so hard to create. They absorb more. Engage more. Trust more. And leave with a stronger impression of the company behind the event.

Thoughtful hospitality doesn't compete with technology and production. It makes both land.

So here's a simple place to start:

Identify the most sophisticated part of your event—the element your team is proudest of.
Then identify the most human moment—the moment when someone felt genuinely looked after.
If there is distance between those two, that's your opportunity.

Your next event should feel as considered as it looks.