Between Saying and Doing Lies the Sea

“We should do that” may be the most affordable sentence in business. It requires no budget, no additional staff, no uncomfortable discussion about priorities, and no explanation of who will be answering questions when the new system develops a personality.

The sentence can produce a wonderful feeling of progress. Everyone leaves with the satisfaction of having supported an excellent idea. Then Monday arrives. The people expected to execute the idea still have their existing jobs, the decision maker is unavailable, and the project’s first significant dependency turns out to be a person who was never invited to the meeting.

Italian has a beautifully compact observation for this situation: Tra il dire e il fare c’è di mezzo il mare. Between saying and doing, there is the sea.

I appreciate the scale of that image. It does not suggest that implementation is a minor administrative inconvenience. There is water to cross. You will need a destination, a means of getting there, people who know what they are doing, and a reasonable willingness to acknowledge the weather.

As the person behind Paper Boat Media, I am also professionally obligated to appreciate a useful maritime metaphor. Even so, a logo does not excuse me from checking whether the boat can carry the work.

Treccani includes the saying in its discussion of proverbs. Its enduring usefulness comes from recognizing a common human problem. We can understand something, agree with it, and sincerely intend to act without yet having created the conditions that make action possible.

This article follows that problem through Florence, Venice, Cremona, and Ivrea, then into the everyday work of leadership and growth. It also follows it into luxury travel, where the distance between a beautiful promise and a beautifully delivered experience becomes intensely personal. A traveler does not experience your strategy document. They experience the day you helped create. And it follows the same question into the markets where businesses operate, because an execution plan that ignores place can be as incomplete as one that ignores people.

The sea inside the saying

A good idea can be simple to describe and difficult to realize. “Make the experience easier.” “Open another market.” “Give customers a better way to buy.” “Use technology to reduce unnecessary work.” Each sentence may point toward something valuable. None tells us exactly how to get there.

The difficulty lives in the details that the sentence leaves out. Which customers? Which part of the experience? What does easier mean? Who will change the process? What must continue working while it changes? How much uncertainty can we reasonably carry?

The proverb invites us to respect that distance. Treating execution as an afterthought can be a way of avoiding responsibility for the actual implications of an idea. The person making the promise receives the moment of enthusiasm; someone else receives the calendar.

That does not mean ambition should become smaller by default. It means ambition needs enough substance to become more than a demand. A leader can set a difficult goal and still take responsibility for the means, choices, and tradeoffs required to pursue it.

We should also avoid using an Italian saying as an excuse for a stereotype about Italians. The gap between intention and action has no particular passport. It can be found in any organization with meetings, limited resources, and a surprisingly optimistic interpretation of the word “just.”

“Just integrate the systems.” “Just expand into another city.” “Just have the team handle it.” The word often marks the precise point where the speaker has stopped describing the work.

The useful response is curiosity. What lies between the current situation and the intended result? Which part do we understand? Which part needs discovery? What should happen first so that the next step becomes possible?

Those questions help distinguish a challenging plan from an incomplete promise. They give capable people something they can work with.

Florence: design the means to build the thing

Florence offers an extraordinary example of ambition requiring a construction method. The dome of Santa Maria del Fiore was built between 1420 and 1436 under Filippo Brunelleschi’s direction. The Opera di Santa Maria del Fiore’s official account explains the significance of creating the immense masonry structure without the conventional full timber support that such a span presented difficulty providing.

The construction problem extended beyond the shape of the finished dome. Materials needed to reach the work. Workers needed a viable sequence. The structure had to remain stable as it developed. An inspiring image of completion would not answer those questions on its own.

Museo Galileo’s account of the dome emphasizes the role of construction-site organization and machines capable of lifting substantial weights. The cathedral organization’s discussion of the worksite, people, and machines makes the same larger point: the means of building were part of the achievement.

That is the connection I would bring into a strategy conversation. Have we designed only the destination, or have we designed enough of the route to make the destination plausible?

A business may want a more consistent customer experience. Achieving it might require shared information, clearer responsibilities, training, and changes in how exceptions are handled. The attractive final state depends on several supporting capabilities that may not exist yet.

A company may want to launch a new service. Before marketing can responsibly promise it, someone must determine scope, delivery capacity, pricing logic, response expectations, and the conditions under which the service cannot be provided well.

