Find the friction.
Build the path forward.

Leadership becomes visible when the situation is uncertain. A team can keep moving without having every answer, but it needs to know what matters, who owns the next decision and what good performance looks like. When those things are missing, capable people spend too much of their time interpreting signals instead of doing the work.

I have led through growth, integration and turnaround situations. The circumstances differ, but one question keeps coming back: does the team understand the direction well enough to make sound decisions without waiting for the leader? A leader who becomes the answer to every question eventually becomes a constraint on the business.

Start with the outcome. Describe what the business needs to accomplish and why it matters to customers, employees and the economics of the company. Then make the tradeoffs explicit. If speed matters more than customization for a particular initiative, say so. If quality requires slowing the rollout, explain the decision. People cannot exercise useful judgment against priorities that remain inside someone else's head.

Next, establish decision rights. Which decisions belong to the team? Which need consultation? Which require executive approval? Give people room to work within those boundaries. Responsibility becomes frustrating when the person who owns the outcome lacks the authority to influence it.

Finally, be consistent in how you respond to difficult information. A leader who asks for transparency but reacts badly to bad news teaches people to manage the message. The result is a business that discovers problems later than it should. Calm, direct questions help the team understand the problem and decide what happens next.

Leadership also includes making changes when the facts demand them. Listening carefully does not mean delaying indefinitely. At some point, the leader needs to explain the choice, assign ownership and move the organization forward—even when consensus is incomplete.

A useful check for your next leadership meeting: ask each person to name the team's most important outcome, the next decision they own and the biggest obstacle they need help removing. If the answers are scattered, the first leadership task is to create clarity. That clarity becomes the foundation for stronger execution.

From the Dalton Operations & Growth Strategy editorial series.

Chaos often feels like a workload problem. The calendar is full, urgent requests keep arriving and every conversation introduces another priority. Adding effort can help temporarily, but sustained chaos usually requires changes in how the organization decides, assigns and coordinates its work.

The first step is to distinguish a real emergency from a noisy issue. A customer problem that requires immediate action should get it. A recurring problem that has become urgent for the fifth time needs a different response: an owner, a diagnosis and a change to the process that keeps producing it.

Create a short priority list for the current period. Start with the outcomes that protect the business and enable the next stage. Depending on the situation, that may include customer commitments, delivery capacity, cash collection or a critical leadership vacancy. Do not describe every worthwhile initiative as essential. A priority list only helps when it makes the choices visible.

Then create one shared view of the work. It should show the issue, accountable owner, next action, due date and decision needed. The tool can be simple. The important part is that people stop working from different versions of the situation and can see dependencies before they become surprises.

Protect a predictable decision rhythm. A brief daily review may be useful during an acute problem. A weekly operating review can help once the business stabilizes. Use those meetings to resolve blockers and make choices. A meeting that only describes the chaos consumes the capacity the team needs to address it.

Be deliberate about what stops. Leaders often approve new work without removing an existing commitment. The team then experiences every decision as an addition. If capacity is constrained, identify what can be deferred, simplified or reassigned. That is an operating decision, not a failure of ambition.

As stability returns, examine the recurring patterns. Are approvals too centralized? Are responsibilities unclear? Does a system hide important information? Do teams make promises that other teams cannot fulfill? Fixing those patterns is what makes the improvement durable.

You do not need to eliminate uncertainty to lead through it. You need enough structure for people to understand the situation, make the next decision and keep the critical work moving. Start there, then strengthen the operating model as the facts become clearer.

From the Dalton Operations & Growth Strategy editorial series.

Many businesses say they want more accountability when what they really need is clearer ownership. A team cannot consistently deliver an outcome if nobody can explain who owns it, what authority that person has or what support is available.

Accountability begins before a deadline is missed. It starts when the work is assigned. Define the outcome, the measure of success, the timing and the decisions the owner can make. Discuss the dependencies as well. An owner who needs help from three other functions needs a way to secure those commitments and escalate conflicts.

Use one accountable owner for a defined outcome. Several people can contribute, and cross-functional work often requires them to. But a list of contributors should not become a substitute for naming the person who brings the work together, identifies the obstacles and ensures that decisions happen.

Make the commitment mutual. Ask the owner to explain the plan in their own words and identify where they expect difficulty. This is the point to find unrealistic assumptions. If the scope, time or resources do not fit, resolve the mismatch before the organization treats the assignment as an agreement.

During execution, review progress against evidence. What has changed? What is complete? What remains uncertain? What decision would move the work forward? A green status label without supporting information is not enough. Neither is a long explanation that leaves the next action unclear.

When performance misses the commitment, diagnose the cause. Was the expectation unclear? Did capacity change? Did another team fail to deliver a dependency? Was a warning ignored? Or did the owner fail to act within the authority they had? Those are different problems and deserve different responses.

Accountability includes consequences, but it also includes help. A leader should remove obstacles the team cannot resolve and address repeated failures directly. Protecting people from every difficult conversation weakens trust just as much as blaming them for conditions they cannot influence.

