A shared map is not yet a shared service
Three neighbouring cooperatives offered a way to extend our reach. We began with seven agreed handoffs and left five unresolved, keeping the partnership smaller than its first map.
The combined map was persuasive. Three neighbouring cooperatives already served places that Qemravi did not, and our own network could offer something useful to them. Put the territories together and a larger proposition appeared almost immediately. I understood why colleagues wanted to begin with that picture. It showed a possible future in a form everybody could recognise. What it did not show was the work required when a parcel crossed from one organisation's responsibility into another's. Existing regional presence was an asset, but the handoff needed its own agreement.
Look for the handoff inside the geography
Our 2022 review identified twelve proposed service handoffs across the partnership. The choice of that unit changed the discussion. Instead of asking whether the partners collectively reached a place, we asked what had to be understood for a particular piece of work to move between them. Commercial terms, operating responsibility and the treatment of an unresolved question could not be inferred from a coloured area on a map. Each organisation remained an enterprise with its own owners and authorised decisions. A shared ambition did not make those boundaries disappear.
I supported₹42 lakh of review work with the appropriate partner representatives and professional owners. The programme was intended to establish a basis for a defined proposition, not to absorb the neighbouring organisations or declare all their capacity available to Qemravi. That distinction mattered in a member-owned setting. Cooperation can create an option that none of the enterprises could develop as economically alone. It also requires the parties to understand what they are contributing and what they retain. Growth should not depend on one participant quietly speaking for responsibilities that another has never agreed to transfer.
The growth sponsor wanted to introduce the broader offer early and resolve individual questions as enquiries arrived. There was a reasonable commercial argument behind that approach. A long preparation period can lose attention, and actual customer interest can reveal which handoffs deserve the most work. I did not want the review to become a search for perfect certainty before any learning was possible. The question was whether a public proposition would imply a service basis that did not yet exist, and whether the partners had an intelligible way to keep the limited next stage within what they could support.
Keep each partner visible in the proposition
Farida wanted the responsibilities settled for the work being offered. I agreed, and seven of the twelve handoffs reached an agreed basis. Five remained unresolved. We recommended a limited next stage through the responsible approvals, confined to the agreed scope. The result was deliberately smaller than the first combined map. It did not prove delivery performance, national coverage or complete integration of the three partners. Seven agreements answered a preparation question. The operating result of using them would require its own account rather than inherit success from the fact that the papers had been settled.
A federation can be misunderstood if its presentation becomes indistinguishable from a single operator. Customers need a clear service account, and that may require a coordinated public explanation. But internal clarity still matters:which organisation decides, who accepts the work and what happens when the agreed scope ends? Strategy should make those questions understandable to the people approving the proposition. It should not treat organisational detail as something that can always be repaired later by a common brand or a friendly relationship between executives. Good relationships help resolve problems;they do not replace a defined basis for the work.
The same point applies to capacity. A partner's regional activity may be commercially impressive without meaning that its resources are available whenever the new proposition needs them. The cooperative must understand the actual commitment rather than count all partner activity as part of its own capability. I did not want our growth paper to borrow scale from organisations whose working owners had their own priorities. A useful partnership recognises that independence and finds a workable arrangement within it. The resulting promise may be narrower, but it is a promise the participants can discuss and improve together.
This approach retained coordination cost. A single-network presentation can make the strategy look simpler than the operating relationship will be. Several organisations may need to revisit a change, and a question that seems small centrally may be important to one partner's members. Those are not automatically reasons to reject federation. They are part of the comparison with building a larger owned network or remaining within the current reach. I wanted the board to choose the form of growth with those consequences visible, rather than discover them after the partnership had been described as an easy extension.
Let the unfinished boundary shape the launch
The five unresolved handoffs did useful work in the decision. They told us where the proposition should stop for now. An unresolved condition is not necessarily a permanent rejection of the relationship. It can identify the question that must be answered before another stage becomes appropriate. We kept those handoffs outside the offer instead of allowing the launch's momentum to make them seem informally available. That gave the partners a route for further work without requiring them to defend an ambiguous promise already made to a customer.
There was a commercial cost in that restraint. The limited next stage offered less immediate reach and a less dramatic story. Some opportunities might go elsewhere while the partners continued their work. I accepted that possibility and did not invent a saving from opportunities we had not pursued. The benefit claimed was a clearer agreed basis at seven handoffs, with the remaining five explicitly unfinished. A strategy account should be able to describe that result without converting preparation into an operating outcome or implying that every delayed opportunity would have been unsuitable anyway.
For a board, the central question is what the partnership has actually made possible. What is agreed, what is merely expected and what remains outside the offer? Which organisation holds each material responsibility? What coordination cost accompanies the new reach? Directors do not need to negotiate every handoff to examine those issues. They can ask whether the investment recommendation has distinguished a combined geography from a supported service, and whether the owners of the participating enterprises understand the commitments being described in their name.
I would put the handoff account beside the first map in our next partnership discussion. That would preserve the map's value as a way to see an opportunity while preventing it from becoming the main evidence that the opportunity is ready. Federation can let regional enterprises serve customers together without surrendering their identity. Its credibility depends on the work between them being as carefully considered as the territory around them. Seven agreed boundaries gave us a place to begin. The five unfinished ones told us what the next stage still needed to earn.