We have a ritual, my husband and I. After a meal out, on the walk home or in the subway, we debrief. And not just the food; we especially focus on the service. The way the host looked up when we walked in, or did not. Whether anyone noticed when a glass sat empty too long. The moment the energy in the room shifted and nobody on the floor seemed to catch it.
My husband works in professional hospitality. Four-star level. And here is the thing about being married to someone who does this work at that level: he never fully stops. At a dinner, he counts the staff-to-table ratio before he sits down. At a restaurant we are visiting for the first time, I will catch him watching the floor manager read the room, and he will lean over and whisper something like “they should have turned that table twenty minutes ago” or “I would have welcomed that guest differently.” He sees the craft operating in real time and cannot unsee it. There is something melancholic about it too. The person who craves hospitality most is the one who sets the bar ever so high.
I am an Agile Coach. I have written before about what I call the ‘Hype Master‘ dimension of this role; the energy, the presence, the way you set the temperature of a room when you walk into it. And I have written about soft skills before too, cataloguing the qualities that make the difference. But I want to go further than cataloguing now. I want to name something that has been bothering me for a long time.
The Agile Manifesto placed “individuals and interactions” above “processes and tools.” That was 2001. We are now 25 years later, in 2026. We have thousands of certified practitioners, hundreds of tools, and entire consulting industries built around the process layer. The interaction layer, the actual human relational craft, is still filed under “nice to have.” We are violating the Manifesto’s most fundamental value with such consistency that we have stopped noticing.
I want to name it. And I want to take a clear position.
The problem with invisible output
Here is why hard skills dominate, and it is actually not that complicated: they leave artifacts.
A velocity chart exists after the Sprint. A deployment frequency metric exists after the release. A filled backlog, a shipped feature, and a dashboard full of numbers: these things persist. Stakeholders can look at them. An investor can screenshot them. A manager can point to them in a quarterly review and say: “this is what we produced.”
Now consider what a skilled facilitator produces. They hold a room together during a Sprint Retrospective where two people are not speaking. They notice the one person who has gone quiet and creates the condition, through a single well-placed question, for them to say the thing they have been not saying for three weeks. They read the energy shift at the forty-minute mark and make a micro-adjustment that keeps the session from collapsing into compliance. The team leaves aligned, energized, carrying something real.
And then, *poof*, it evaporates. There is no artifact. The meeting happened. The calendar invite remains. What happened inside the meeting, the presence, the reading of the room, the recovery, the genuine forward motion, it leaves no trace that a dashboard can capture.
It is a structural bias toward the visible, and it shapes every investment decision the industry makes. Certifications are visible. Jira experience is visible. Facilitation as a craft is not. So we fund what we can see and call everything else supplemental.
I know this from the inside. At a software company newly acquired by investors, the kind where billability had become the organizing religion overnight, I once led a company-wide presentation on facilitation skills. I was pulled aside afterward and dressed down in front of the entire management team. Distraction from real work, I was told. Meanwhile, the same organization was haemorrhaging hours in purposeless meetings that nobody ran well, that never arrived at a decision, that people left more confused than when they entered. The form was fine. The calendar invites went out. Nobody tracked what the meetings cost in lost direction, diminished trust, and accumulated exhaustion.
I ground my teeth. My singular facilitation session was the distraction. The bad meetings were just overhead. “Penny wise, pound foolish”, I heard myself think. It left a lasting impression.
The word that licenses underinvestment
Soft skills. The word “soft” has been doing damage for years, and I am frankly done letting it.
Becasue here is what the word does: it creates a hierarchy. Hard skills are the ‘real’ ones. Certifications, tools, frameworks, metrics. Soft skills are the ‘supplemental’ ones. The nice-to-haves. The things you develop once the real stuff is covered. Squishy. Something to sprinkle on top to make the product more palatable, more human-seeming. Not the core. Never the core.
I vouch for the exact opposite. I believe soft skills are the core, the load-bearing structure, and in my humble opinion everything else is furniture.
You see the damage in job descriptions that list “strong communication skills” under ‘nice to have’ while “experience with Jira” is under ‘required.’ You see it in certification programmes that spend forty hours on process mechanics and forty minutes on psychological safety. You see it in the retrospective that ends early because the team “didn’t have much to say” and the Scrum Master who did not know how to create the conditions for saying it.
Patrick Lencioni identified the absence of trust as the foundational dysfunction in any team, with every other failure (fear of conflict, lack of commitment, avoidance of accountability, inattention to results) stacking directly on top of it. The relational work required to address that foundation is not a supplement to agile practice. It is the precondition for it! And the word “soft” has been quietly licensing us to underprepare for it, year upon year, upon year.
I refuse to use it anymore, because it is inaccurate.
What the restaurant floor teaches
My husband’s craft has a name in the literature I care about. Priya Parker calls the host’s obligation ‘generous authority’. Not holding space passively, but actively leading it, making decisions that serve the whole room even when individual guests would not make those decisions for themselves. The generous host does not ask what everyone wants. They already know what the room needs. They create the conditions for it. Every single shift.
Jan Gunnarsson’s Hostmanship framework names six components of this disposition: serving, responsibility, caring, knowledge, dialogue, and seeing the big picture. What strikes me, every time I map these against my own facilitation practice, is that the architecture of a well-run retrospective sits directly on top of all six. The opening that signals to the team that this room is different from your daily work. The question sequence progresses from observation to interpretation to commitment. The closer that sends people out carrying something specific. None of that happened naturally. It was by design. It was hosted.
The best ceremonies I have run felt, to the people in them, like they simply emerged. Easy, safe, generative. When my husband recovers a table that started badly (i.e. a slow greeting, a mix-up with an order) and the guests leave delighted, they think the evening was always going that way. They do not see the micro-interventions that redirected it. That invisibility is a craft at its most refined.
The receipts the discourse should check
Google’s Project Aristotle found that the single strongest predictor of team performance was not skill mix, experience level, or process maturity. It was psychological safety. The capacity to speak up without being punished for it.
Amy Edmondson is precise about what this means, in a way the broader Agile discourse rarely is: psychological safety is a structural condition, a climate in which interpersonal risk-taking is possible. It is not warmth. It is not the absence of tension. Creating that condition is demanding, sustained, skilled work. Patrick Lencioni (The Advantage, 2012) and Sybil Keller’s research on organisational health makes the same point from a different angle: a cohesive, trusting team will outperform a technically excellent one, given time.
The workforce data is moving in the same direction. IBM’s research established that technical skills carry a half-life of roughly two and a half years. Relational and social skills decay significantly more slowly. The World Economic Forum’s Future of Jobs Report 2025 confirms the trajectory at scale: leadership and social influence rose 22 percentage points in employer prioritisation between 2023 and 2025 — outpacing even AI and big data. Dependability, attention to detail, and quality control fell. The procedural layer is being automated. What remains is the human one. The Agile industry has been slow to reckon with what that means.
What AI is about to confirm
It is 2026. AI handles the procedural, the repetitive, the information-dense. It writes the summary of your Sprint Review. It tracks metrics and flags blockers. It runs a decent portion of what used to pass for backlog refinement.
What it does not do is read a table in thirty seconds. What it does not do is notice that one person has gone quiet in a retrospective and make the low-key, timely, specific intervention that brings them back in a correct way. What it does not do is create the room in which someone finally says the true thing they have been not saying for six weeks.
The hardest thing in this work is not organizing the call. It is holding it together. It is digging through the whys. It is helping a room move forward when it would rather stay comfortable. Presence. Purpose. Those are not personality traits; they are skills. Learnable, practicable, refinable skills that the industry has systematically underfunded because they do not show up on a dashboard.
The Agile Manifesto named this priority in 2001. Individuals and interactions over processes and tools. That value is not becoming less relevant as AI scales. The opposite; it is becoming more essential than ever. The automation is arriving. The human layer is what remains.
My position
I believe the relational, hospitality-driven competencies at the heart of agile facilitation are structurally harder to develop, harder to sustain under pressure, and more resistant to automation than the technical practices they have been subordinated to.
I believe the word “soft” is a category error that costs practitioners their argument, costs organizations their best teams, and costs the field its own stated values.
I believe that reading a room, recovering energy, making a stranger feel they belong: these are not nice-to-haves. They are the work.
My husband evaluates himself against them after every shift. I do the same after every ceremony I facilitate.
Soft is not a side event. It is not something to sacrifice when the board wants cold hard output. “Soft” is the hardest thing we do.
I am done calling it soft. I am calling it craft. And I am calling on the Agile community to start investing in it like that is true.
—
This blog post is part of a series on Hostcraft: the discipline of facilitating through the full repertoire of the skilled host. Presence. Reading the room. Recovering energy. Creating the conditions in which the true thing can finally be said. None of that is personality, and all of it is practice.