The familiar word that wasn't so familiar

Accountability is one of those words that sounds wonderfully clear until you ask ten people to define it. In a leadership conversation, a group can agree that accountability needs attention and still be talking about entirely different problems. One person is thinking about missed deadlines. Another is thinking about uneven standards. Someone else is thinking about whether leaders follow through on their own commitments.

Before the solution, the definition

I believe that when a word becomes a recurring organizational complaint, the first useful question is not always 'How do we fix it?' Sometimes it's 'What exactly do we mean?' Ask people to describe what they see, hear and experience. Listen for whether the concern is about clarity, consistency, ownership or trust. The differences are not distractions. They are the diagnosis.

Accountability begins at the top

A leader cannot credibly ask a team to take ownership while treating their own commitments as optional. Expectations need to be visible, standards consistent and follow-through observable. When people say accountability is missing, they may be describing an absence of trust rather than an absence of rules.

The thought worth keeping

Getting everyone to use the same word is not the same as getting everyone to share the same understanding. Define the expectation, agree on what it looks like in practice, and then make it measurable. The most useful leadership conversations often begin when we stop assuming we already agree.

The number is not the whole story

When a business needs to reduce costs, payroll often becomes an immediate focus. It's visible, measurable and relatively easy to model. But a reduction in payroll expense is not the same thing as an improvement in business performance. Labor also supports revenue, service, safety and the capacity to deliver what customers actually buy.

Look at the relationship, not just the line item

I start by examining labor alongside revenue trends, overtime, vacancies, scheduling patterns and operational demand. Where are we paying a premium because positions remain unfilled? Which roles directly support sales? What happens to service or throughput when staffing changes? The right question is not simply 'How much can we remove?' It is 'What happens to the rest of the business if we do?'

Challenge the inherited operating model

Cost pressure can also expose habits that have become mistaken for requirements. Before eliminating capacity, ask whether a task, service standard or workflow still serves its original purpose. Some standards are essential; others may be expensive traditions. A redesign can protect the customer experience while changing the cost structure.

The thought worth keeping

A recommendation becomes more credible when it shows both sides of the equation. Sometimes reducing a position saves money. Sometimes it costs more in lost revenue, overtime or turnover. Strategy requires the curiosity to distinguish between the two.

A question that changes the room

'We've always done it this way' can sound like an explanation, but it is often only a description of history. I don't believe every process should be challenged for the sake of change. I do believe every important process should have a reason to exist today.

Understand the box before moving the walls

A good standard protects something: safety, quality, consistency, fairness or a customer promise. The interesting work begins when we separate that purpose from the particular habit used to deliver it. What outcome are we protecting? Is this method required? Is it still effective? What else could produce the same or a better result?

People need a reason to move

Change is not only an operational design exercise. People attach meaning, identity and confidence to familiar routines. Asking them to abandon a practice without understanding why it matters to them creates resistance. I prefer to invite people into the reasoning, acknowledge what the old approach accomplished and help them see what the new one makes possible.

The thought worth keeping

Structure has purpose. Standards have value. Creativity is not the absence of either. It is the ability to see possibilities that routine sometimes hides. I don't mind a box. I just like knowing whether the walls can move.

Culture shows up in ordinary moments

A statement on the wall can describe what an organization wants to be. Culture is what employees actually encounter when they ask for help, make a mistake, challenge an assumption or need a decision. The most credible culture work starts by comparing those two realities.

Listening has to lead somewhere

I look at patterns in turnover, manager behavior, communication and employee feedback. Then I ask which practical changes would make the biggest difference in people's everyday experience. An engagement activity can bring energy to a team, but it cannot substitute for consistent expectations and follow-through.

The leadership question

If employees described the culture based only on the last thirty days of decisions, would it sound like the values we promote? That question is often more revealing than a slogan.

Before the software, understand the friction

When a process relies on scattered emails, unclear approvals and repeated data entry, technology can help. But automating confusion only makes confusion happen faster. I start by mapping who does what, where information gets lost and which decisions actually require a human.

Design for adoption, not a demonstration

A useful workflow makes ownership visible, removes unnecessary handoffs and leaves room for exceptions. The technology is only successful when employees and managers can use it consistently without creating a parallel workaround.

The leadership question

Are we measuring the number of tools implemented, or the time, clarity and confidence those tools return to the business?

The first day is only the beginning

Organizations can spend hours explaining policies while leaving new employees uncertain about how to succeed. The better question is what someone needs to know, feel and accomplish during their first week, first month and first ninety days.

Make learning usable

I favor clear, relevant information delivered at the right moment, supported by managers who understand their part in the experience. Short learning modules, useful resource guides and knowledge checks can reduce information overload, but they need to connect to the real work.

The leadership question

Does our onboarding prepare someone to contribute confidently, or simply prove we presented the information?

More than a course

Development begins with knowing what someone does well, what motivates them and where the organization needs stronger capabilities. A training calendar cannot replace those conversations.

Give people room to exercise judgment

Stretch assignments, operational exposure, constructive feedback and ownership of meaningful work help people build confidence. I look for leaders who can explain the goal, coach through uncertainty and gradually step back as capability grows.

The leadership question

Are we building a team that needs us to approve every answer, or one that can make thoughtful decisions without us?

Understand what people are carrying

When organizations change direction repeatedly, even sensible decisions can feel destabilizing. Employees may be asking whether expectations will change again, whether leadership is aligned or whether their work still matters.

Communication is an operating practice

I believe leaders should distinguish what is decided, what remains uncertain, who owns the next step and when people can expect another update. Clear communication does not require pretending to have every answer.

The leadership question

Are we asking people to embrace change without giving them enough information to understand their role in it?

A score is not a conversation

When performance reviews feel disconnected from the work, they can become an administrative exercise. I start with job expectations, meaningful measures and whether managers have the tools to coach rather than simply rate.

Consistency creates credibility

Two employees doing comparable work should not have to guess whether different rules apply. Consistent standards and transparent follow-through support trust, while room for context allows leaders to exercise judgment.

The leadership question

If we asked employees what success looks like in their roles, would their answers match what their managers are measuring?