Those supporting decisions can feel less exciting than the idea itself. They are also where much of the value is created. A good execution leader makes the invisible requirements visible before they become expensive surprises.

The historical achievement also depended on skilled workers whose individual names are less famous than the architect’s. Modern organizations should remember that. Vision becomes real through people who solve detailed problems, often far from the stage where the vision was announced.

When someone says a project needs more preparation, the useful question is what that preparation enables. Some planning delays action unnecessarily. Other planning creates the means to act at all. Knowing the difference requires understanding the work.

Venice: the voyage begins long before the departure

At Venice’s Arsenale, shipbuilding connected ambition to a large productive operation. La Biennale di Venezia’s account of the site describes the historic complex where the Venetian Republic’s fleets were built and identifies the Corderie with the production of maritime ropes and cables.

That physical setting helps correct a romantic picture of commerce as a sequence of bold departures. A ship needs a great deal before anyone can confidently announce where it is going. Materials, workmanship, equipment, coordination, and maintenance belong to the story.

The modern business equivalent is familiar. A company can announce geographic expansion in a sentence. Serving the new market requires an operating model. Who handles inquiries? What can be delivered? How will the promise change across distance? Which relationships are needed before the first transaction?

Marketing can create interest faster than an organization can build the capacity to serve it. That sounds like a pleasant problem until customers begin experiencing the gap. Demand is useful when the business can respond well enough to turn it into a relationship worth keeping.

There is a second lesson in the maritime image: being busy at individual tasks does not guarantee that the whole operation is progressing. Many teams can be productive while one unresolved dependency prevents completion.

If the offer is unclear, a better website may make the confusion more attractive. If sales has no agreed response process, additional inquiries may produce additional disappointment. If fulfillment cannot support the promise, a successful launch can accelerate the consequences.

Execution therefore requires attention to sequence. What must be true before the next step becomes useful? Which preparation has the longest lead time? Which decision is holding up several other decisions?

Asking those questions is a form of respect for the people doing the work. It prevents them from being asked to compensate indefinitely for an operating problem with personal effort and extraordinary patience.

Cremona: tools matter, and judgment makes them useful

Cremona’s violin-making heritage offers a different scale of execution. Here, the relationship between intention and outcome can be examined through a maker’s materials, tools, and accumulated judgment.

The city’s account of the Museo del Violino describes instruments associated with the Amati, Stradivari, and Guarneri families, alongside more than 700 drawings, forms, and tools from Stradivari’s workshop. The surviving working objects help us see a practice behind the celebrated result.

For me, the tools are a useful part of the story because they resist the idea that excellence is simply an inspired moment. A finished instrument has a history of decisions embedded in it. The maker had to work with particular materials and respond to what the work revealed.

Owning a tool does not grant the judgment associated with its best use. A business can buy the same software as a successful competitor and still lack a coherent process. It can adopt the vocabulary of an experienced team without understanding the decisions that vocabulary was designed to support.

This is especially visible when organizations expect technology to supply missing clarity. A project-management platform can record an owner. It cannot make the owner’s authority real. An automation can move information. It cannot settle a disagreement about what the information means.

Skill also includes knowing what deserves attention now. Experienced people recognize when a small inconsistency is harmless and when it suggests a larger problem. That discernment develops through practice, feedback, and exposure to consequences.

Organizations should make room for it. Give capable people access to the problem, rather than reducing them to the final instruction in someone else’s incomplete plan. Ask what they see. Ask which assumption they would check. Let their knowledge influence the design before their task becomes a rescue operation.

There is a commercial lesson here for creative and technical work alike. Clients are paying for more than the visible output. They are often paying for the judgment that makes the output appropriate, usable, and worth maintaining.

This distinction matters when craftsmanship becomes part of a travel experience. A visitor curious about violin making deserves an encounter shaped around the craft itself: what the maker is willing to share, what the visitor hopes to understand, and what the workshop can accommodate. Selling “authenticity” without considering the working life of the person providing it creates an awkward transaction. Good experience design gives the maker a voice in the promise.

Italy and luxury travel: the beautiful promise has to survive the actual day

Italy gives this proverb a particularly rich application in luxury travel. Think of the difference between describing an extraordinary afternoon in Florence and delivering one. The description can be written quickly. The afternoon requires decisions about pace, expertise, access, transport, rest, and the interests of the people who will actually be there.

