The Business Should Be Stronger Than Its Busiest Person.

01 / What the saying asks of us

Coming together is an action with consequences.

Ní neart go cur le chéile is often expressed more briefly in English as “Strength in unity.” The fuller wording retains a useful challenge: strength depends on people bringing their efforts together. It points toward something people do, rather than a flattering description they award themselves.

We should give that distinction some room. An organization can put “teamwork” on its careers page while making cooperation difficult every working day. Departments receive competing targets. Staff cannot see the information they need. Managers ask people to take ownership but retain approval of every meaningful choice.

The resulting friction is then described as a culture problem. Sometimes it is. Sometimes the culture is responding quite logically to the way the work has been designed.

A sales team rewarded exclusively for volume will feel pressure to sell more. A delivery team already at capacity will feel pressure to control what arrives. A founder who intervenes whenever a decision looks unfamiliar teaches both groups to wait for the founder. Nobody needs to be malicious for the organization to become exhausting.

The proverb gives us a better question than “Why can’t everyone be more collaborative?” What would make their efforts fit together? That leads toward priorities, incentives, information, and responsibility. It moves the discussion closer to something a leader can change.

It also leaves room for independence. People do not need identical personalities or opinions to contribute to a shared result. A useful team can contain a careful skeptic, an imaginative designer, a commercially minded operator, and someone who asks where the numbers came from. The value lies partly in the differences they bring.

Irish history and contemporary life contain conflict, exclusion, and competing interests as well as solidarity. A proverb does not erase that complexity or describe every Irish person. Its value here is as an invitation to examine cooperation, with enough honesty to ask when it works and who carries its cost.

02 / County Wexford

The work was always more substantial than the slogan.

At Johnstown Castle in County Wexford, the Irish Agricultural Museum preserves tools, machinery, and accounts of rural life. Its displays include dairy equipment, threshing machinery, and representations of workshops such as the blacksmith’s forge and cooper’s workshop. These objects make the practical demands of work visible.

They are useful to think with because they interrupt a romantic picture of community as people merely feeling warmly toward one another. A crop has to be gathered. Equipment has to function. A container has to hold what someone puts in it. Skills and timing make the difference between good intentions and a completed task.

The Irish term meitheal is associated with a working group and with traditions of neighbors helping one another with substantial tasks. Its appeal is practical: a job beyond one person’s available capacity becomes possible through coordinated effort. The word continues to appear in contemporary projects organized around shared contribution.

For a business owner, the useful analogy begins with the task. What needs to happen? What skills does it require? Which parts depend on one another? How will people know when the job is done well enough to move on?

If those questions are unresolved, adding more people can increase confusion. A larger group needs coordination, and coordination requires attention. A company can have twelve helpful people and still leave the customer waiting because every one of them reasonably believes the next step belongs to someone else.

Expertise belongs to the people who understand the work.

The range of skills represented in a rural museum also resists the myth of the universally capable individual. The blacksmith, cooper, farmer, and equipment maker have different knowledge. Their work connects without becoming interchangeable.

Modern businesses should be equally precise. An excellent designer may not be the right person to own commercial positioning. A strong salesperson may not understand the implications of a custom delivery promise. A founder may know the customer exceptionally well and still benefit from someone who can examine process, economics, or measurement more systematically.

Recognizing those distinctions is respectful. It allows people to contribute what they know while making the limits of each role visible. “We all wear many hats” can describe healthy flexibility. It can also mean nobody knows which hat comes with the authority to make a decision.

The question I would bring from Wexford into the office is simple: have we assembled the capabilities the work requires, and have we made their relationship clear? That is a more useful starting point than asking everyone to work harder at the same confused arrangement.

03 / County Tipperary

Thurles: even talented teams need to agree on the game.

The GAA’s own account of its foundation describes an Easter Monday match in 1884 between the Metropolitans and Killiomor of Galway. Play repeatedly stopped because the teams were using different rules. The experience helped convince Michael Cusack that Irish sports needed standardized rules and an organizing body.

Later that year, the association’s founding meeting took place at Hayes’s Commercial Hotel in Thurles on November 1. The history places organization alongside enthusiasm. People cared about the games; a shared structure helped make coordinated participation possible.

That interrupted match is a remarkably good image for departmental conflict. Both teams can be trying sincerely to succeed while disagreeing about what counts as a legitimate move. Effort does not resolve incompatible rules.