Ownership becomes part of the culture when leaders practice it themselves. Acknowledge your decisions, explain changed priorities and honor the commitments you make to the team. The organization learns more from that behavior than from a slide describing accountability.

From the Dalton Operations & Growth Strategy editorial series.

Control what you can control is useful advice, but it needs to become more than a way to stay calm. For a business leader, it should help decide where to spend attention, what action to take and how to respond when conditions change.

Start by separating the situation into three groups: decisions you own, conditions you can influence and factors you need to monitor. You may not control demand, financing costs or a competitor's behavior. You can influence customer retention, improve response time and decide how the business allocates its capacity.

The distinction matters because teams can spend weeks debating an external problem while leaving internal opportunities untouched. A slower market may be real. It can still be useful to ask whether follow-up is consistent, proposals are clear, delivery is reliable and existing customers are being served well.

Translate the issue into operating actions. If demand is weaker, what will the sales team do differently this week? If a supplier is unreliable, who is developing alternatives? If staffing is constrained, what work will be prioritized and what promises need to change? Each response should have an owner and a review date.

Build scenarios around the factors you cannot control. Decide what the business will do if a condition improves, holds steady or worsens. Identify the signals that would trigger a change. This gives leaders a way to respond deliberately instead of revisiting the entire strategy every time a new piece of information arrives.

Be careful about confusing limited control with limited responsibility. An executive may not cause an external disruption, but the response still belongs to the leadership team. The job is to adapt the operating plan, communicate the tradeoffs and keep people focused on the work that can improve the outcome.

This discipline also helps protect energy. Teams need room to discuss legitimate concerns, but repeated conversations without a decision can become another source of friction. Close the loop: what have we learned, what will we do and what will we continue to watch?

From the Dalton Operations & Growth Strategy editorial series.

A strong hire can change the trajectory of a business. But hiring a capable person does not automatically create a capable organization. The role, authority, expectations and working environment all affect whether that person can succeed.

Begin with the work the business needs done. Describe the outcomes the role must deliver over the next stage of the company. A growing business may need someone who can build a function, introduce discipline and make decisions with incomplete information. A mature operation may need a different combination of strengths.

Avoid treating a familiar title as a complete specification. Two companies can hire a COO and expect very different work. Define the mandate, reporting relationships, decision rights and resources before searching. Otherwise the company may attract an excellent person for a role it has not actually created.

Assess candidates through relevant situations. Ask how they diagnosed a business problem, which choices they made, how they worked through disagreement and what changed after implementation. Explore what they learned when the original plan did not work. These conversations reveal judgment in a way that a list of accomplishments cannot.

Once the person joins, connect them to the real business quickly. Introduce the customer journey, operating economics, key relationships and constraints. Explain the history behind important decisions. Give them access to the people and information they need to test their understanding.

Set clear early outcomes while leaving space for discovery. A new leader needs to contribute, but immediate activity can mask a weak diagnosis. Agree on what they should understand, which decisions they should recommend and what they can reasonably implement during the first phase.

Then keep your part of the agreement. If you hired someone to recommend changes, be prepared to evaluate those recommendations seriously. If you assigned responsibility, provide authority. If priorities shift, address the consequences openly rather than judging the person against an outdated mandate.

Helping talent excel is continuing leadership work. Provide candid feedback, remove unnecessary obstacles and recognize the contributions that move the business forward. The best hiring decision becomes valuable when the organization enables the person to deliver.

From the Dalton Operations & Growth Strategy editorial series.

Outsourcing can provide useful capacity and access to talent. The result depends on the work being transferred and the way the relationship is managed. A lower quoted cost is only one part of the decision.

First, define the customer journey and the work the partner will own. Is the operation handling inbound sales, appointment setting, service requests, follow-up or a combination? Which interactions require judgment? Which need local knowledge? Where does the partner hand the customer back to your team?

Examine the current operation before asking a provider to reproduce it. Unclear scripts, inconsistent qualification, incomplete CRM records and poor handoffs will follow the work into the new arrangement. Outsourcing can make those problems harder to see if responsibilities are split across organizations.

Build the business case around outcomes as well as cost. Consider conversion, appointment quality, customer experience, rework, escalations and the management effort required. For a field service business, an appointment that never becomes productive work may be expensive even if the call itself was inexpensive.

Evaluate providers against the actual operating requirements. Review recruiting, training, supervision, quality assessment, continuity and system access. Use sample situations that reflect your customers. Understand how the provider develops its people and how your leaders will get visibility into performance.

Start with a defined pilot. Agree on the work, service expectations, reporting, escalation process and the evidence needed to expand. Keep responsibility for the overall customer experience clear. Your customers should not have to resolve the boundaries between your company and its provider.

Review the relationship through a shared management rhythm. Discuss patterns in calls, customer outcomes and handoffs. Use coaching and process changes to improve the work. A vendor scorecard should lead to decisions, not simply report numbers after the month closes.