A photograph can promise a mood. An operator has to organize the conditions in which that mood has a chance of existing. Somewhere between those two responsibilities, a guest may discover that the “leisurely” itinerary has the cardiovascular expectations of a military selection course.

My luxury travel consulting and strategic advisory work connects directly to this question: how does a business turn a compelling idea into an experience it can deliver well? For a travel company, destination specialist, or villa business, the commercial promise needs the same disciplined execution as any other ambitious strategy.

Florence: understanding what deserves the afternoon

Imagine a hypothetical couple planning a visit to Florence. One has spent years reading about Renaissance architecture. The other enjoys art but would rather have a thoughtful conversation over lunch than complete a compulsory march through every available masterpiece. A weak brief reduces both people to “luxury travelers” and assembles expensive activities. A useful brief identifies what would make the day worthwhile for each of them.

The dome we discussed earlier now has two roles. It is a historical achievement worth understanding, and it is a test of the contemporary business arranging the visit. Has the proposed experience been explained accurately? Have physical requirements been checked against the guests’ needs? Is the timing realistic? Does the person presenting the history know how to connect it to these particular visitors?

Those questions are less photogenic than the skyline. They determine whether the skyline becomes part of a wonderful memory or the background to an argument about whose idea this was.

The leadership lesson is that quality begins in the brief. When a business learns what the customer actually values, it can make intelligent choices about what to include, what to explain, and what to leave out. Adding another activity is easy. Taking responsibility for the shape of the day requires judgment.

Venice: every transfer is a promise crossing a boundary

Consider a hypothetical Venice arrival arranged through several independent partners. The travel advisor has one confirmation. The accommodation has another. The transfer provider has a departure time. Each party may have completed its own task, yet the traveler still needs the parts to connect.

Who notices when the arrival time changes? Who tells the next provider? Which person can approve a revised arrangement? What instructions does the traveler receive, and are those instructions understandable after a long journey? The point is to rehearse the dependency before a guest becomes responsible for discovering it.

This is the Arsenale lesson translated into hospitality. The departure is visible; the preparation makes it possible. A premium experience needs someone who understands the whole sequence and can see where a small failure will travel downstream.

The same question belongs in luxury hospitality and private club consulting. A reservation, welcome, meal, activity, and departure may sit under different managers. The guest still has one day. The operating model should account for that continuity.

The people who make a place meaningful belong in the plan

A destination is also somebody’s working home. The craftsperson, guide, cook, driver, and property team have knowledge and responsibilities that an itinerary cannot simply absorb by calling itself exclusive. Their participation needs workable timing, clear expectations, fair commercial arrangements, and room to say what is feasible.

Suppose a specialist can provide an exceptional conversation for four interested visitors but cannot deliver the same encounter for twenty people on a rigid schedule. That limit is information about the product. A growth plan should understand it before selling more of the experience than the people behind it can sustain.

There is a useful connection to Ivrea here, too. The conditions around the work influence the quality of the result. If a business depends on partners repeatedly rescuing unrealistic promises, it has placed its reputation on a foundation of borrowed patience. Eventually someone will need that patience back.

Market the experience your operation can stand behind

For a luxury travel business, the proverb can become a practical review of its own website. Take the promises one at a time. What does “personalized” require the team to learn? What does “seamless” require partners to coordinate? What must be confirmed before an experience can responsibly be described as private?

The exercise should produce specific answers. A process owner. A confirmation step. A capacity limit. An exception that the customer needs to understand. Otherwise the adjectives are simply enjoying themselves while operations does the worrying.

Useful content can make those distinctions clear before the inquiry. Explain who an experience suits, what preparation matters, how the business approaches changes, and where local expertise influences the plan. Give a prospective client enough substance to ask a better question. A beautiful page earns more credibility when its claims have something solid beneath them.

That connects Italy’s lessons in craft and execution to the wider luxury brands and experiences market. The compelling story and the delivered result should belong to the same business. Their relationship deserves attention before more demand makes any mismatch harder to repair.

For organizations in Orlando or Daytona Beach, the application is local as well as international: examine how the promise passes from marketing into the actual visit. For businesses considering cross-border relationships through markets such as Dubai, investigate the partners and delivery requirements that the new relationship would introduce. The route needs its own preparation.