In business, one department may consider a project ready when the creative work is approved. Another considers it ready when the offer is priced. A third is waiting for the service team to confirm capacity. Everyone reports progress using a different definition, and the executive dashboard produces the reassuring color green.

Then the customer arrives and discovers that green is apparently a matter of interpretation.

Shared definitions reduce unnecessary arguments.

What qualifies as a good lead? What must be true before a proposal is sent? When can sales promise a delivery date? Which changes require customer approval? What does completion include?

These questions deserve explicit answers because they define the work between roles. Agreement does not need to become a fifty-page policy for a six-person business. A short set of usable standards can resolve more friction than another meeting about alignment.

The distinction matters in marketing strategy. A campaign may produce inquiries successfully while the organization has never agreed which inquiries it wants. Marketing calls the campaign effective. Sales calls the leads weak. The disagreement may begin in the brief, before either team performs its work.

Useful standards also have a revision process. The first definition will not anticipate every situation. People need a way to raise an exception, examine its consequences, and decide whether the rule should change. Otherwise the shared standard gradually becomes an obstacle everyone learns to work around.

The historical lesson is specific enough to travel: participation becomes more productive when people understand the rules governing their shared effort. Talent still matters. So does knowing whether everyone is playing the same game.

04 / Dublin and a distributed archive

The knowledge needs a life beyond the person who holds it.

The National Folklore Collection at University College Dublin preserves oral tradition and cultural history across manuscripts, photographs, recordings, and other materials. Its account describes the work of collectors and archive staff who documented knowledge through fieldwork across Ireland.

There is a profound idea in that effort. Something valuable can be widely known within a small circle and still be vulnerable to disappearance. Preserving it requires someone to recognize its value, ask questions, record it, and make it possible for another person to find and understand.

In an organization, the same vulnerability can exist in less dramatic form. A senior employee knows why a customer needs a particular arrangement. The founder remembers which estimate requires an extra allowance. A coordinator knows which supplier can solve an unusual problem. That knowledge may be essential even if it has never appeared in a procedure.

When someone says, “Just ask Sandra,” they may be describing an efficient shortcut. If the entire organization says it all day, they are describing a knowledge system with one very busy search engine.

Recording information is only part of making it useful.

Meitheal Dúchas.ie invites volunteers to transcribe material from the Schools’ Collection so it can be searched as text. Participants can improve one another’s work, and the project supplies guidance and review for new contributors. Collective contribution is supported by a method.

My business interpretation is that access and quality need to be designed together. Saving information in a folder is not enough if nobody can find it, understand whether it is current, or decide when it applies. The file exists. The capability may not.

A useful internal guide explains the decision as well as the steps. What are we trying to achieve? Which facts matter? What are the common exceptions? When should someone stop and ask for help? Who keeps the guidance current?

Those details allow another person to exercise judgment. A rigid script may work for a routine situation and fail the moment a customer says something unexpected. Shared knowledge should help people understand the work well enough to respond intelligently.

This is where digital transformation advisory can become more substantial than choosing software. Searchable information, sound ownership, and usable workflows can help distribute capability. Installing a platform does not decide whose knowledge is missing or whether anyone has time to maintain it.

05 / When commitment becomes a constraint

The founder may be protecting the quality and limiting the capacity.

It is easy to tell a founder to let go. It is more useful to understand why they are holding on. Perhaps a previous delegation went badly. Perhaps the standards exist mainly in their own judgment. Perhaps the business has never given another person enough time, information, or authority to become dependable at the work.

The founder may be right that nobody else can currently make the decision as well. The strategic question is what the organization is doing to change that.

If the answer is nothing, every additional customer increases the load on the same person. Growth becomes a test of endurance. The founder’s vacations become experiments in remote access, and the team learns that the fastest route through any uncertainty is another message marked “quick question.”

Quick questions have an impressive collective ability to consume an entire day. They arrive individually dressed as harmless little requests and depart carrying the afternoon.

Look for the decision that keeps returning.

A founder-dependency problem often becomes visible in repetition. The same discount needs approval. The same type of complaint escalates. The same proposal requires rewriting. The same customer exception catches the team by surprise.

Each repetition offers a chance to transfer judgment. Why did the founder make that choice? Which facts changed the answer? What would have made a different response appropriate? Can someone else explain the reasoning and apply it to the next case?

