.svg)
Every organization hosts meetings. Very few know how their meetings actually happen: the workflows, dependencies, tools and friction points that shape each meeting, from the moment it is planned to the days after it ends.
Meeting Journey Mapping changes that. It is a structured way to make the as-is journey visible (how meetings are scheduled, prepared and run today) and to design the to-be journey (how they should happen). It connects business logic, technology, policies and people, and aligns them toward one goal: a workplace where meetings hold, and where the people behind them are supported, not frustrated.
This post walks through the whole process, step by step, the way we run it with customers at AskCody. Feel free to borrow it and try it yourself.
What Is Meeting Journey Mapping?
Meeting Journey Mapping is a facilitated workshop where every team involved in meetings maps, together, how a meeting really moves through the organization: who does what, in which system, and where the hand-offs happen, before, during and after the meeting. The result is one shared map of today's journey, the friction points in it, and a design for how the journey should run. At AskCody, it is the starting point for every implementation.
Why Meeting Journey Mapping Matters
It reveals the invisible work. Behind every meeting lies a web of actions, decisions and rules, from booking rooms and catering to visitor management and IT setup. Mapping exposes what really happens behind the scenes, and puts everyone involved in meetings on the same page, or rather, the same map.
It connects silos. Facilities, IT, HR and the business units each hold a piece of the puzzle. Mapping brings them together to uncover the dependencies between their systems and teams, and to agree on one process.
It drives better technology adoption. A new meeting management solution rolled out without understanding the current journey meets resistance. Mapping makes the technology fit your people and processes, not the other way around.
It gives change a foundation in facts. Mapping shows where time is lost, where friction sits and where automation and simplification will have the biggest impact.
How Meeting Journey Mapping Works, in Six Steps
Every map follows the same six steps. The illustration below plays them in order on the four lanes we use most often, the host, reception, the service provider (catering, AV and setup) and facility staff, across the meeting's timeline: before the meeting, the day of the meeting, after the meeting and the days after.
Step 1: Bring Every Team In
Meeting Journey Mapping is not a Facilities or an IT exercise. It is a joint exploration of how meetings touch the entire organization, so the room needs everyone who plans, supports or depends on a meeting:
Facilities and Real Estate: how physical space supports meeting types and usage patterns.
IT and Digital Workplace: the systems, integrations and constraints that enable or block the journey.
HR and Culture: how people work, meet and collaborate.
Executive Assistants and Office Managers: the frontline experts who feel the friction first.
Reception: how guests are expected, welcomed and handed over to their host.
Catering, AV and Support Staff: the logistics that make meetings work.
Security and Compliance: the rules for access, data handling and visitors.
End Users: the employees, managers and teams who plan, attend and run meetings every day.
This mix makes sure every perspective is represented, from policy to practice, and from system to user experience. If you can, bring a sponsor from leadership too. Their presence turns a mapping session into a conversation about workplace strategy, and opens doors a project team cannot open alone.
Step 2: Start With Curiosity
Organizations often rush into new workplace or meeting management solutions with a long list of assumptions. Those assumptions tend to come from decision rooms, not real rooms. They come from policies written years ago, not from the lived experience of the people who plan, run, support and attend meetings every day.
Meeting Journey Mapping asks for something different: curiosity. Step into the organization with open eyes and an open mind, and look for how meetings actually happen, not how we believe they happen.
There is a famous moment in the series Ted Lasso, where Ted plays darts with Rupert. Ted reflects on all the people who underestimated him because they made assumptions instead of asking questions, and the lesson he draws is to be curious, not judgmental. Meeting Journey Mapping relies on the same idea. When we slow down, observe and ask the right questions, the real meeting journey becomes visible, and we start solving real problems instead of imagined ones.
Curiosity is the discipline that turns mapping from a checklist into a discovery process. The 25 questions we start from are further down in this post.
Step 3: Map the As-Is Journey
Now draw the journey as it runs today. Give every role its own lane, and put time along the top: before the meeting, the day of the meeting, after the meeting and the days after. Then follow a real meeting through it. Who books the room, and where? When is catering ordered, and by whom? How does reception learn that a guest is coming? Who approves what, and who resets the room afterwards?
Write down every step and every hand-off, including the ones that happen in an email, a phone call or a spreadsheet. Those are often the most important ones on the map, because no system knows they exist.
Step 4: Find the Friction
With the as-is journey on the wall, mark where it breaks. The friction points we find most often:
Manual workarounds: the shadow processes, extra lists and confirmation calls that "make meetings happen".
Ghost meetings: rooms that are booked, and nobody shows up.
Changes that never arrive: the meeting moves, and nobody tells the kitchen, reception or the AV team.
Broken ownership: steps that belong to everyone, and therefore to nobody.
Do not solve anything yet. Name each friction point, place it on the lane where it happens, and agree on what it costs: in time, in experience, or in trust that the meeting will work.
Step 5: Design the To-Be Journey
Now design the journey as it should run, with the friction removed. Every friction point gets a resolution, and the resolutions become recommendations in three areas:
Governance: the rules, roles and policies that decide who can book what, when services must be ordered, and how visitors are handled.
Optimization: the steps to remove, automate or hand to the right person, so the journey has fewer hand-offs and fewer places to fail.
Value creation: what the new journey makes possible, for the business, for the people who run meetings, and for guests and visitors.
Then prioritize. Agree on the few changes that matter most, and on the one you start with.
Step 6: Configure and Set Up AskCody
The to-be journey becomes the configuration. We set up AskCody to match it, starting with the Exchange integration, so the meeting in Outlook stays the one record every team works from. Then come booking rules and policies that put your governance into the calendar, meeting services such as catering, AV and setup that follow the meeting when it changes, and visitor management that tells reception and the host who is coming.
That is why the map comes before the setup. AskCody is configured for how your meetings should run, not for the assumptions anyone brought into the room.
What You Walk Away With
One shared map of how meetings run today, agreed by every team.
The friction points, placed where they happen and prioritized.
A to-be journey, with recommendations for governance, optimization and value creation.
A setup plan for AskCody that follows the to-be journey.
A common language across Facilities, IT, HR and the front line, which often lasts longer than the map itself.
When to Run a Meeting Journey Mapping Workshop
At the start. Meeting Journey Mapping is part of planning and preparation in every AskCody implementation, before the platform is set up. See how getting started with AskCody works.
And again later. Workplaces change. New room types, new services, a new office or a new way of working all change the journey, and yesterday's map stops matching today's meetings. Meeting Journey Mapping workshops are part of Premium Support, and you can also book them on their own.
What to Explore? 25 Questions to Start Mapping the Meeting Journey
Curiosity is the key to understanding how meetings work in your organization, or at least how they should work.
We use these questions, or some of them, to guide discovery sessions and workshops when we define the as-is and to-be meeting journeys. Get inspired, and try them yourself.
What types of meetings take place most often across the organization?
How are meeting rooms and spaces booked today?
What systems or tools are used to schedule meetings, and how are they connected?
Who can book rooms, and are there any approval processes?
How do people find available rooms or spaces that meet their needs?
What data is used to judge room utilization or meeting success?
How are recurring meetings managed, updated or canceled?
What are the typical friction points when scheduling a meeting?
How is catering requested, approved and delivered? Are there deadlines or rules for when to order, and how are they managed?
How are AV and IT services coordinated or requested for meetings?
What happens when meetings are rescheduled or canceled, and how is that communicated?
How are visitors managed before, during and after meetings?
What policies exist around booking etiquette or space usage?
How are no-shows and ghost meetings handled today?
What integrations exist between Outlook and Exchange and the room booking or visitor systems?
Who owns the meeting experience end to end, and where does ownership break down?
What metrics are used to evaluate meeting efficiency and space utilization?
How do employees report issues with rooms, AV or services?
What feedback do we capture from employees about their meeting experiences?
How do hybrid or remote meetings differ in setup, support or complexity?
What manual workarounds or shadow processes exist to "make meetings happen"?
What rules or constraints (IT, HR, security) shape how meetings are organized?
How does the meeting experience differ across locations or departments?
What would the ideal meeting journey look like if no constraints existed?
What impact would a frictionless meeting journey have on productivity, culture and experience?
Then add your own. The best questions usually come from the second answer, not the first.
From Mapping to Transformation
A well-facilitated Meeting Journey Mapping session does more than produce a map. It builds shared understanding. It starts conversations between teams that rarely talk. It breaks down silos. And it lays the foundation for meaningful digital transformation, where business logic, user experience and technology work in harmony.
When you understand how meetings actually happen, you can finally design how they should happen.
Meeting Journey Mapping, Answered
What is Meeting Journey Mapping?
Meeting Journey Mapping is a facilitated workshop where every team involved in meetings maps how a meeting really moves through the organization, before, during and after it, finds the friction points, and designs how the journey should run.
Who should take part in Meeting Journey Mapping?
Everyone who plans, supports or depends on meetings: Facilities and Real Estate, IT, HR, executive assistants and office managers, reception, catering, AV and support staff, security and compliance, and end users. A sponsor from leadership adds weight.
What is the difference between the as-is and the to-be journey?
The as-is journey is how meetings are scheduled, prepared and run today, workarounds included. The to-be journey is how they should run, with the friction resolved through recommendations for governance, optimization and value creation.
When should you run a Meeting Journey Mapping workshop?
At the start of an implementation, before the platform is set up, and again whenever the workplace changes: new room types, new services, a new office or a new way of working.
Is Meeting Journey Mapping part of AskCody?
Yes. It is the starting point for AskCody implementations. Meeting Journey Mapping workshops are part of Premium Support, and you can also book them on their own.
Key Takeaways
- Meeting Journey Mapping makes visible how meetings really run across every team, before, during and after the meeting, and designs how they should run.
- It follows six steps: bring every team in, start with curiosity, map the as-is journey, find the friction, design the to-be journey, and configure and set up AskCody to match it.
- The most important hand-offs are often the ones no system knows about: the email, the phone call, the spreadsheet.
- The map comes before the setup, so the platform is configured for how meetings should run, not for assumptions.