Ultimately, a luxury travel brand puts its judgment into someone else’s calendar. That is a considerable responsibility. An afternoon cannot be delivered again exactly as it was meant to happen. Taking execution seriously is one way of respecting the time the traveler has entrusted to you.

Ivrea: the working conditions belong in the strategy

In Ivrea, Piedmont, the industrial landscape associated with Olivetti provides a wider view of what an organization chooses to design. UNESCO’s account of Ivrea as an industrial city of the twentieth century includes industrial buildings alongside housing and facilities for social services, reflecting a vision of the relationship between production and community.

The Adriano Olivetti Foundation’s presentation of Ivrea gives additional detail about workers’ housing, a library, social services, and the built environment. These choices made ideas about organizational responsibility tangible.

We do not need to turn that history into a claim of perfection to learn from it. The useful question is whether the conditions in which people work are treated as part of execution or as an unrelated concern to be addressed after productivity improves.

A company asking for excellent work must consider what makes excellent work possible. Are priorities understandable? Is the workload feasible? Can people find the information they need? Is there room to learn a new process before being judged for using it slowly?

Many implementation failures are described as resistance when the people involved are reacting to a practical problem. The new tool adds work. The promised training never happened. A formerly simple decision now requires approval from someone in another time zone.

Listening does not mean accepting every objection as decisive. It means examining whether the objection identifies something the plan omitted. A person who explains why the current design will fail may be contributing more to the project than someone who enthusiastically approves every slide.

The leadership implication is concrete: include working conditions in the plan. Training time, access, support, authority, and capacity need to exist in the schedule and budget. Otherwise “our people are our greatest asset” becomes a decorative sentence placed above an increasingly exhausted group of people.

Ownership needs authority, and priorities need consequences

One of the fastest ways to discover whether a plan is real is to ask who owns the outcome. If the answer is a department, a committee, or “all of us,” ask a second question: who can make the decisions needed to keep the work moving?

Shared contribution is valuable. Shared ambiguity is expensive. A project can involve many people while still needing a clear person responsible for coordinating the outcome and escalating decisions they cannot make.

That responsibility must come with access and authority. Giving someone a deadline while withholding the ability to resolve scope, obtain input, or get an answer from leadership is a particularly elaborate way to manufacture frustration.

The owner does not have to perform every task. They need to understand how the tasks connect, where the risks sit, and which decisions require attention. They also need a reliable route to the people who control resources and priorities.

This is where executive sponsorship becomes more than a name on the kickoff slide. A sponsor should help resolve conflicts, make consequential tradeoffs, and protect the work from contradictory instructions. A senior person who approves the project and disappears has provided a blessing, which may be comforting but is difficult to schedule.

Priorities are revealed by what changes when they conflict. If a new initiative is important, which existing work receives less attention? If the answer is nothing, the organization may be assigning additional obligations while describing them as a new focus.

That is a conversation I want to have early in executive strategy and advisory work. A roadmap cannot compensate for leadership refusing to choose. The same capable team cannot give its full attention to every initiative at once.

Useful clarity sounds like: “This quarter, this outcome takes precedence. These two activities will pause. This person owns delivery. These decisions come to this sponsor within this time frame.” There is enough structure in that statement for someone to act.

People can still disagree about the choice. At least they know which choice has been made. Execution becomes much harder when each department quietly operates from a different interpretation of what matters most.

The budget conversation includes time, attention, and the work you stop doing

A project budget often captures the most visible purchase and misses the work around it. The subscription has a price. Implementation, cleanup, training, testing, transition, and ongoing ownership require resources too.

Imagine replacing a customer-management system. The licensing fee is only one part of the commitment. Records need review. Processes need decisions. Integrations need attention. Employees need to learn the new system while continuing to serve customers.

If that labor is assigned to people already working at capacity, its cost does not disappear. It shows up in delays, overtime, reduced attention elsewhere, and mistakes caused by trying to do too much simultaneously.

A responsible plan makes those costs visible. How much internal time is required? Which skills are missing? What support will the team need? Which work can stop during the transition? What must remain dependable throughout?

Capacity also depends on concentration. A person with ten open projects may have hours available on paper and very little uninterrupted time to complete a difficult task. Fragmented attention can make a straightforward piece of work take weeks.