That is more demanding than telling a colleague to copy what happened last time. It also creates more lasting value. The organization begins to learn a decision process instead of accumulating isolated instructions.

Being less necessary to routine work can make leadership more valuable.

There is an emotional transition here. A founder may experience constant requests as proof of importance. Fewer requests can feel, briefly, like a loss of relevance. But the point is to make their contribution available where it matters most.

Customer insight, major relationships, difficult tradeoffs, and the direction of the business may deserve the founder’s attention. Repeatedly approving something another capable person could decide under clear standards consumes that attention.

A healthier organization gives the founder a choice about where to contribute. It also gives other people room to become more capable. Shared strength expands the work people can do; it does not require the founder to disappear.

06 / What effective cooperation requires

Give the team more than responsibility.

“You own this now” is incomplete if the person cannot access the relevant information, change the process, or make the necessary decisions. Responsibility without those conditions often amounts to becoming the new person who has to explain why nothing moved.

I would examine three elements together: the result the person owns, the decisions they can make, and the support available when the situation exceeds those decisions. The boundaries should be understandable enough to use during a normal working day.

People need practice before you can expect confidence.

A useful transition can move through several stages. First, the experienced person explains a real decision. Next, the colleague proposes a decision and discusses the reasoning. Then the colleague decides within agreed limits, with selected cases reviewed afterward.

This sequence allows judgment to develop while consequences remain manageable. It also gives the founder evidence that capability is growing. Trust does not have to be a leap across a canyon when you can build a reasonable bridge.

The time for that development has to come from somewhere. If the person already has a full workload, adding a major responsibility means changing priorities, providing support, or reducing other work. Calling it an opportunity does not create more hours in the week.

A specialist should strengthen the whole arrangement.

Outside help can be valuable when the missing capability is clear. The engagement should explain which decisions the specialist owns, which knowledge should remain with the business, and how the internal team will work with them.

For example, fractional chief marketing officer leadership can give a company senior responsibility for marketing direction and coordination when that is the gap. It is a different commitment from providing a recommendation or delivering a defined project.

The arrangement should make the business more capable of acting. If every uncertainty simply moves from the founder’s inbox into the consultant’s inbox, the organization may have relocated its dependency without addressing it.

07 / An illustrative business scenario

The company that hired a team and still could not take a Friday off.

Consider a hypothetical professional services business with a founder, several specialists, and an operations coordinator. Demand is healthy. The founder writes or rewrites most proposals, approves unusual pricing, answers delivery questions, and personally reassures clients whenever something changes.

The team is capable, but the founder knows things they do not. Certain customers need additional preparation. Some requests look simple and usually expand. A particular promise should only be made when a specific specialist has confirmed availability.

The business has never made those distinctions explicit. Instead, everyone sends the work back to the founder. The team waits, clients wait, and the founder concludes that hiring has failed to create enough capacity.

Start with a small sample of real decisions.

I would begin by examining recent proposals and the changes the founder made. Which edits improved clarity? Which protected scope? Which reflected a genuine customer requirement? Which were personal preferences that did not materially affect the result?

That last distinction matters. A founder is allowed to have preferences. A business should know when it is delaying a customer to satisfy one.

The review might reveal that most proposals fall into a few recognizable patterns. The team could document the scope, required information, pricing considerations, and circumstances that call for escalation. One person could own preparing the proposal; another could check delivery feasibility before a commitment is made.

Nothing in that table guarantees a result. The point is to make the work testable. The business can try the changes on suitable cases, review what happened, and improve the arrangement before extending it.

The founder still has work to do.

The transition requires restraint. If the founder rewrites every acceptable decision simply because they would have expressed it differently, the team receives a contradictory lesson. Officially, it has authority. Practically, it is expected to anticipate the founder’s exact preference.

That creates anxious imitation. People spend energy guessing what will survive review instead of applying the agreed standards to the customer’s problem.

A better review asks whether the decision met the objective, respected the boundaries, and used the available evidence sensibly. If it did, let it stand. If it did not, identify the gap and help the person understand how to improve.

The successful outcome would be a business where routine proposals can move without the founder, difficult cases arrive with useful analysis, and the founder’s expertise is applied more deliberately. The team has gained capability. The founder has gained time for work only they should be doing.

08 / Shared effort needs shared respect

Cooperation cannot mean the most dependable person absorbs everything.

