Guide · organisations
Skill Swap Projects for Companies: Collaboration, Tourism, Resilience
Skill swap projects between companies are a different animal from everything else on this site, which is about individuals in a room. They are longer, more formal, and aimed at a different outcome. That outcome is resilience — the ability of a sector to keep functioning when the ground shifts under it — and that is worth more to the companies involved than any individual skill transferred.
The distinction is not academic. An individual skill transfer is measured by whether somebody can now do a thing. Resilience is measured by whether the organisation still functions when the person who could do that thing leaves, or when the channel it depended on stops working. Those two objectives lead to different project designs, and most cross-company exchanges are designed for the first while being justified with the language of the second.
Skill swap projects between companies are best understood through a real example, because it shows both what makes collaboration durable and where this kind of project usually goes wrong. Treated properly they are a resilience strategy rather than a training budget line.
Why Companies Run Skill Swap Projects at All
The obvious reason is cost: training staff by exchanging expertise with another company is cheaper than buying it. That is true and it is not the interesting reason. Cost alone would argue for cheaper courses, not for exchange, and organisations that go into this to save money tend to treat it as procurement and get a procurement outcome.
The interesting reason has nothing to do with budgets. It is that ongoing professional development inside a single organisation tends to circulate the same assumptions, and no amount of spending fixes that, because the money buys more of the same perspective. Companies in the same sector accumulate the same blind spots, and an exchange between them is one of the few mechanisms that reliably introduces a genuinely different method. The real change comes from continuous formation of professionals through an innovative methodology of exchange between companies rather than inside them.
That is why skill swap projects between companies belong in the same conversation as any other resilience strategy, and not in the training budget. It is a resilience argument, not a training argument. A sector where practitioners have seen several ways of working recovers from disruption faster than one where everybody was taught the same single way.
A Tourism Collaboration Across Six Organisations
One project took exactly this approach in the tourism sector. Six different organisations from several European countries took part:
- Sextaplanta (Spain)
- Rinova (UK)
- Dimitria (Greece)
- EdiTC (Cyprus)
- Folkuniversitetet (Sweden)
- Chamber of commerce (Spain)
The participation of Sextaplanta was vital to the project’s success. It is a company that actively promotes resources for distributing hotels and apart-hotels in the digital world, which is precisely the kind of specific operational knowledge that does not travel between organisations by accident.
The mix matters as much as the number. Two commercial companies, a training institution, a chamber of commerce and sector specialists is not a tidy set of peers — and a project made only of direct competitors, or only of training bodies, tends to produce agreement rather than exchange.
Geography is doing work here too. Partners in five countries cannot default to the assumption that everybody already handles a problem the same way, because they demonstrably do not: booking practices, seasonal patterns, regulatory expectations and customer behaviour all differ enough that the differences have to be discussed rather than assumed away. A project run between six organisations in one city would have been cheaper to schedule and would have surfaced far less.
The asymmetry is deliberate as well. A chamber of commerce and a hotel-distribution company do not have comparable expertise; they have complementary expertise, and the exchange runs in both directions for different reasons. Projects assembled from organisations of the same type and size tend to produce a shared position paper, which is a different and much less useful output.
What the Project Was Actually For
The aim was to go deeper into the continuing development of tourism professionals. Rather than a single course, the work was structured as an exchange carried out in stages across different periods, so that participants took a method back to their own organisation, used it, and returned with what happened.
Continuing development is the phrase to hold onto, because it is what distinguishes this from the training most sectors actually buy. A course is a fixed body of material delivered once to whoever is available that week. Continuing development assumes the practice itself keeps moving, which in a sector where distribution channels and customer behaviour change every few years is simply true. An exchange tracks a moving practice; a syllabus written last year does not.
That staged shape is the part worth copying. A one-off exchange between companies produces enthusiasm and a report. An exchange with a return leg produces evidence, because somebody had to try the method in their own building and report back on it failing.
The tourism sector is a reasonable test case for this. It is seasonal, it is exposed to shocks it cannot control, and its skills are distributed unevenly between large operators and small independents. Any sector with those three properties is a candidate for the same treatment.
The unevenness is the specific thing an exchange addresses. A large operator has people whose entire job is one function — distribution, revenue management, digital presence — while a small independent has one person doing all of it alongside running the business. Conventional training sells the same course to both and suits neither. An exchange lets the independent see how the function is actually organised at scale, and lets the operator see decisions being made without the apparatus, which is frequently the more useful direction.
Staging it across periods rather than as a single visit is what converts that into anything durable. A method observed once is a story told back at the office. A method observed, tried at home for a season, and then discussed again with the people who use it daily is the only version that produces a change anybody can point to a year later.
Resilience Is the Outcome Worth Measuring
Skill swap projects between companies are usually justified on cost and then assessed on satisfaction, which measures neither the cost saving nor the resilience. If resilience is the actual objective, the questions to ask a year later are more awkward and more useful: which practices from the other organisations are still in use, and who inside the company can now do something they could not before?
Collaboration of this kind also fails in a predictable way, and it is not lack of goodwill. It is that nobody owns the return leg. The exchange visit gets scheduled because it is an event; the follow-up does not, because it is admin. Naming a person responsible for the second half at the point the project is signed off is the single highest-value administrative decision available.
The second failure is that the knowledge leaves with the person. One employee attends, learns something real, and takes it with them when they change job eighteen months later, and the organisation is exactly where it started. The defence is unglamorous: send two people rather than one, and require that whatever comes back is written down somewhere colleagues will find it. An exchange whose output lives only in one person’s head has bought a training course, not resilience.
The third is measuring the wrong thing at the wrong time. Satisfaction is measured at the end, when everybody is well disposed and nothing has been tried yet. The questions worth asking arrive a year later and are uncomfortable by design: what are we doing differently, who can now do something they could not, and what did we try and abandon? The last one matters most. A project that produced no abandoned attempts almost certainly produced no attempts.
For the individual-scale version of the same mechanism, the methodology guide covers objectives and assessment, and the Brighton archive is ten years of the informal end of the same idea.
None of this requires a funded programme, which is the assumption that stops most organisations trying it. The example above had six partners across five countries because it was set up as a formal project, but the mechanism it used is available to any two companies in the same city that do adjacent work and are not competing for the same contract. One afternoon in each other’s building, a named person on each side, one thing each tries afterwards, and a conversation a season later. That is the whole structure, and it costs two afternoons.
The version at individual scale is the same idea again, and it is what the rest of this site documents: a room, two people describing their own work, and the same thing next month. The Brighton archive ran for a decade on no budget at all. The difference between that and a cross-company project is formality and horizon, not principle. Both are trading expertise instead of buying it, and both are more durable than training because what comes back has already been tested by somebody who had to make it work.