That is why adding tasks to a board is not the same as creating progress. The board can become a beautifully organized record of overcommitment. Its labels may be excellent. The work still needs someone with time to do it.

There is room for ambition here. A challenging project can justify investing in new capability, bringing in outside help, or redesigning the sequence. The important point is to acknowledge the requirement rather than assume motivation will fill the gap.

Different engagement models serve different needs. Fractional marketing leadership can provide ongoing functional ownership when that is the missing capability. A defined project can address a bounded problem. Retained advice can support decisions without implying day-to-day management. The role should match the work the business actually needs.

Finally, reserve some capacity for what you have not yet discovered. A plan that depends on every assumption being correct and every contributor being continuously available has confused precision with resilience.

The sea between departments can be surprisingly deep

Some projects struggle because no individual task looks especially difficult. Marketing can generate the inquiry. Sales can hold the conversation. Operations can deliver the service. Finance can issue the invoice. Yet the experience between those steps is inconsistent.

The problem often lives in the handoff. What information moves forward? What does the next person need? What has already been promised? What happens when the case does not fit the normal pattern?

A handoff is successful when the next person can act appropriately. Sending an email proves that an email was sent. It does not establish that the recipient understood the decision, had the necessary information, or knew the work was now theirs.

Consider a sales team promising a customized service. Operations receives a signed agreement, but the special assumptions from the sales conversation never arrive. The customer experiences a broken promise while both teams believe they followed the process.

The remedy begins by looking at the work from end to end. Describe what should be true at the transition: agreed scope, relevant customer information, exceptions, timing, and an acknowledged next owner. Keep the requirements proportionate to the risk.

The same applies to outside vendors. A designer cannot responsibly solve a positioning problem that nobody has resolved. A developer cannot infer a business rule that departments disagree about. A consultant cannot make an unavailable decision maker available through exceptional formatting.

Clear handoffs are not an insult to skilled people. They let skill focus on the real problem instead of reconstructing context. The purpose is to reduce avoidable guessing, not to document every possible human action.

Choose a method that helps people finish useful work

I am a Certified Scrum Master and PMP, with experience in Kaizen, RUP, and Waterfall. Those methods give me different ways to think about planning, improvement, uncertainty, and delivery. The useful question is which approach fits the problem in front of us.

A project with stable requirements and costly physical dependencies may need substantial sequencing before work begins. A new digital service with uncertain user needs may benefit from smaller increments and frequent feedback. A recurring operational problem may need careful observation and focused improvement.

The method should make the work more understandable. If the organization spends more energy performing the method than learning or delivering, the method has acquired an unfortunate side business.

The official Scrum Guide connects work to a Product Goal and describes a Definition of Done that makes quality expectations explicit. Even outside Scrum, the broader questions are useful: what are we working toward, and what must be true before we call this piece complete?

For a new service page, “done” might include accurate positioning, usable mobile presentation, functioning inquiry routing, and a person prepared to respond. The text being approved is one milestone. The customer being able to use the complete path is another.

For a reporting project, completion may require more than a dashboard loading successfully. The measures need shared definitions, reliable inputs, an owner, and a decision they inform. A report that nobody trusts or uses remains an unfinished business capability, however polished the charts.

Useful methods also create a rhythm for surfacing impediments. A meeting should help decide or unblock something. Repeating that a dependency is unresolved, week after week, does not become more productive because the meeting is standing up.

Be flexible about the mechanics while remaining clear about responsibility. Teams can adapt a workflow when they understand its purpose. They struggle when the purpose is hidden behind a ritual nobody feels authorized to question.

The route changes with the market

Geographic expansion is an especially revealing example of the proverb. It is easy to say, “We should sell there.” The work begins with understanding whether the offer, sales process, delivery model, and relationships can support that decision.

Distance can affect scheduling, travel, follow-up, and the economics of smaller engagements. A buyer in a new territory may need different evidence before trusting the same service. The useful question is what changes for this particular business and customer.

Remote delivery can remove some friction. It does not remove the need for availability and clear responsibility. A client still needs to know who responds, who decides, and what happens when an issue crosses working hours or organizational boundaries.

The announcement should follow enough preparation to make the opportunity credible. Otherwise the business has promoted a destination before deciding how to reach it.