Every organization seems to have someone who will make sure the thing gets done. They notice the missing detail, remind the distracted colleague, recover the awkward handoff, and stay late when the plan was unrealistic.

That person is valuable. The danger is that their reliability becomes the organization’s substitute for improving the process. They become the permanent emergency service for problems that stopped being emergencies months ago.

A leader should ask who carries the invisible work. Who explains things repeatedly? Who trains newcomers? Who resolves confusion between teams? Who maintains the shared knowledge? If those contributions are essential, they deserve time, recognition, and an appropriate place in the role.

Reciprocity does not require identical contributions.

People can contribute different skills and still participate fairly. Fairness means the expectations are understandable, the workload is considered, and the benefits of cooperation do not depend on a few people quietly exhausting themselves.

The rural idea of shared assistance becomes distorted when transferred into a workplace as an excuse for unlimited availability. Employment carries responsibilities around pay, time, and role clarity. A leader should never use the language of community to make reasonable boundaries feel disloyal.

Likewise, unity should leave room for disagreement about the work. A specialist who explains that a promise is unrealistic may be protecting the shared result. A colleague who identifies an unfair workload may be helping the organization preserve the capability it relies on.

Make contribution visible without turning everything into a contest.

Some forms of individual measurement can discourage cooperation if they ignore the work between people. Someone who helps colleagues improve may appear less productive under a narrow count of personal output. A department may hit its own target by passing difficulty to the next team.

Useful KPI dashboard design considers the result across the process. Track what reaches the customer, what needs rework, and where decisions wait. Examine individual measures in that context rather than assuming that a collection of good departmental scores guarantees a good overall experience.

The objective is to understand the work well enough to improve it. A metric should help someone ask a useful question, including whether the system rewards the behavior the business says it wants.

09 / A practical place to begin

Choose one recurring decision and make the business better at sharing it.

A founder-dependency problem can look so large that the response becomes another ambitious transformation plan. Start with a decision that occurs often, has manageable consequences, and consumes more founder attention than it should.

Gather a few recent examples. Ask the founder to explain the reasoning. Identify what another person needs to know, which boundaries matter, and when help should be requested. Then give a capable colleague time to practice with feedback.

A useful first version can fit on a page. Describe the outcome, relevant facts, decision owner, limits, escalation route, and review approach. The document should be short enough to use and clear enough to improve when it encounters reality.

Let the review show whether capability is growing.

Look for more than a reduction in questions. People can stop asking because they understand the work, or because they have learned that asking is unwelcome. Review the quality of the decisions, the exceptions being noticed, and the results reaching customers.

If questions increase temporarily during the transition, that may be useful. Previously hidden uncertainty is becoming visible. Deal with it while the stakes are manageable, and incorporate what is learned into the guidance.

Progress might mean fewer avoidable escalations, better proposals on the first pass, shorter delays, or a second person who can explain why the decision was made. Those are concrete signs that knowledge is becoming organizational capability.

Build something other people can carry forward.

There is a generous ambition in building a business that can make good use of other people’s abilities. The founder’s knowledge becomes a starting point for more capability. A colleague’s skill gains room to develop. A customer receives consistent care even when the original decision maker is unavailable.

Wexford’s working history directs attention to the skills a task requires. The GAA’s foundation story shows why participants need shared rules. The folklore archive and its community transcription project show the work involved in making knowledge available beyond its original setting.

None of those lessons makes cooperation effortless. They make it more concrete. People need a purpose, a useful way to contribute, and enough structure for their efforts to connect.

A founder can remain deeply important without being required for every routine step. A strong business gives their contribution room to matter while allowing other people to do meaningful work. That is an achievement worth building toward, and a much better reason to gather a team than simply acquiring more people to answer messages from the airport.

If you are working through a question about shared responsibility, Rob welcomes a thoughtful conversation.

10 / Frequently asked questions

The proverb and the practical questions behind it.

Explore the history

Working life, shared rules, and collective memory.

These sources support the article’s historical examples. The professional services scenario is hypothetical, and the business interpretations are original applications of the cultural material.

• Irish Agricultural Museum, Johnstown Castle: rural working life, equipment, and specialist crafts in County Wexford.
• The GAA’s foundation history: Michael Cusack, the 1884 rules disagreement, and the founding meeting in Thurles.
• The National Folklore Collection: the preservation and organization of Irish cultural knowledge.
• Meitheal Dúchas.ie: community transcription, shared contribution, and access to archival material.