Outsourcing is most effective when it supports an operating model that already has clear ownership. Treat the partner as part of that model. The objective is a stronger customer operation with the capacity to scale.

From the Dalton Operations & Growth Strategy editorial series.

A difficult board conversation is a test of leadership judgment. The team needs to acknowledge the performance gap, explain it clearly and establish a credible response. Defensiveness and an oversized recovery plan can both make the situation worse.

Start by agreeing on the facts. What was expected? What happened? Which measures reveal the gap? Separate actual performance from forecast assumptions and distinguish timing issues from more fundamental weaknesses. The board and management team need to be discussing the same version of the business.

Then explain the drivers. Was the miss related to demand, conversion, capacity, execution, costs or a combination? Show the connection between the operating evidence and the financial result. An external factor may explain part of the situation, but the discussion should still identify the choices management can make.

Assess the original assumptions honestly. A market entry may have been slower than planned. An integration may have required more work. A pricing change may have affected conversion. Revisiting those assumptions helps the company decide whether the response should improve execution, change the plan or reconsider the investment.

Bring a focused action plan. Identify the few changes most likely to affect the result, assign owners and establish review points. Be explicit about the resources and decisions required. A plan with twenty urgent initiatives can leave the board less confident that management understands the central issue.

Show the path from actions to outcomes. If conversion is the problem, explain the work on qualification, coaching, offers or follow-up. If capacity is the constraint, explain how staffing, scheduling or supplier changes will affect delivery. Avoid promising a financial recovery without identifying the operating changes behind it.

Establish a reporting cadence that reveals whether the plan is working. Include leading indicators where they are useful, actual results and the assumptions that remain uncertain. Agree on the conditions that would require a different response.

The objective is to restore confidence through clear judgment and visible execution. Leaders earn that confidence by telling the truth about the business, making necessary decisions and following through on commitments.

From the Dalton Operations & Growth Strategy editorial series.

Technology decisions become expensive when the business buys a platform before defining the work it needs to improve. An impressive demonstration can create confidence without proving that the system fits your operating model.

Begin with the business problem. Where is information missing? Where do people repeat work? Which customer or operating decisions are difficult because the current tools do not provide visibility? Describe the outcome you want in terms the business can measure.

Map the process before selecting the technology. Identify the users, data, handoffs, approvals and exceptions. Decide which practices should change and which requirements are essential. Automating an unclear process can make the confusion faster and more difficult to correct.

Ask vendors to demonstrate your situations. Use examples that include real complexity: multiple locations, product differences, financing, scheduling changes, customer follow-up or unusual exceptions. Have the people who perform the work participate. Their questions often expose gaps that an executive demonstration misses.

Look beyond the subscription price. Understand configuration, implementation, integration, migration, training, administration and ongoing changes. Discuss what happens when the business expands or the original vendor relationship ends. A proposal should make those dependencies and costs visible.

Validate the critical requirements through a limited proof of concept where practical. Test the hardest workflow, confirm that the required information moves correctly and examine the quality of reporting. Do not allow a successful demonstration of an easy task to stand in for evidence about the operation's most important needs.

Build an implementation plan alongside the purchase decision. Name the business owner, identify the resources, plan training and decide how adoption will be measured. The system is only useful if people can work in it and the organization can maintain it.

Technology should help the business operate better. A disciplined assessment keeps attention on that outcome and makes it easier to choose a suitable tool, negotiate a realistic scope and implement it without unnecessary disruption.

From the Dalton Operations & Growth Strategy editorial series.

A strategy can be sound and still fail to change the business. The gap often appears between the decision to pursue an opportunity and the practical work of building the capability to deliver it.

Design begins with understanding the problem and making choices. What does the customer need? Where is the opportunity? What constraints matter? Which approach fits the business economics and the organization's capacity? This work defines the direction and the tradeoffs.

Development turns those choices into an operating capability. The business needs roles, processes, systems, measures and supporting relationships. A plan to enter a new market may require recruiting, supplier access, customer support, training and delivery capacity before the first revenue target becomes meaningful.

Implementation brings the capability into use. Leaders need to align the team, coordinate dependencies, resolve obstacles and make decisions as the work meets reality. This stage exposes assumptions that looked reasonable in planning but require adjustment in practice.

The three stages need to stay connected. Someone who understands the original strategy should remain close enough to implementation to recognize when the plan needs to change. Someone doing the work should be able to explain which assumptions are no longer holding.

Use decision gates to manage the transition. Before expanding, confirm that the necessary capability exists. Before scaling a pilot, review its economics and customer outcomes. Before adding more complexity, determine whether the current model can deliver consistently. Each gate should be based on useful evidence rather than activity alone.

Keep accountability clear across the full sequence. The organization should know who owns the outcome, who contributes and who makes the decisions. A project that moves between several teams without clear ownership can lose both momentum and intent.

This is the work I enjoy most: define the path, build the capability and lead implementation. When those activities are connected, a growth plan becomes something the organization can actually deliver—and sustain.

From the Dalton Operations & Growth Strategy editorial series.