A practical example: the expansion that looked like a marketing project

Consider a hypothetical specialist service company in Central Florida. Leadership wants to enter a new territory, increase qualified inquiries, and establish the company as a credible option for larger customers. The initial request is for a website update and a campaign.

Those may be useful deliverables. Before building them, I would ask what must happen after someone responds. That question often reveals the real size of the project.

First, define the promise the company can deliver

Which service will be offered? What scope is appropriate? What response can the company sustain? Does the new territory change travel time or staffing needs? Which requests should be declined or referred?

A clear promise helps everyone. Marketing can explain the offer accurately. Sales can qualify inquiries consistently. Operations can prepare for the work. Customers can understand whether the service fits their needs before investing time in a conversation.

Second, make the decision process visible

Name the person responsible for the expansion and identify who approves changes to scope, resources, and timing. Bring the people responsible for selling and delivering into the conversation early enough to influence the plan.

If leadership wants a launch date that conflicts with readiness, surface that conflict plainly. The options might include a narrower initial territory, a smaller offer, additional support, or a later launch. Pretending all constraints can remain unchanged is not another option; it is simply a deferred decision.

Third, prepare a complete path for the first customer

Build the materials and process together. The service explanation, inquiry form, routing, response, qualification, proposal, and delivery handoff should describe the same business. Each transition should give the next person what they need.

Work through a realistic example before announcing availability widely. If an inquiry arrives tomorrow, who sees it? What do they say? Where is the relevant information recorded? How does the customer learn what happens next?

Fourth, launch at a scale that allows learning

A controlled initial scope can reveal where the process needs adjustment without placing the entire organization under avoidable pressure. Record questions, response times, fit, and the work required to deliver.

The initial goal is to establish a useful operating capability. If the business cannot handle the first reasonable level of demand consistently, additional reach may simply expose more people to the unfinished parts.

Fifth, connect the evidence to the next commitment

Review both commercial results and delivery requirements. Which opportunities fit? What effort did they require? Where did the process stall? What changed after the team began using the new approach?

KPI and dashboard design can help make these questions visible. The measures should guide the next decision about scope, investment, or improvement. A report that only congratulates the launch team has a limited shelf life.

This example shows why a marketing request can become an execution problem. The website and campaign matter, but their usefulness depends on the capabilities around them. The sea is crossed by connecting those pieces.

The launch is the beginning of use

Organizations often treat launch as the finish line because it is visible and easy to celebrate. The product goes live. The new process is announced. The team receives a message thanking everyone for the hard work.

Then people begin using it, which is when many of the most useful questions finally become concrete. Someone encounters an exception. A customer misunderstands an instruction. A report reveals an inconsistent definition that had remained hidden while the old process depended on individual memory.

Adoption deserves its own plan. Who needs to use the new approach? What will they stop doing? What support will they receive? Who observes the difficulties and has authority to improve them?

Training should reflect actual tasks. A tour of every menu may demonstrate that the software contains menus. People still need to know how to complete the work they are responsible for and what to do when the normal path fails.

There is also an emotional side. A new system can make an experienced employee feel temporarily less capable. The person who knew how everything worked now has to ask basic questions. A good implementation makes room for that transition without treating it as a character flaw.

Invite practical feedback and distinguish different concerns. “I preferred the old system” may express familiarity. “This step requires information we do not have until later” identifies a design problem. Both deserve listening; they call for different responses.

Decide how the old process will end. If everyone continues both indefinitely, the organization has doubled the work while calling it modernization. A transition may require overlap, but overlap should have a purpose, an owner, and a condition for ending.

Maintenance belongs here too. Who updates the content, reviews the data, handles exceptions, and checks whether the service still fits the promise? A capability becomes dependable when the business can keep it useful after the people who launched it return to other work.

This is why I treat digital transformation as organizational work as well as technical work. The system becomes valuable through the people and processes that use it.

Change the route without losing the destination

Execution is often described as following the plan. That is part of it. Another part is recognizing when new information makes the original plan less useful.

A dependency may take longer than expected. Customer feedback may reveal a different need. A supplier may be unable to meet a requirement. The team may discover that one part of the scope contributes little value compared with the effort it consumes.

A strong execution leader can adjust the route while preserving clarity about the intended outcome. That requires a distinction between what is essential and what was simply the first proposed method.

If the goal is to make a service easier to request, the particular form design is negotiable. If the goal is to establish a profitable new territory, a launch date chosen for convenience may be negotiable. If the goal itself no longer makes sense, leadership should be willing to reconsider it rather than demand increasingly expensive loyalty.

Changes should be explicit. What did we learn? What are we changing? What does that affect? Who agrees to the tradeoff? These questions prevent adaptation from becoming a quiet accumulation of additional work.

The same care applies to deadlines. Some dates are genuinely fixed because of an external commitment. Others are preferences. Treating every date as immovable can make a team hide risk instead of helping resolve it.

Honest execution reporting distinguishes completed work, work in progress, and unresolved decisions. “Nearly done” is not particularly informative when the remaining piece determines whether anyone can use the result.

Leadership needs enough visibility to act, and the team needs enough safety to provide that visibility. A person should be able to say, “We need a decision this week or the next milestone moves,” without being accused of insufficient enthusiasm.

A plan that can survive Monday morning

Before leaving a strategy conversation, I want the important decisions to be clear enough that people can begin. The plan can be concise. It must still answer the questions that turn agreement into coordinated work.

These questions work at different scales. A small business may answer them in one focused session. A complex organization may need several people and more detailed analysis. The objective is enough clarity for the work, rather than complexity for its own sake.

I also like to ask what could make the plan fail quietly. An unavailable approver. A data source nobody owns. A sales promise that exceeds delivery capacity. These are easier to address while they are still questions than after they have become someone’s emergency.

A plan should leave people with a next action they understand and can actually take. If the meeting ends with broad agreement and no change in behavior, the organization may have enjoyed a discussion rather than made a commitment.

Good ideas deserve the care required to make them real

Tra il dire e il fare c’è di mezzo il mare. There is something generous in taking that distance seriously. It respects the idea enough to give it a route and respects the people enough to acknowledge the work.

Florence reminds us to build the means to build. Venice reminds us that a voyage depends on an operation. Cremona reminds us that tools become useful through judgment. Ivrea asks whether the conditions around the work support the people expected to do it.

Luxury travel makes the same obligation tangible: the care described before booking has to reach the guest through the people, decisions, and coordination behind the journey. The modern application is practical. Make the choice. Assign real responsibility. Provide capacity. Connect the handoffs. Learn from use. Adjust the route when necessary. Carry the commitment beyond the moment when it was exciting to announce.

The same discipline matters in a local Florida business and an organization working across national borders. The details change with the market, the people, and the problem. The obligation to connect the promise to a workable plan remains.

Frequently asked questions

What does “Tra il dire e il fare c’è di mezzo il mare” mean?

It literally means “Between saying and doing, there is the sea.” The Italian proverb expresses the difficulty that can separate an intention from its realization. In business, it is a useful reminder to plan the work required to deliver a promise.

How does this Italian proverb apply to luxury travel?

Luxury travel depends on delivering the experience described before booking. The proverb highlights the work between that promise and the actual journey: understanding the traveler, confirming arrangements, coordinating partners, respecting local expertise, and giving someone responsibility when plans change.

Why do good business strategies fail during execution?

Common problems include unclear ownership, conflicting priorities, insufficient capacity, unresolved dependencies, weak handoffs, and inadequate support after launch. Some strategies also rest on assumptions that need revision once the work begins.

What is the difference between strategy and execution?

Strategy establishes the choices and direction intended to achieve an outcome. Execution organizes and performs the work needed to realize it. The two inform each other because implementation reveals constraints and opportunities that may require strategic adjustment.

How does geography affect execution?

A new market can change buyers, relationships, delivery requirements, service coverage, and decision processes. A company should investigate those differences before assuming that its existing offer and operating model will transfer unchanged.

Can a fractional CMO help with execution?

A fractional CMO can provide ongoing marketing leadership, coordinate priorities, and connect strategy to delivery when that role fits the engagement. Project work and retained advisory serve different needs. Responsibilities and authority should be agreed explicitly.

Why should an execution plan include adoption and maintenance?

A launch does not establish that people can use a new capability consistently. Training, support, ownership, feedback, and ongoing maintenance help the work remain useful after the initial project ends.

Further reading: history, craft, and the work behind the result