Take Yourself Seriously: Stewardship DRIVES Alignment

As organizations grow, complexity increases faster than most operating models can handle. What once worked through instinct and informal coordination begins to strain. More people are involved. Dependencies multiply. Execution requires tighter coordination. Pivots become more difficult.

In this environment, what is left unsaid in leadership discussions has a greater impact. Decisions carry forward with assumptions that have not been tested. Gaps widen as work moves into execution. Unaddressed issues don't disappear and will show up in the daily work of your teams.

You’re in a leadership meeting. A decision is forming. The direction is clear. And from where you sit, you can see what has not been addressed:

• A dependency that hasn't been mapped.

• A constraint that will bottleneck execution.

• A risk that has not been named.

And you choose not to raise it.

In leadership meetings, decisions are shaped in real time. Direction is set, tradeoffs are made, and commitments are formed. Even at this level, hesitation to speak up is common. We tell ourselves: “This might not be the right time,” or “The direction is clear; I don’t want to disrupt the momentum.”

With that, your perspective, your well informed opinion, does not enter the decision.

The Case of the "Premium" Expansion

Consider this scenario: A $25M services firm decides to launch a high-touch, "Executive" tier of its current offering.

In the boardroom, the vibe is extremely optimistic. The CEO sees higher margins, brand prestige, and a way to move up-market. The staff is excited, too; they want to do the more sophisticated, high-touch work. The momentum is undeniable.

It sounds great, and, from your vantage point, you see the unaddressed complexities.

• You know your mid-market customers will feel deprioritized.  

• Your strongest people, the ones the CEO wants to lead the new service, are already in demand and at capacity.

• With no plan to offload their current work or manage the transition for existing clients, the much valued "standard of care" that built the firm could be at risk.

When the CEO asks for a final "thumbs up" to greenlight the launch, you make a calculation. You don’t want to kill the excitement, slow momentum, or  be seen as unsupportive, so you stay silent. You don't mention the capacity shift or the risk to the existing client base.

By choosing the comfort of the room over the reality of the work, you have traded authentic alignment for a future execution failure.

The Pressure to Align Quickly

Alignment is essential. So is the responsible stewardship of organizational resources. In practice, those two can get out of sync.

Raising a constraint can be misinterpreted as disagreement, when it is often an act of stewardship. Real alignment is not simply agreement on the destination. It is a shared understanding of what it will take to get there.

When a leader points out that additional capacity is needed to integrate a $5M acquisition, they are not pushing back on the goal. They are ensuring the organization is aligned with the requirements of that goal so that the organization has the capacity to realize the ambition

The Cultural Signal

When leaders hold back, it does not stay at the leadership table. It sets a pattern for the entire studio. Teams take their cues from this. If leadership does not surface competing perspectives or reality-check the capacity of the staff, neither will the organization.

What It Costs

Holding back rarely feels like a "decision" in the moment; it feels like restraint. But it has consequences.

When we hold back we aren't being an effective steward for the organization. Like it or not, unaddressed issues find a way into the daily work of our teams.

What looks like forward momentum can result in a mid-air stall as the  unspoken issues finally becomes visible and unavoidable

What Taking Yourself Seriously Looks Like

At the leadership level, taking yourself seriously means recognizing that your perspective is a necessity for the organization to see clearly. It means using your vantage point to prepare for success, even when it introduces temporary tension.

A Pattern Worth Noticing

Every organization has insight. How does your organization encourage people to bring their insight into the decisions that shape the work.

In your next leadership meeting, when you see an unaddressed constraint, will you prioritize the momentum of the room or the capacity of the organization?

Take Yourself Seriously: ALIGN in Practice

Have you ever been in a meeting and thought, “this is a waste of time”?

Most people have.

Meetings improve when enough people ask a second question:

What can I do about it?

In this post, I use meetings as a practical example of how to apply the ALIGN method at an individual level.

ALIGN, on an individual level, begins in a familiar place: Your own experience.

Absorb: Pay attention to what is actually happening

The next time you are in a meeting you find frustrating, ask yourself:

Why does this feel like a waste of time? What is actually going on?

Listen for specific, observable details:

• We started 10 minutes late

• There is no agenda

• I do not actually know why I am here

• People are on their computers

• Things have to be repeated because people are not listening

You may also notice a broader pattern:

I spend a significant portion of my time in meetings and do not feel like I get a corresponding value from that investment.

This is Absorb. You are not judging the meeting. You are noticing what is happening and what it adds up to over time.

Legitimize: Acknowledge that what you are noticing matters

Once you have identified what is happening, the next step is to take it seriously.

This is where most people dismiss their own thinking.

• Maybe it’s just me

• This is probably just how meetings go

• It’s not worth saying anything

Instead, stay with the observation.

If meetings consistently:

• start late

• lack clarity

• require repetition

• leave you unsure of purpose

then your experience is grounded in something real.

Next is something that may be a little more difficult.

Ask yourself: How am I helping or hindering this meeting?

It might look like something like this:

• We started 10 minutes late

  • I was on time!

• There was no agenda

  • Turns out there was an agenda, which I ignored and review it before the meeting

• I don’t know why I am here:

  • I ignored the agenda sent three days in advance and that is why I do not know why I am here

    • I did not bring the information that could have helped the team make a decision

    • The decision we needed to made was clearly stated on the agenda that I did not read.

• People are on their computers

  • I keep looking at my phone

• Things have to be repeated because people are not listening

  • Sorry, could you repeat that?

The legitimizing phase is recognizing that your perspective is worth paying attention to, including where you are contributing to the problem.

You move from:

• This is frustrating
  to

• There is something here worth understanding and acting on

Integrate: Act in a way that improves the outcome

Once you have taken your observation seriously, the next step is to do something with it.

This is where alignment becomes visible.

There are many aspects of organizational life we can positively impact through our own actions.
Meetings are one of them.

It may look like preparing before you arrive.
Reviewing the agenda, or asking for one if it has not been shared.
Taking a few minutes to consider where you have perspective to add, or what you need clarified.

It may mean getting clear on your role.
Are you there to contribute to a decision, or to stay informed?
If you are there to contribute, come ready to do that.
If you are there to be informed, it is reasonable to ask whether notes would be sufficient, knowing that stepping out also means stepping back from the decision.

In the meeting itself, it often shows up in small, visible ways.
Staying present.
Building on what has been said instead of repeating it.
Saying the thing you were considering holding back.

And when the conversation turns to action, helping ensure clarity.
Who is doing what, and by when.

Afterward, it is following through.

You follow through and let others know when your part is complete, or when you are experiencing delays.

These techniques are known to improve meetings, and they are available to anyone who chooses to use them.

Grow: Pay attention to what develops as you engage

As your commitment to improving meetings growing, you may notice more about your contributions:

• When your contribution moves the conversation forward

• When it does not land the way you expected

• When a question opens up better thinking

• When active listening encourages people to speak up

• When clarity informs what happens next

Growth comes from paying attention to what happens when you participate and adjusting over time.

It also requires openness.

You may realize that when you are asked to present something complex, especially in the moment, it is not as clear or engaging as you would like. You may also notice that the meetings you lead are not as effective as they could be. Or recognize that it would be helpful to let others speak first, and listen more.

These are useful signals. They point to where additional development could help.

For some, that may mean practicing how to think and respond in real time, in a setting like Toastmasters International.
For others, it may mean learning how to design and facilitate meetings so time is used well.

Growth occurs through reflection and a commitment to improving your own skills so that you are more effective in your role.

Nurture: Sustain the practice

One meeting does not change much. A pattern does. Nurture is the decision to keep showing up this way, consistently over time.

There will be meetings where it would be easier to disengage.
Where the agenda is unclear.
Where the conversation circles.
Where you are not sure your input will change anything.

This is where the practice matters.

You prepare anyway.
You stay present anyway.
You contribute when you have something to add.
You help bring clarity when the conversation drifts.
You follow through on what you commit to.

Not perfectly, but consistently over time.

Over time, this compounds.

• Conversations become more focused as you ask clearer questions

• Decisions become more defined as ownership and timing are named

• Your presence begins to shape how the meeting operates

People notice.

They come to expect that when you are in the room:

• the conversation will move forward

• the work will become clearer

• commitments will be real

This is where Take Yourself Seriously becomes visible.

You are no longer waiting for the meeting to be well run. You are part of what makes it work.

And that changes both your experience of the meeting, and the quality of the work that comes out of it.

When you read this, who did you think it applied to?

A CEO? A Director? A Manager? A staff member?

Any person in any of those roles can sit in a meeting and think it is a waste of time.

Anyone in any of those roles can also make it better.

Take Yourself Seriously: What Happens to Insight at Work

We have all had these moments at work when something feels off.

You notice an inefficiency.
A decision doesn’t quite make sense.
A behavior is getting in the way of progress.

Most people recognize these moments as they’re happening. They see what isn’t working. Often, they have a sense of what would improve it. But that insight does not always go anywhere.

In my work with individuals and teams, I have noticed a consistent pattern: people feel frustrated by an aspect of their work but don’t always address it.

They minimize what they see.
They question whether it really matters.
They don’t think it is their role to address it.
They go along to get along.

Sometimes this hesitation is shaped by past personal experiences.
Sometimes it’s shaped by the organization itself, by what is rewarded, what is ignored, and what feels risky to name.
Often, it’s a combination of the two.

For many people, speaking up doesn’t feel safe, useful, or worth the cost. As a result, the issues that get in the way of doing the work well don’t always reach the people making decisions.

Organizations are full of insight.
Much of it goes unused.

This is one of the reasons the ALIGN method is structured the way it is.

It asks leaders to actively seek out perspectives from customers, staff, vendors, and other stakeholders.
It creates a clear and timely path for that input to inform decisions.
It brings people into the work when strategy affects how their job is carried out.

Without a deliberate effort to surface and work through different perspectives, decisions are made with only part of the reality in view.

To make sound decisions, leaders must integrate perspectives that may be in tension with one another.

A customer may experience the service as excellent, while a vendor struggles to deliver materials in the time and manner required. Both perspectives are valid.

The leader’s role is to sort through them, determine priorities, and move the work forward.

That is the organizational side of the equation.

The individual side looks different.

In one-on-one coaching conversations, when we slow the focus down and look closely at what is bothering a person, something else becomes clear. Their frustration is not random. It is connected to real impediments to their work.

They have identified gaps, misalignment, inefficiencies, or behaviors that are getting in the way, not just for themselves, but for the team and the organization.

Their frustration reflects an unspoken standard for how the work should function, and where reality does not meet that standard.

Their observations are valid.
They are useful.
But they are not brought forward.

In these conversations, I ask clients a simple question:

What would you do if you took this seriously, instead of continuing to live with it?

The response is almost immediate. People can articulate the steps they would take. The actions are practical, thoughtful, and effective.

Then I ask a second question:

What would it look like if you took your perceptions, your insights, yourself, seriously?

This is where things get more complicated.

For some people, the answer is constrained by reality. They know what they would do, and they also know why they haven’t done it. They don’t feel safe raising the issue. They don’t trust it will be received well. They don’t believe it will change anything. Those assessments are not imagined. They are often accurate.

This is the chicken-and-egg problem.

Organizations need people to speak up in order to improve.
People need organizations to be safe in order to speak up.

Both are true.

When I say Take Yourself Seriously, I don’t mean you should ignore context or expect to have things always go your way. I mean recognize that what you are noticing is legitimate, even if acting on it requires care, timing, or restraint. I mean resist the impulse to dismiss your own insight simply because the system around you makes it difficult to use.

The ALIGN method provides a path for productive input. But no system can fully compensate for insight that has already been discounted before it ever reaches the surface.

There is wisdom in every person. And that wisdom can improve the organization.

The question is not whether people see what needs attention.

The question, for both individuals and organizations, is what makes it possible, or impossible, to take that seeing seriously.

How Are Decisions Made Where You Work?

Most people can feel it when work is not working. You sit in meetings where decisions seem to circle. You watch things get approved, then somehow, undone. You leave conversations unclear on what was actually decided, or who is responsible for moving it forward. It can feel frustrating, inefficient, and like a big waste of time.

While at first it may feel like random occurrences, if you step back and study the situation, a pattern begins to emerge. These are not isolated moments. They are decision-making patterns embedded in the organization.

And most organizations tend to operate in one of three ways when it comes to leadership and decision-making. Each approach emerged for a reason. Each solved a problem. Each has strengths. Each has limits. Understanding them helps explain why work can feel clear in some moments and confusing in others.

The Directive Approach (Command and Control)

The Directive Approach, otherwise known as Command And Control, concentrates decision-making. Leaders set direction and communicate it downward. Roles are clear. Speed is prioritized.

The Directive Approach works well when:

• The environment is predictable

• The path is known

• Precision matters more than experimentation

• Time is short

Where it breaks down:

• As organizations grow, complexity increases. More people are involved. More information is generated. More coordination is required. Leadership is focused on the big picture. But the big picture is carried out through day-to-day operations.

• When operational realities are not fully considered, decisions that look sound at a high level can prove difficult, or even impossible, to execute. At times, in the name of speed, leaders move forward without fully engaging the operational reality, trusting their teams will make it work. And they do, often at significant cost in stress, rework, and strain.

• More often, the gap shows up in a more subtle manner. Decisions are made based on how the work is expected to function rather than how it actually does. Steps are missing. Constraints are underestimated. Dependencies are not visible. What makes sense in theory does not always hold up in practice. Sometimes people are not asked. Other times, when they are, they are not fully forthcoming.

What it feels like:

• Work is redesigned without understanding what it actually takes

• Tradeoffs are made without visibility into consequences

• Teams are asked to deliver outcomes that do not match current capacity or constraints

• People adapt quietly, work around issues, or carry the burden of making things function

From the leadership perspective, the plan makes sense. From the operational perspective, it does not quite work.

The Consensus Approach (Management through Collaboration)

The Consensus Approach, otherwise know, as collaborative management, expands participation. This model emerged as a necessary and vital response to the rigid, often dehumanizing nature of the Directive model. It acknowledged that people are not just "resources" to be moved, but individuals with agency, purpose, and insight. Leaders began to prioritize inclusion, working to ensure that people felt heard and that their contributions mattered. This was a significant evolution in how we value people at work.

The Consensus Approach works well when:

• Engagement and buy-in are needed

• The goal is to surface a range of perspectives

• The stakes are shared across groups

Where it breaks down:

While the shift toward collaboration was a correct and humanizing move, it often stopped short of redesigning how decisions are actually finalized. Without a clear structure for moving from "hearing" to "deciding," inclusion can drift into diffusion.

When everyone is included in everything:

• Meetings multiply

• Accountability blurs

• Decisions are revisited

• Agreement is confused with alignment

This is what creates the "Murky Middle." It is not a failure of intent, but an incomplete evolution. We softened the hierarchy to honor the person, but we haven't yet built the new architecture of authority.

What it feels like:

• Exhaustion

• Meetings about meetings

• Decisions made publicly and unmade privately

• Politeness masking disagreement

• Leaders hesitant to decide for fear of alienating others

While it is not rigid, it is also not clear. It is murky.

The Alignment Approach

The Alignment Approach brings structure to how decisions are shaped and carried forward. Many leaders have experienced versions of this approach and may describe it as collaborative or participative. What is often missing is a clear structure.

The Align ™ method provides a way to consistently gather perspective, integrate it into decisions, and carry those decisions forward into execution. It recognizes that no one sees everything, and that different perspectives are valuable for different reasons. Some insight comes from being close to the work. Some comes from seeing it from the outside. Both types of input matter, but without structure, input can become unfocused or overwhelming.

Someone must decide what to incorporate and move the work forward. That responsibility sits with leadership.

The Five Moves of the ALIGN Method:

• Absorb: Seek out the lived experience of a variety of stakeholders – customers, staff, vendors, shareholders, board members etc.. Listen to the people without judgement.  Analyze hard data, and observe the lived experience of the work before rushing into solutions.

• Legitimize: The pivot point. Leadership filters perspectives and establishes shared priorities. Crucially, this is where leadership does the internal work of reflecting on how their own actions contributed to the current situation. They must make a firm commitment to adjust their own leadership practices to support the new direction. If the leader is unwilling to move their own obstacles, they cannot ask the staff to move theirs.

• Integrate: Translating direction into practice. Staff are invited back in to determine how those priorities actually function in daily operations, planning, and decision-making.

• Grow: Building capacity and confidence. This is a shared growth; leaders must evolve their own practices and behaviors alongside the team to stay in motion.

• Nurture: Tending to the progress over time. Leadership remains committed to stewarding the culture and resisting the urge to slide back into old patterns.
  

Works well when:

• Problems are complex

• Multiple stakeholders will be affected

• Execution depends on coordination

• The decision will influence strategy, culture, or how work gets done

• The decision will move across teams or require multiple handoffs

• The consequences will be difficult to unwind

Where it breaks down:

• There is no shared understanding of which decisions require alignment

• Input is not consistently gathered from the stakeholders affected by the decision

• The "Closed Loop" is broken: Input is gathered but not acknowledged. Gathering input that is ignored is more damaging than never asking. If leadership has already made a decision, they should not ask.

• Caught in the middle: Leadership pushes a strategy without the commitment to move their own obstacles. This creates an invisible pressure where staff are forced to manufacture results for a change that lacks true support.

Not every decision requires ALIGN. It is most useful when a decision has meaningful implications for strategy, culture, or execution. Leadership does not need to get this perfect at the start. In the beginning, it is often enough to identify a few types of decisions that clearly benefit from broader perspective and coordination, and to approach those consistently.

Over time, patterns emerge. Leaders become more precise about when to use alignment and when a decision can simply be made and communicated. That consistency matters. People begin to understand and trust how decisions are made, when their input will be sought, and how their perspective will be used.

What it feels like:

• Decisions are informed by relevant perspective

• Leaders draw on broader perspective to navigate uncertainty

• Teams understand the reasoning behind decisions—even if their specific input isn't in the final solution, they know why the decision moved in a different direction.

• Disagreement becomes useful

• Execution strengthens

Strategy, culture, and execution begin to align in theory and in practice. There is a shared understanding of how decisions we made, so work feels clearer, more grounded, and less reactive.

Directive and collaborative approaches often emerge by instinct, shaped by experience and pressure rather than a defined method.

Some leaders practice alignment this way as well. They draw on perspective, engage people thoughtfully, and make decisions that hold together across the organization.

What is often missing is consistency.

The ALIGN method provides a deliberate way to lead, so alignment does not depend on instinct alone. It can be applied, taught, and sustained across teams over time. The result is an organization that moves forward with clarity, consistency, and confidence.

yOUR AI IMPLEMENTATION CHECKLIST

There is a lot being asked of organizations right now.

AI has been added to an already full set of priorities.

Organizations are working to understand what AI will realistically accomplish and what it takes to manage it well in practice.

Over the past several weeks, I’ve written about the many considerations involved in effectively introducing AI into an organization.

There are important conversations that need to take place about how AI supports the organization’s strategy, how roles and responsibilities may shift, and how quality will be maintained. There are decisions to make, conditions to put in place, and information that needs to be clearly communicated so people understand what is changing and why. This is the work required to introduce AI in a way that is thoughtful, coordinated, and effective in practice.

I’ve compiled that work into a single resource: the AI Implementation Checklist.

The checklist is designed to help organizations see what needs to be considered before launching the use of AI, so the work can move forward without creating confusion or anxiety.

The checklist brings these considerations together in one place so organizations can make clear decisions that strengthen strategy, culture, and execution to ultimately benefit the customer.

If your organization is already using AI and has encountered unforeseen challenges, you can use the guide to identify the specific factors contributing to those challenges.

You can download the checklist here:
https://www.workwisestudio.com/resources

I am interested to hear from you: what are you experiencing in your workplace? What has worked, what has been more complicated than expected, and what you would approach differently?

AI Scales Output. Disciplined Execution Protects Quality.

AI changes how work gets done, but it does not ensure that standards hold under pressure. Execution determines how decisions are reviewed, how responsibility is assigned, and how quality is protected when speed increases. Without disciplined execution, AI will scale output faster than organizations can verify it.

This is the third post in a four-part series sharing the AI Implementation Checklist, developed through the ALIGN Method for Strategy, Culture, and Execution. Here, we examine Execution — the daily practices required for AI to strengthen reliability, accountability, and performance.

AI implementation works when the organizational ecosystem is highly functioning.

• Strategy sets direction.

• Culture sets expectations.

• Execution determines how well those intentions hold under pressure.

During implementation, theory meets reality. Standards and policies that sound solid on paper will prove to be overly bureaucratic, insufficiently rigorous, or well designed for the work they are meant to support.

When AI becomes embedded in workflow, real conditions surface:

• Are decision rights clear?

• Is review responsibility defined?

• Do practitioners have the time required for verification?

• Are workloads adjusted to account for new oversight demands?

Execution is where AI either reduces strain and increases clarity or introduces new tension into an already stretched system.

We already know two things about AI that make disciplined execution essential.

1. It moves quickly.

2. It is not always accurate.

AI can generate significant volume at speed. It can also produce errors. When output scales, the impact of those errors scales with it.

For that reason, review cannot be assumed. It must be designed.

Well-structured execution makes responsibility explicit. It clarifies:

• Who reviews AI outputs

• When review is required

• What can be automated

• What must be manually verified

• What triggers escalation

• What requires designated sign-off

Verification should sit at the level of the work.

In most cases, the practitioner using the tool should evaluate and verify AI-supported output. AI can generate drafts, surface options, and accelerate production, but it does not replace professional judgment.

Escalation should occur based on defined criteria, not hierarchy. If every AI-supported output requires managerial approval, workflow slows and accountability becomes diffused.

Building Capability During Early Implementation

Confidence in AI-supported work develops over time and across varied use cases. Until reliability is demonstrated consistently, disciplined verification is required.

There may be instances where the practitioner using the tool does not yet have sufficient knowledge or context to independently assess accuracy. In those situations, an additional designated reviewer may be appropriate.

That added oversight should be temporary and clearly defined. Its purpose is to support learning while protecting quality. As competence increases, that layer should recede, returning authority fully to the level of the work.

Communication and Shared Learning

Execution requires ongoing communication. As experience with the tool expands, organizations should create structured opportunities to surface lessons learned and refine processes.

Leadership should make time to review workflows and recalibrate expectations as confidence in the tool develops. Deliberate review ensures that increased speed is matched by sustained clarity, accountability, and professional standards. With shared understanding, responsible oversight becomes a collective discipline that strengthens overall performance. Through intentional design and disciplined action, AI can expand the capacity of your organizational ecosystem in service of your goals.

AI Implementation Checklist: Execution

Workflow Integration

☐ The data  informing  AI systems is accurate, current, and structured to support reliable outputs.

☐ We have clearly defined:

• Who reviews AI outputs

• When review is required

• What can be automated

• What must be manually checked

• What triggers escalation

• What requires a staff person’s sign-off

☐ Informal workarounds have been identified and replaced with formal workflow updates.

☐ AI-supported work is not considered decision-ready until a designated staff person has evaluated its accuracy, implications, and alignment with intent.
☐ Staff are designated to ensure AI-supported work reflects company standards and culture.

☐ We are starting with defined pilot use cases and have established success criteria that must be met before expanding implementation.

The Reality of Pacing

☐ We recognize that AI processing speed is only a fraction of the total task speed. We have factored in the time required for human verification as an essential part of the completed task.

☐ We have prioritized the final sign-off over the speed of delivery. If a professional cannot verify the accuracy or appropriateness of the output in the time allotted, the deadline is extended until the check is complete.

The Feedback Loop

☐ We have a simple way to flag when the AI is incorrect. Reporting these instances is a vital contribution to improving the system for the entire team.

☐ We have scheduled calibration check-ins. The team has dedicated time to discuss whether the current workflow is sustainable or if the pressure for speed is compromising quality.

☐ We have identified clear pause criteria. We have agreed on the specific types of errors or system failures that would require us to halt the trial and reassess the process.

Adoption and Support

☐ Clear ownership exists for sustaining AI integration after the initial rollout. We have identified who is responsible for the tool’s health once the trial ends.

☐ A plan is in place to monitor adoption after project teams transition ownership.

☐ Support channels are defined, including how employees get help and how issues are resolved.

Organizational Dynamics & Culture

☐ We are mindful of maintaining an environment that promotes the individual and collective strengths and creativity of the team.

☐ We prioritize original thought and personal engagement. We actively guard against an over-reliance on machine-generated content to ensure the work remains a reflection of our team's talent.

☐ We value collaboration and want to safeguard the unique perspectives of our colleagues, ensuring the tool isn't creating silos that discourage human interaction.

☐ We see AI as a tool to enhance professional mastery. We work to ensure the tool supports a person's expertise rather than bypassing the critical thinking required to develop it.

The next post will focus on the Alignment required to sustain these standards over time.

AI Changes the Rhythm of Work. Leadership Determines the Culture.

AI changes how work gets done, but it does not define how people work together. Culture determines how speed is interpreted, how judgment is applied, and how accountability is maintained. Without cultural clarity, AI will quietly reshape norms in ways leadership did not intend.

This is the second post in a four-part series sharing the AI Implementation Checklist, developed through the ALIGN Method for Strategy, Culture, and Execution. Here, we examine Culture — the shared expectations that determine whether AI strengthens or erodes trust, professionalism, and collaboration.

For many people, AI felt like it appeared overnight. One day it belonged to science fiction. The next, it was sitting in a browser window, answering questions, drafting emails, analyzing data, and offering recommendations.

With that shift came excitement about how fast it is, how capable it is, and how much it can produce in a short amount of time.

It also raised very direct human questions:

Will I still have a job?
If I do, what exactly is my job now?

For some organizations, those questions are not abstract. AI has already reshaped markets, displaced revenue, and altered competitive landscapes. For leaders responsible for implementation, however, the most immediate impact is internal. AI changes how work is experienced.

Culture is the set of shared expectations that guide behavior. Under pressure, it reflects what is valued, what is protected, and what is quietly tolerated. It shapes how decisions are made when tradeoffs are real.

AI presses directly on culture because it changes the rhythm of work.

It increases speed.
It expands what can be attempted.
It generates output before people have fully considered context.

That shift affects how people relate, how they decide, how they take responsibility, and what they believe their role is.

When AI becomes part of daily work, managers may wonder how their role changes. Is AI now the first stop for answers? Or is it a tool that strengthens coaching and judgment?

Employees may wonder where their value now sits. Is it in speed? Oversight? Interpretation? Relationship? Decision-making?

These are cultural questions. They are leadership questions.

If leadership does not clearly define how human judgment, accountability, collaboration, and standards function alongside AI, those norms will be shaped by default. Employees will draw their own conclusions, and the system’s pace and outputs will begin to influence what becomes acceptable. Speed, not values, may become the defining factor.

Leadership has an opportunity to further shape and strengthen organizational culture so that AI operates within it, not in place of it.

In the Culture section of the AI Implementation Checklist, I ask leadership teams to examine how AI will influence shared purpose, employee experience, judgment, pacing, managerial stewardship, and workload. The questions are designed to surface assumptions before they solidify into habits.

CULTURE: How will using AI shape how we work together?

Shared Purpose

☐ Leadership has clearly articulated the role and value of human judgment, collaboration, and accountability alongside AI use.

☐ AI-related decisions reflect our stated values.

☐ Customer benefit is prioritized alongside operational efficiency.

☐ The purpose and intended impact of AI have been clearly communicated to all teams.

Employee Experience

Foundational Readiness

☐ Employees have had the opportunity to ask questions and explore their concerns about AI-supported work.

☐ We have established clear parameters for AI use, defining which specialized systems are required for core work and the protocol for using general-purpose tools.

☐ Employees have been shown how AI supports their specific roles and the organization’s broader purpose.

☐ Training and support resources are in place for employees to use AI with confidence.

Judgment & Pacing

☐ We have established that human judgment is the final authority. AI output is treated as a draft that requires an active professional "seal of approval."

☐ We have defined the "human finish" for AI work, documenting the specific steps required to verify and refine AI-generated content.

☐ Workflow expectations allow employees sufficient time to perform mandatory evaluations before acting on AI information.

Protection of Integrity

☐ We recognize that AI is not 100% accurate; therefore, human verification is a mandatory, integrated part of the workflow.

☐ We have a "No-Fault" reporting channel for AI quirks. We’ve made it easy for people to flag weird or wrong AI behavior so we can improve the tool as a team.

☐ There is a clear way for people to flag "Speed vs. Quality" conflicts. If the pace of the work is making it impossible to apply a professional "seal of approval," the priority is to adjust the timeline, not lower the standard.

Managerial Stewardship

☐ Managers are prepared to coach employees on how to use AI in ways that strengthen judgment and decision quality.

☐ Managers are prepared to coach their teams on when to override or question AI, protecting the time needed for human oversight.

☐ Managers support their teams in decoupling the pace of human analysis from the speed of AI generation.

Workload and Role Impact

☐ We have reviewed how AI changes job scope and responsibilities.
☐ We have adjusted workload to provide sufficient time for the front-loaded demands of AI integration, including learning, setup, data cleanup, and process redesign.
☐ Managers have and will continue to adjust workloads based on visible priorities.
☐ Expectations around pace and responsiveness are clear.

Identify the Non-Negotiables for your Culture

Before implementing new tools, Leadership must decide what remains non-negotiable.

What does human judgment mean to our organization?
What standards must never be compromised?
What does stewardship look like under pressure?

AI changes the rhythm of work.
Leadership determines whether that rhythm strengthens or destabilizes the culture you intend to build.

AI Is a Powerful Technology. Strategy Still Leads.

AI can generate volume, speed, and expansion, but it cannot determine what is worth pursuing. Strategic clarity must be the filter that determines what moves forward and what is set aside. Without it, you are simply accelerating in an unknown direction.

This is the first of a four-part series where I share the AI Implementation Checklist, developed through the ALIGN Method for Strategy, Culture, and Execution. We begin with the foundation: Strategy.

Last year I attended a LinkedIn-sponsored webinar on AI and leadership. One recommendation caught my attention: the presenter suggested that when a direct report comes into your office with a question, your first response should be, “Did you ask AI?”

As an organizational development practitioner, that direction raised several questions for me:

• Does AI have enough context to answer in a way that reflects the company’s values and strategic intent?

• If AI becomes the first stop for thinking, how do we ensure its answers reflect what matters most to the customer?

• What happens to the relationship between a manager and employee who value connection and mentorship?

• How does that shift redefine the function of the manager?

We often encourage employees to also present a solution when they present a problem. That is a healthy discipline. This felt different. It positioned AI as the first stop for thinking rather than a support to human judgment.

At the time, I was still getting familiar with AI. Still, a few warning signals went off. Since that webinar, I have used AI extensively. I find it incredibly helpful for clarifying my thinking. It often says succinctly what I have been struggling to articulate. It analyzes information quickly and suggests logical next steps without hesitation. It knows a lot about a lot.

I have also seen its limits:

• It will confidently make things up.

• It will exaggerate when it lacks context.

• It requires clear instructions to perform well.

• It moves quickly toward completion when nuance, judgment, and context still require human evaluation.

It is a powerful tool, but it requires thoughtful management. Every significant technology investment—ERP systems, CRM platforms, data dashboards—reflects the quality of strategy, the clarity of culture, and the discipline of execution. AI does as well. It simply operates at greater speed and with greater generative capacity.

The shift we are seeing:

• AI generates output.

• AI expands scope.

• AI increases volume.

• AI operates in ambiguity.

• AI fills in gaps when clarity is missing.

Whatever is strong in your organization becomes more visible. Whatever is unclear or misaligned also becomes more visible. Because the pace is faster, the consequences surface faster.

Many organizations are accelerating AI adoption because the pressure to keep pace is real. But an increase in volume does not require people to accelerate; it requires disciplined judgment. Strategy—and ultimately the benefit to your customer—becomes the filter that determines what moves forward and what is set aside. AI increases what is possible, but strategic clarity determines what is worth pursuing.

That is why alignment matters before implementation.

I developed an AI Implementation Checklist through the lens of an organizational development practitioner. It is designed to help leadership teams align strategy, culture, and execution so that AI strengthens the organization in deliberate ways. This first set of questions ask the important questions to ensure AI is in service to the strategic direction.

STRATEGY — Will AI help us advance what matters most?

Strategic Clarity

☐ We have identified the enterprise-level outcomes AI is expected to improve (e.g., growth, margin, customer retention, speed, quality).

☐ We have defined how customers will benefit, directly or indirectly.

☐ We can clearly explain why we are using AI.

Focus and Tradeoffs

☐ We have defined the initial operational problems AI will address.

☐ We have identified what tasks or projects will be paused to make room for AI integration.

☐ AI investments align with how we compete and grow.

Milestones and Horizon

☐ The original reasons for adopting AI have been translated into measurable milestones.

☐ Strategic objectives are mapped to 30–60–90-day milestones, followed by 6-month intervals through a 24-month horizon.

☐ Leadership will review progress at defined intervals aligned to these milestones and will make adjustments as needed.

In the next post, we will examine Culture: How will AI shape how we work together?

#WorkWiseStudio #AILeadership #StrategicClarity #OrganizationalDevelopment #LeadershipChecklist

AI: IS IT WORTH IT

Success with AI depends on how well the technology supports your people and advances your strategy.

In this five-part series, I am sharing how to use the ALIGN framework to help organizations integrate AI in ways that strengthen strategy, culture, and execution, and turn AI into a genuine strategic advantage.

In Absorb, leaders gather data to understand what is actually happening.
In Legitimize, leaders respond with a clear, prioritized roadmap that reflects what they heard from stakeholders, what the data reinforces, and what they observed firsthand.
In Integrate, leaders engage staff to translate the roadmap into practical, workable detail, aligning priorities, systems, and roles.
In Grow, leaders strengthen the organization’s capacity and confidence to carry the work forward.

Here, in Nurture, we focus on what allows the investment to pay off over time. Nurture is about sustained leadership attention, clear priorities, and ongoing stewardship that help AI mature into a reliable, effective part of how the organization operates.

Is It Worth It?

When leaders introduce new technology, the question underneath the launch is simple: is it worth it?

That question reflects the full cost of the investment. The cost of the tool itself. The cost to redesign workflows. The cost to integrate systems, train people, and support adoption over time. Leadership attention, organizational capacity, and opportunity cost all factor into the decision. The investment is financial, operational, human, and strategic, shaping how the organization competes and grows.

This series opened with research from McKinsey, The State of AI in 2025: Agents, Innovation, and Transformation. That report shows a consistent pattern. While most organizations are using AI in some form, only a small group report meaningful enterprise-level value. McKinsey refers to these organizations as AI high performers.

What distinguishes AI high performers is sustained commitment. They redesign workflows to maximize human and AI strengths across the flow of work. Senior leaders demonstrate visible ownership and remain engaged well after implementation. Measurement continues beyond early milestones. Training and support remain in place. Over time, usage deepens and value compounds.

This is how the original question, “Is it worth it?”, is answered. AI becomes worth the investment when commitment extends beyond launch and meaningfully shapes how the organization operates day to day.

In the ALIGN framework, Nurture is the phase where leadership commitment to the goals is critical to realizing the intended outcomes.

Nurture as a Leadership Practice

Nurture is a leadership responsibility. Leaders ensure the organization maintains focus on AI implementation and creates the conditions for it to mature into a highly effective tool.

That focus is supported through feedback loops. The success criteria that made the investment worth pursuing in the first place are translated into ongoing milestones with clear objectives. Progress is reviewed at meaningful intervals. Leaders remain curious about what the data, lived experience, and results are showing. Learning guides adjustment as conditions evolve.

From Champion to Steward

Once an AI tool goes live, leadership involvement evolves from championing implementation to stewarding long-term use.

Ownership remains clear. Resources stay aligned. Measurement reflects real operating conditions. Leaders stay connected to how the system supports daily work and decision-making. This continuity protects the original investment and sustains momentum.

RebalancE Work to Reach Equilibrium

AI changes how work is distributed across the organization. Some tasks move into the system. New responsibilities emerge around oversight, judgment, and coordination.

The role of leadership is to keep priorities visible and viable so the organization can make decisions consistent with those priorities. When leaders are clear about what matters now, what can wait, and what can be set aside, managers realign work accordingly.

Managers translate that clarity into operational decisions. They adjust workloads, sequence work, and integrate AI into planning and delivery in ways that reflect stable priorities rather than constant change. Tradeoffs become explicit. Some work is set aside in favor of efforts that add the most value. AI begins to relieve pressure in practical, observable ways.

Learn Through Ongoing Dialogue

AI capabilities continue to evolve. Nurture depends on staying in conversation with the people closest to the work.

Leaders establish regular opportunities to surface insights, constraints, and opportunities. Patterns appear early. Adjustments remain manageable. Trust grows as people see their experience reflected in how the system evolves.

Reinforce Purpose Over Time

As AI becomes part of everyday operations, an ongoing sense of purpose provides continuity.

Leaders reinforce purpose by recognizing effort as well as outcomes. Milestones reached, lessons learned, and improvements made are acknowledged. This attention signals that the work remains visible and valued.

Positive recognition sustains energy. Commitment strengthens as people experience support while working through discomfort and uncertainty. Purpose connects daily effort to the original intent of the investment.

The Payoff

Sustained commitment produces compounding returns. As capability deepens, confidence builds. As work becomes more coherent, capacity increases. As the organization becomes more effective in how it uses its time, makes its decisions, and gets things done, the payoff multiplies.

This is Nurture in action. The question “Is it worth it?” is answered when leadership remains engaged, stays focused, and adjusts based on what is learned about customers’ experiences, employees’ work, organizational dynamics, and system performance as the technology becomes embedded over time.

AI Raises the Bar

Success with AI depends on how well the technology supports your people and advances your strategy.

In this five-part series, I am sharing how to use the ALIGN framework to troubleshoot friction in AI implementations and turn AI into a genuine strategic advantage.

In Absorb, leaders gather data to understand what is actually happening.
In Legitimize, leaders respond with a clear, prioritized roadmap that reflects what they heard from stakeholders, what the data reinforces, and what they observed firsthand.
In Integrate, that roadmap meets the realities of daily work, where priorities, systems, and roles must begin to line up in practice.

In Grow, we explore ways to strengthen the organization’s capacity to carry the work forward.

Strength the Ecosystem

Congratulations. You have launched your AI initiative. Now the real work begins.

Once priorities have been translated into action during the Integrate phase, the next step is to strengthen the people and systems that will carry the work forward. This is the Grow phase, where leaders, teams, and individuals build the capacity, confidence, and resilience required to sustain progress.

A byproduct of AI’s ability to operate at a much faster pace than humans is that it accelerates decisions, exposes inconsistencies, and makes gaps in clarity, judgment, and leadership visible far more quickly than before. In doing so, AI introduces a new kind of pressure into the organization.

Grow is the phase where organizations pause long enough to understand their current state and identify where strategy, people, and processes must grow in skill and understanding for AI to be effective. Without this work, AI will amplify issues that humans might previously have corrected in the moment, issues that now risk being embedded into automated systems and scaled across the organization.

Reallocation, not Replacement

When people hear “AI” and “efficiency,” they often hear “replacement.” That fear is understandable. No one wants to feel that their judgment, experience, or contribution can be reduced to a machine.

The reality is that people and technology are good at different aspects of work. AI is well suited to speed, scale, and consistency. Humans are well suited to context, judgment, and meaning. Grow is about building the skills and knowledge that enable people to work at their best. In the context of AI implementation, Grow also focuses on maximizing human strengths so the technology is effective, making that division of labor explicit and workable.

While organizations may not explicitly state that they intend to replace people with AI, there is often a quiet hope that once AI is introduced, cost savings will be realized by reducing or stretching human involvement. What is often underestimated is the opposite reality: AI raises the demand for human capability. As systems move faster and decisions scale, organizations need clearer judgment, stronger decision-making, and more disciplined learning than before. When that capacity is not developed alongside the technology, AI exposes gaps that teams are not equipped to manage.

While this gap often shows up first in how leaders think, decide, and learn, it does not stay there. These demands quickly move into execution, shaping how work is paced, how risks are managed, how quality is maintained, and how people experience the culture under pressure. Grow is where strategic intent and cultural norms translate into how work actually gets done across roles and teams.

Strengths and Meaningful Work

As a Gallup Strengths coach, I am very aware that people thrive in different parts of execution. What feels energizing to one person may feel draining to another. Someone with Strategic may want to move quickly and adjust course as new information appears. Someone with Deliberative may want time to think risks through. A person high in Adaptability may shift naturally to meet the moment, while someone strong in Consistency finds meaning in stability and reliability.

What one person finds dull gives another person energy. What one person finds difficult is easy for another. There may be assumptions that certain kinds of work are inherently dull or undesirable while for many people they find deep satisfaction in work that is structured, repeatable, and predictable. They take pride in accuracy, continuity, and getting things right over time. That contribution matters. AI does not eliminate the need for those qualities. It changes where they are applied.

As systems take on more of the mechanical repetition, human work often shifts toward oversight, quality, exception handling, and judgment at the edges. For someone who values consistency or deliberation, this may mean becoming a steward of reliability rather than a processor of volume. For someone who values adaptability or strategy, it may mean focusing more on direction-setting and course correction. The work evolves, but the strengths still matter.

Grow is about helping people see how what they naturally do well continues to be valuable as the shape of the work changes. It is not about forcing everyone into the same kind of role. It is about redirecting strengths so people can contribute with confidence and pride as AI becomes part of how work gets done.

Personal Agency

Admitting where support is needed can be uncomfortable, especially in environments that reward competence and speed. Leaders can lower that barrier by starting with strengths. Naming what someone already does well, and why those strengths matter to the work or the team, establishes respect and context before discussing development needs.

From there, invite the individual to identify where additional support would be most helpful. When people are asked for their perspective first, the conversation shifts from evaluation to collaboration. The perceived risk drops, and participation in learning becomes more likely because it feels self-directed rather than imposed.

This process is more effective when leaders pair the conversation with a defined set of options. Offering a clear menu of development supports signals that help is real, available, and endorsed. People are more willing to name what they need when they know those needs can actually be met.

People at every level, from the front line to the C-suite, benefit from support that helps them calibrate their strengths in an AI-augmented environment.

Growth in Capacity Precedes Growth in Results

Many organizations name growth as a top priority while simultaneously contending with uneven execution, workforce strain, and unresolved questions about identity and direction. These tensions matter because AI does not operate in a vacuum. It operationalizes whatever clarity or confusion already exists in the system.

Organizations often articulate ambitions to use AI to improve efficiency, strengthen operations, or elevate the customer experience. Those outcomes are achievable, but only if the organization grows in parallel in several critical ways.

Grow focuses on building clarity and judgment so that speed does not outpace understanding.

A Critical AI Design Constraint

People routinely navigate ambiguity by applying context and judgment. AI does not have that context. When clarity is missing, it will still produce an output, but that output is based on statistical inference rather than situational understanding.

AI does not understand a situation. It recognizes patterns.

More specifically, statistical inference means that AI:

• Looks at large volumes of past data.

• Identifies patterns, correlations, and probabilities within that data.

• Uses those patterns to predict or generate what is most likely to come next, based on the inputs it receives.

What AI does not do:

• Understand why something matters in this moment.

• Grasp intent, consequences, or tradeoffs unless they have been explicitly defined.

• Sense shifts in tone, trust, pressure, or context the way people do.

• Adjust based on lived experience or values unless those are encoded into rules or training data.

When clarity is missing, AI does not pause or ask for meaning. It fills the gap by extending patterns it has seen before. This is why Grow matters.

Strategy (Including Brand)

Strategy sets direction. It establishes what the organization is trying to become and how success will be defined.

What AI can do

• Analyze large volumes of data to identify trends, opportunities, and risks.

• Model scenarios and tradeoffs based on defined objectives.

• Optimize toward stated goals and scale strategic decisions quickly.

What AI needs humans to be clear about

• What the organization is trying to become, not just what it is trying to improve.

• What differentiates the organization and what should not be optimized away.

• Which tradeoffs matter most when priorities conflict.

• How success is defined beyond speed, volume, or short-term gain.

Development focuses on strengthening direction-setting.

Examples of effective support include:

• Strategy clarification sessions that force explicit tradeoffs.

• Leader working sessions on framing useful questions and constraints for AI systems.

• Coaching senior leaders to articulate strategy and brand intent in operational terms.

• Scenario-based exercises that practice decisions with incomplete or competing data.

Culture

Culture shapes how decisions are made when pressure is high and priorities collide. It is experienced through what people believe will be supported when judgment is required.

What AI can do

• Apply policies, rules, and priorities consistently once expectations are clear.

• Reinforce patterns of work through scheduling, workflows, and automated interactions.

• Reduce variability in routine decisions.

What AI needs humans to be clear about

• How values are meant to guide real decisions.

• What matters when priorities compete.

• Where discretion is expected and where consistency is required.

• What people can trust will be supported when judgment is exercised.

Development focuses on shared understanding.

Examples of effective support include:

• Facilitated conversations using real decisions to explore how values apply in practice.

• Leader coaching on explaining tradeoffs, especially when decisions disappoint someone.

• Team forums that normalize naming tension instead of working around it.

• Clear escalation paths so individuals are not carrying cultural decisions alone.

Execution

Execution is how strategy becomes real in day-to-day work. It is the set of decisions, handoffs, and follow-through that determine whether priorities are delivered or quietly eroded over time.

What AI can do

• Monitor performance continuously and at scale.

• Surface patterns, anomalies, and early warning signals.

• Automate routine tasks and reporting.

What AI needs humans to be clear about

• Which signals matter and which can be ignored.

• What constitutes meaningful deviation versus normal variation.

• When human intervention is required and who is accountable.

• How decisions should be made when data is incomplete or contradictory.

Development focuses on judgment under speed.

Examples of effective support include:

• Helping leaders and managers interpret AI outputs in the context of real operating decisions.

• Practicing how to respond to early signals using live data, not hypothetical scenarios.

• Clarifying decision rights so accountability remains with people, not systems.

• Coaching leaders to intervene early and proportionately, rather than waiting for failure or overreacting to variation.

Normalize the Learning Curve

Innovation requires new skills, and proficiency takes time. Leaders play a critical role by modeling curiosity, calibrating expectations to the reality of learning, and creating conditions where learning is expected and supported.

Feedback as Fuel

Growth depends on feedback that is integrated into everyday work. When people see their insights shaping real decisions, trust increases and resistance decreases. Feedback becomes a source of refinement rather than a penalty.

The Result: A Culture of Continuous Learning

AI increases the demand for continuous learning. While there is a temptation to believe technology will reduce the need to build human capacity, this kind of technology does the opposite. It requires more clarity, more judgment, and more learning over time. When people do better, AI does better. In that way, AI becomes a reflection of an organization’s commitment to learning, especially when the pressure to move faster is highest.

UP NEXT: Nurture

In the next post, Nurture, we’ll explore the ongoing commitment leaders must make to protect, reinforce, and sustain the human practices that allow an AI-enhanced organization to realize its full potential.

Why Didn’t Anyone Ask Me?

Success with AI depends on how well the technology supports your people and advances your strategy.

In this five-part series, I am sharing how to use the ALIGN framework to troubleshoot friction in AI implementations and turn AI into a genuine strategic advantage.

• In Absorb, leaders gather data to understand what is actually happening.
  In Legitimize, leaders respond with a clear, prioritized roadmap that reflects what they heard from stakeholders, what the data reinforces, and what they observed firsthand.
  In this post, we focus on Integrate, the phase where that roadmap meets the realities of daily work.

When a “New Way of Working” Misses the Mark

Have you ever been told there was going to be a new way of working, and the moment you heard the details, you knew it was not going to work?

Maybe the plan sounded reasonable at a high level. But once you pictured it inside the flow of your actual tasks, it was clearly a non-starter. The natural response is often, Why didn’t anyone ask me?

When AI initiatives stall, it is usually because of this gap. The tool is being built or adjusted by people who do not have to live with the consequences of its output.

Organizations often limit participation to a small group in the name of efficiency, only to delay surfacing issues that later become harder and more expensive to fix.

The Integrate phase exists to close this gap.

Bringing the Doers and the Builders Together

Integrate brings the doers, both internal and external, and the builders to the same table.

In Absorb, the project team worked with leadership to synthesize input from staff, customers, and vendors. In Legitimize, that same team helped leadership assess what was feasible and set priorities.

In Integrate, we extend information equity to the people who actually carry the work forward.

Information Equity

Integration depends on transparency and shared understanding.

Sharing high-level themes from the Absorb Phase (discovery) helps staff understand the realities that informed leadership and project team decisions, while protecting the candor of those who contributed. This shared context reduces resistance and builds trust.

The Communication Loop

Information equity only works when communication flows consistently.

Because the project team helped shape priorities and sequencing, they are now responsible for keeping sponsors and impacted staff informed of progress. External partners do not need internal diagnostics, but they do need clear, targeted updates about changes that affect their work.

When everyone is working from the same source of understanding, attention shifts away from defending decisions and toward building the future.

Shared Design: From Mandate to Meaning

AI systems are often technically correct and operationally broken. The logic may be sound, but it frequently fails to reflect organizational values, institutional knowledge, and the nuanced judgment people apply every day to do the work well.

Shared design closes that gap. The project team works directly with the people who touch the work. If the AI is customer-facing, this may include trusted customers. If the issue is data quality, it includes the vendors supplying that data.

As teams move into the details, a second round of discovery typically occurs, one that focuses on practical realities and operational nuance. This deeper examination allows assumptions to be tested and adjusted in the context of real work.

When those who are impacted play an active role in shaping how the solution is designed and implemented, it is more likely to fit the realities of the work, reduce rework, increase adoption, and clarify risks and tradeoffs so the team can adjust course sooner rather than later.

Solve for the System, Not the Tool

During Integrate, the combined team wants to identify any friction across the entire ecosystem.

• Is the AI underperforming because vendor data is inconsistent?

• Does the output require multiple layers of verification by staff?

• Is a fix creating new hurdles for customers?

• Where have people created manual workarounds just to get their job done?

The tool is only one part of the system.

Work in Draft Mode

When a project is already strained, announcing a final fix increases risk. Instead, move into draft mode.

Choose one friction point identified by the people doing the work. Run a one to three week pilot with a small group of staff or a subset of customers.
Be explicit that this is a test. If it does not work, adjust and try the next draft.

Draft mode lowers the temperature and replaces pressure with learning.

Integration is where strong ideas become an operational reality

You do not need to involve everyone, but you must involve those who are materially impacted. When the people responsible for execution and the partners affected by the change have a voice in shaping the solution, implementation accelerates and resistance fades.

As noted in the first post of this series, many organizations are using AI tools without embedding them deeply enough into everyday workflows to realize sustained value. Integration is the work of closing that gap, so AI becomes part of the operating system, strengthening the system’s capability rather than standing apart as a separate solution or the answer in itself.

Up Next

Once AI is part of how work gets done, success depends on ensuring people are supported as roles, decisions, and expectations evolve. In the fourth stage of ALIGN, “Grow”, we reinforce skills, clarity, and confidence so individual and organizational capability continues to develop and move forward.

Yes, you have a point

Success with AI is not about the technology itself. It is about how the tool supports your people and advances your strategy.

In this 5-part series, I’m sharing how to use the ALIGN framework to troubleshoot friction in your AI implementation and turn AI into a genuine strategic advantage.

The Absorb phase was about gathering data to understand the current situation. The Legitimize phase is about respecting the people who shared their experiences and perspectives by responding with a clear, prioritized roadmap.

The Reality Check

Launching an AI initiative is an achievement. While we all want projects to go off without a hitch, sometimes we just don’t know things until we start. If outcomes aren’t lining up with expectations, consider it an opportunity to learn rather than a setback. Use this phase to identify gaps and recalibrate.

Gather the feedback you received during the Absorb phase and organize it into these three sources of friction:

• Strategy (The "Why"): Feedback regarding high-level goals.

  • Is the AI helping you move the needle on your core mission, or has it become a distraction?

• Execution (The "How" and "When"): Feedback regarding the daily reality.

  • Is the tool reliable, useful, and credible? Does it fit the workflow, or is it creating "shadow processes" and just too messy to be useful?

• Culture (The "Who"): Feedback on how the technology impacts your people.

  • Is it shifting how you live out your values or how you serve your customers and staff?

  • Do customers and/or staff feel undervalued, or ignored. Do staff staff feel like their jobs are threatened?

Make clear the Gaps

Use this simple audit for each major feature to highlight exactly where the project is falling short of the vision:

The Reality Gap:

What we planned: AI reduces administrative burden by 30%.

What we observed: Staff are spending 40% more time "babysitting" the AI's output.

The Verdict: The tool is functioning, but the data is unreliable.

Individually Review the data

Each leadership team member should review on their own the data collected during the Absorb phase. This includes insights from:

• Direct Conversations with project teams and users.

  • Note on Responsibility: Use discretion regarding names in the report. People can become fixated on "Who said that?" rather than "What is the problem?" If the culture has a tendency toward this, the person compiling the report should keep the findings focused on high-level themes.

• Feedback from impacted staff and customers.

• Data Trends and technical performance metrics.

• Direct Observations of the tool being used in daily workflows.

Reviewing this individually first allows leaders to process the "unfiltered truth" before the pressure of a group meeting begins. Some folks may feel "under fire," so it is best not to do this as a group initially. If the Project Sponsor is not on the senior leadership team, I recommend they be included in the review from the beginning. If that is not congruent with current practices, bring them in as soon as possible.

Lead with a desire to understand and empathy

The Empathy Filter: Appreciate the role and status of the person who shared the data. It may be anonymous, or it may be clearly identifed. Consider that each person is offering their “truth” their perspective informed by their experience. Their position, the level of that position, their time with the company, their comfort with AI, their comfort with change all are factors in their responses.

Take an Initial Pass: Mark each item:

• ✅ This sounds accurate to me.

• ❓ I need more information.

• ✖ I don't see this.

THe leadership gut check

“Change starts at the top” is a common refrain. I used to think that simply meant needing a strong sponsor to decree a project’s existence. Now, after years of organizational development and project management, I see it differently.

Leaders are often the primary obstacles to an initiative, sometimes unconsciously, and sometimes consciously as they protect their territory. The tragedy of leadership misalignment is that the staff are always the ones caught in the crossfire.

An effective leader must be brave enough to ask themselves hard questions before walking into the leadership team alignment meeting:

• Commitment: How committed am I, truly, to the success of this AI implementation?

• The Unspoken: What concerns have I been harboring that I haven’t shared?

• Vision: What does success actually look like from the perspective of my specific role?

• Self-Reflection: On the whole, am I helping or hindering this implementation?

Leadership Alignment Check: Four Essential Conversations

After the individual team members have had time to digest the information, the leadership team will begin a series of meetings with four distinct conversations to avoid "decision fatigue" and ensure raw data is fully understood before decisions are made or work is prioritized.

• Conversation 1: The Pulse (Review the Summary)

• Goal: Capture initial reactions without discussion. Look for "Small Wins", the parts that are working, to lead with when you eventually communicate to the organization.

• Conversation 2: The Context (Fill in Missing Details)

• Goal: Address items marked "Need more information." If the data doesn't exist, establish the metrics you need to track.

• Conversation 3: The Reality (Validate Assumptions)

• Goal: Compare initial project assumptions against the lived experience of the staff. What did we get right? Where were we blindsided?

• Conversation 4: The Alignment (Identify Priorities & Root Causes)

• Goal: Reach consensus on the "Why" we are doing this AI implementation and why we are having these issues. If leaders disagree on either the purpose or the root cause of problems, the resulting roadmap will be disjointed and the staff will get caught in the middle.

The Technical Reality Check: AI Recalibrations

Before prioritizing, apply a technical lens to determine if the friction is a human, data, or tool problem. This ensures your roadmap is grounded in reality:

• Instruction vs. Tool Failure: Is the AI failing, or is the "prompt" simply missing context? If it’s an instruction issue, the fix is better templates, not a new tool.

• The "Fabrication" Audit: Identify where the AI is generating confidently incorrect fabrications or "Logic Breaks." These are non-negotiable risks. Move them to "Stops" or "Mystery" immediately.

• Data Foundation Debt: Is the AI underperforming because internal data is messy? You may need to prioritize "cleaning the house" before the technology can deliver.

The Prioritization Filter

Now, filter the remaining feedback and technical requirements through the lens of Strategic Impact vs. Effort. At this stage, our goal is stabilization. We must address areas of frustration quickly so that people don't disengage from using the AI.

• The "Maintains": Start by identifying what is working well. These "Bright Spots" build confidence and provide a stable baseline for the team to lean on while other areas are fixed.

• The "Stops": Features causing enough friction to degrade the customer experience or data integrity. Once you've acknowledged the wins, you can objectively decide what to pause or pivot immediately to stop the "bleeding."

• The "Nuance Gaps": Manual workarounds necessary because the AI doesn't understand the job. These require training or process adjustments to eventually move them into the "Maintains" category.

• The "Mystery": Issues where you aren't sure of the root cause; give these more time with guardrails before deciding their permanent home.

The Responsive Roadmap

A roadmap in the ALIGN framework is a commitment.

• Immediate Fixes: Address the top 1–2 "Blockers" to show momentum and build trust.

• Strategic Adjustments: Realign the AI’s role to support the actual nuances of the work you identified in the Absorb phase.

• The Commitment: Explicitly state what you are not doing right now, so the team knows where to focus their energy.

It is really important to attach a high level timeline to the roadmap so that people know relief is on its way.

The Strategic Project Sponsor: Anchoring the Realignment

When the C-Suite recommits to the priorities, it is a good time to take a look at the project sponsor. It is common to appoint the CTO as the default Sponsor for AI just to get it off the ground, but as the project’s impact becomes clearer, you may realize the true owner should be the person who "owns" the specific strategic pillar the AI is meant to support.

The best Sponsor is the person who has the most to lose if the strategic goal isn't met. If the AI's goal is to reduce customer churn, the Head of Customer Success should likely be the Sponsor, with the CTO as a key Strategic Partner.

The Immediate Focus of the Strategic Sponsor:

• Before the roadmap is finalized, the Sponsor brings it to the project team for a "sanity check." By seeking their input on potential technical hurdles or "tweaks" before the final stamp of approval, the Sponsor demonstrates respect for the team’s expertise and ensures the plan is actually executable.

• They serve as the vital link between leadership’s vision and the project team’s reality. They ensure the C-Suite understands the technical "cost" of strategic pivots, while ensuring the project team understands the "why" behind shifting priorities.

• They ensure the "Stops" actually stop and the "Maintains" are protected.

• They protect the Project Manager and technical team from "scope creep" and competing departmental "asks" while the system is being stabilized.

Communicating the Road Map and Next steps

Legitimize is the practice of validating your team’s feedback, aligning leadership around immediate priorities and creating a prioritized roadmap to swiftly address concerns and limit frustration.

Staff will want to to know if they were really heard, and what is going to be done about it.

Deciding who communicates “Yeah - you have a point” is a strategic decision that depends on the level of disruption to customers and to staff. If this project resulted in High-Stakes Disruption to customers and/or to staff, breaking the trust of the customer, causing deep frustration, the CEO needs to be the one to step up. When the CEO validates the team's lived experience, it provides the psychological safety needed for everyone to re-engage.

If the issues were caught before things went entirely off the rails, then the project sponsor can likely communicate the priorities and road map with high level next steps to the staff. It is something you are going to want to thoughtfully consider to ensure a continuation of trust and buy-in.

The Goal: A Calibrated Ecosystem

If people must overextend themselves to meet a technology, the system is not correctly calibrated. In a well-calibrated ecosystem, technology supports the strategy and the people. When we align these elements, we fix a project and we build an organization capable of turning any disruption into a new way to thrive.

Next Post: Integrate. We will explore how the project team and impacted staff turn these priorities into actionable steps and daily practices.

What’s going on with Your AI implementation

Success with AI is not about the technology itself. It is about how the tool supports your people and advances your strategy.

In this 5-part series, I’m sharing how to use the ALIGN framework to troubleshoot friction in your AI implementation and turn AI into a genuine strategic advantage. We start with Absorb; the practice of surfacing what is really happening by listening to your people and your systems.

"While AI tools are now commonplace, most organizations have not yet embedded them deeply enough into their workflows and processes to realize material enterprise-level benefits... the transition from pilots to scaled impact [remains] a work in progress at most organizations." — McKinsey Global Survey, 2024

Many AI implementations are currently driven by the technology itself, rather than by the people it is meant to serve. As I learned while implementing technical projects for Denver Public Schools, technology must support a strategic initiative to be successful. If the tool does not help you ultimately serve your customers better, its a distraction.

The Diagnostic: Understanding Reality vs. Hype

To get a full-spectrum view of the Absorb phase, I recommend looking at three specific data sources. Using only one of these gives you a skewed perspective; using all three provides a clear diagnostic of where the implementation is actually stalled.

1. Conversations: The Human Story You need to have honest, psychologically safe conversations with your staff, and potentially your customers, to understand the actual impact of the implementation. While leaders often see the high-level intent, your team sees the daily friction. Their feedback reveals whether the tool is a genuine asset or just another hurdle in their workday.

2. Analytics: Beyond the Anecdotes Add objectivity to your research by reviewing the data your systems are already generating. Look for any changes between your AI-enhanced processes and your previous benchmarks.

• Are you seeing a true reduction in cycle times?

• Has the "saved" time been swallowed by new layers of troubleshooting?

• Do error rates, output volume, or login frequency align with the stories you’re hearing?

3. Observation: Watch the Workflow Finally, you must physically or virtually observe the work in motion. "Shadow" a team member as they interact with the AI tool. Watch for the "workarounds", those manual steps employees take when the technology fails to handle a specific nuance of their job. These "shadow processes" are often where the most significant implementation friction is hidden. If the workflow looks clunky or frustrating, no amount of positive data will make the implementation sustainable.

The ABSORB phase of ALIGN starts with listening to your people: Start by asking these seven questions to your team:

1. Strategic Intent: Describe your experience with AI to date. What did you believe the primary goals were for this implementation?

2. Customer Impact: How do you think our customer is benefiting from our use of AI?

3. Operational Reality: How has AI impacted your daily work? What has become easier, and what has become unexpectedly harder?

4. The Friction Check: If you could change one to three things about how we rolled this out, what would they be?

5. The Nuance Gap: What is not understood about your job and its nuances that make AI not as effective as you would like it to be?

6. The Capacity Check: What is your personal comfort level with these tools, and what support do you actually need?

7. The Adoption Check: On a scale of "Pioneers" to "Hard Pass," where would you rate your team’s willingness to work through these issues?

The Anchor Questions

Depending on where your team currently sits, use one of these two anchors to help define the path forward:

• For the team seeing success: "I consider AI to be a strategic advantage for our company because __________ happens."

• For the team experiencing problems: "I will consider AI to be a strategic advantage for our company when __________ happens."

Who to Include

In smaller organizations, include everyone. In larger organizations, ensure you have a statistically valid cross-section of staff.

Be intentional about including people who are both directly and indirectly impacted by AI. Even when one department is the formal test case, the ripple effects are real. HR may be absorbing employee frustration. Accounting may be managing operational inconsistencies. Customer-facing teams may be fielding confusion long before leaders hear about it.

The Specialist Perspective

If you have a Project Manager, Change Management specialist, or Communications lead, schedule a specific conversation with them. It must be clear that you are not assigning blame; rather, you are seeking their candid, ground-level perspective. These roles are often the first to see the "cracks" in the implementation. They likely have a deep understanding of why things are jammed, but may feel they lack the authority to fix leadership-level misalignments. By inviting them to share the "unvarnished truth" about the project's health, you gain a perspective that is often filtered out of formal status reports.

You also want representation across the full Technology Adoption Spectrum, since each group brings a different perception of risk, confidence, and readiness.

• Innovators
  Often using AI before it was formally sanctioned. They may have advocated for adoption and pushed boundaries early.

• Early Adopters
  Typically volunteered for pilots and are willing to experiment, even when outcomes are uncertain.

• Early Majority
  Came on board as part of the planned rollout once expectations were clearer.

• Late Majority
  Adopted once proof, guardrails, and social validation were firmly in place.

• Laggards
  May quietly resist or openly question the change, often reflecting deeper concerns about trust, relevance, or workload rather than the technology itself.

Everett M. Rogers Innovation Adoption Curve

A Note to Leaders: Listen, Don't Defend

The answers to these questions may be hard to hear. That discomfort is not a failure. It is data. One way to interpret it is this: the level of discomfort you feel often reflects the gap between your aspirations and current reality. The important thing is that you have started the process. From here, the work is refinement. This input is what allows you to close that gap.

To get honest, useful answers, you must first provide psychological safety:

• Listen for the point, not the delivery. People may be frustrated. Listen for the core truth they are trying to make, not how they are saying it.

• Reframe the "Complaint." Remember that people who complain are often the most committed to the ideals of the company. Their "complaints" represent a disappointment that the reality isn't meeting the potential.

• Clarify, don't challenge. If you have a question, it should be to deepen your understanding of their perspective, not to challenge it.

• Acknowledge and Close the Loop. Thank every person for their candor. Let them know management will gather this information and provide a summary of the learnings with clear next steps.

Alignment is a practice, not a one-time event

By absorbing these insights gained from conversations, data and observation, you will be able to verify if and how AI technology is supporting your people, or identify the gaps before trouble and frustrations grow.

Next Up

In the next post, we’ll look at Part 2: Legitimize: "Yeah, you have a point; here is what we’re going to do."

Is your AI strategy matching your team's reality? If you aren't sure, my 9-question ALIGNMENT snapshot is a great place to start.

Note for Leaders: If tension feels high around these issues, it can be incredibly helpful to have a neutral third party conduct these interviews and provide the synthesized summary. Contact kathy@workwisestudio.com to discuss how we can help you bridge the gap between AI hype and organizational reality.

#AIStrategy #Leadership #WorkWiseStudio #ALIGNFramework #PsychologicalSafety #OrganizationalDevelopment

Is Your Superpower also your Kryptonite

Every organization, every team, and every person has their superpower. But weirdly, that superpower can also be kryptonite.

In my previous post, we looked at how Microsoft’s self-examination enabled them to turn what could have been their kryptonite into a superpower. Every organization feels the tension between where they are and where they want to go. Today, I’m sharing the seven foundational skills that move your organization from friction to alignment.

Perhaps your company has a strong strategy and gets great energy from coming up with new ideas, but then has little patience for the discipline of execution. Or maybe you have an amazing culture and people love working there, but you come up short on strategy, leaving the team reactive rather than proactive. While it can be "fun" to put out fires together, eventually it will burn people out.

Organizational Development is the rigorous discipline of paying attention to the three forces that drive every company: Strategy, Culture, and Execution.

As an OD practitioner, my goal is to help organizations become highly effective across all three. I developed the ALIGN framework to provide a repeatable practice for understanding and transformation:

🔹 Absorb: Listening to people and systems to understand what is actually happening.

🔹 Legitimize: Turning those insights into a roadmap that the whole team actually owns.

🔹 Integrate: Making sure new ideas show up in daily work and decisions.

🔹 Grow: Helping people find the confidence to lead through the change.

🔹 Nurture: Tending to the culture so the progress sticks over the long haul.

While the ALIGN framework is a process to follow, it is also builds and strengthens new capabilities. As teams move through the ALIGN framework, they naturally develop seven foundational skills that turn a one-time project into a repeatable way of working:

1. Attention and Presence: Slowing down to see the patterns before rushing to fix them.

2. Active Inquiry: Learning to ask the kind of questions that actually uncover the truth.

3. Sensemaking: Taking a variety of perspectives and find the shared "why."

4. Relational Trust: Making it safe for people to say the hard things without fear.

5. Systems Thinking: Seeing how the people, the work, and the goals all pull on each other.

6. Reflective Practice: Regularly pausing to ask, “What are we learning here?”

7. Stewardship: Caring about where the ship is going in the long run, not just hitting today's target.

Alignment is the bridge between a brilliant idea and a reality that doesn't fall apart. It’s how we make sure our superpowers are used to build what’s next, rather than just exhausted by the friction of today. As these seven skills become part of your organizational DNA, strategy, culture, and execution consistently align for work that is meaningful, sustainable, and impactful.

The ALIGN Framework: A High-Performance Discipline for Strategic Execution

In the high-stakes race of Silicon Valley, the default setting is "speed." But as we enter the AI era, the rules have changed. Microsoft understood a fundamental truth: In the AI era, trust is a non-negotiable element to sustain your competitive advantage. To move forward, they had to have the bravery to look inward and address the legitimate weaknesses of their systems.

In early 2024, Microsoft faced its defining moment. Facing a sobering report from the Cyber Safety Review Board (CSRB), CEO Satya Nadella paused the feature treadmill. He chose security over speed. By reverse-engineering this move through the ALIGN lens, we can all learn from this masterclass in strategic discipline.

The ALIGN framework is built for this level of high-stakes decision-making. It is a high-performance discipline that asks leaders to absorb uncomfortable truths, legitimize hard priorities, redesign systems, and stay the course when easier options are available. It requires the bravery to take in stinging criticism without getting defensive, the risk to deprioritize profitable features, and the grit to stay the course when the market demands a quick fix.

By backward-engineering the ALIGN framework to the steps Microsoft took to address their challenges, I demonstrate that ALIGN is a rigorous blueprint for achieving operational effectiveness and sustainable trust in the most complex global environments.

Absorb: The Bravery to Listen

Alignment begins with the courage to Absorb what your customers, staff, shareholders, regulatory agencies, and other stakeholders tell you. Sometimes it is great news, and sometimes it is a set of really uncomfortable truths.

Following the Storm-0558 cyberattack, Microsoft didn’t deflect the Cyber Safety Review Board’s (CSRB) findings. Leadership sat with the feedback, absorbing the reality that their current pace was creating vulnerabilities. They took in the "trillions of unique signals" and the lessons from adversaries like Midnight Blizzard to understand the gap between where they were and where they needed to be. This is where many leaders fail due to ego, but Microsoft utilized this input to fuel their pivot rather than fuel a defense.

Legitimize: Turn Insights into a Roadmap

Insights only gain power when leadership owns them together.

Microsoft Legitimized the crisis by turning it into the Secure Future Initiative (SFI). Satya Nadella clarified the priority: "If you’re faced with a tradeoff... the answer is clear: Do security."

This turned a real point of tension into a roadmap that the entire C-suite signed their names to, prioritizing it above all other innovations.

Integrate: Redesign the Machine

Strategy is only ideas until it’s Integrated into daily work.

This is the "gritty" work of systems and structures redesign. Microsoft wove security into daily operations.

Leadership also let staff know they would be invited into the process sooner rather than later to “solicit your feedback and input on how we can implement them effectively and efficiently. We want this to be a collaborative and transparent effort that involves all of you as key stakeholders and contributors.”

They tied senior leadership compensation directly to security milestones and added a "Security Core Priority" to the performance reviews of all 220,000+ employees.

Grow: Building Resilience, Not Just Headcount

Progress endures when teams expand their capacity.

Microsoft Grew its organizational muscle by dedicating the equivalent of 34,000 full-time engineers to security work. They upskilled staff through the Microsoft Security Academy, ensuring their people had the tools and the confidence to carry this change forward. They built the tools and the "technical and operational rigor" necessary for their people to carry this change forward.

By training teams to prioritize security over new features, they built the resilience needed to defend against increasingly sophisticated threat actors.

Nurture: The Discipline of Momentum

Momentum is sustained when practices are embedded over time, yet this is where most transformations fail. Organizations often lack the stamina to stick with a pivot, eventually pulling resources or shifting focus to the next "shiny object."

Microsoft continues to Nurture this culture by resisting the urge to declare an early victory. They utilize an internal listening network to check progress and ensure that security remains the default setting, not a temporary project. This long-term grit directly led to the decommissioning of 560,000 unused tenants, systematically cleaning up "security debt" that had been ignored for years.

Critically, this effort continues through bi-weekly governance meetings at the highest levels and a public commitment to transparency through recurring SFI progress reports, ensuring that security remains a permanent operational pillar rather than a finished task.

The Result: A trusted partner

By 2026, Microsoft has reestablished its identity as the world's most trustworthy business partner.

The ALIGN framework is a high-performance discipline that asks leaders to absorb uncomfortable truths, legitimize hard priorities, redesign systems, and stay the course when easier options are available. By reverse-engineering this transformation, we see that the ALIGN framework is about effective organizational transformation.

References

• Microsoft 2024 Proxy Statement (SEC Filing): Details on SLT bonuses and CEO accountability.

• Official Microsoft Blog: "Security Above All Else": The foundational mandate for the 220,000+ employee pivot.

• Microsoft SFI Progress Report (Sept 2024 Update): Data on decommissioning 560k tenants and engineer dedication.

• CSRB Report: Review of Microsoft Exchange Online Intrusion: The external report that triggered the realignment.

About the ALIGN Framework

The ALIGN Framework (Absorb, Legitimize, Integrate, Grow, Nurture) moves an organization from high-level strategy to operational reality.

I help organizations achieve true alignment by auditing current states, identifying friction points, and designing systems that turn values into measurable outcomes.

Alignment in Action: Practices to Retain Customers and Sustain Staff

In my previous post, I presented the idea that the real test of alignment is that it effectively responds to the needs of the customer and ideally makes their life easier. Identifying where friction exists is only the first step. The deeper challenge is the internal work of re-tooling the organization to eliminate that friction without burning out your people.

To move beyond "listening" and into "aligning," leaders need specific practices that bridge the gap between customer feedback and daily execution. Here is how to apply the ALIGN framework as a set of operational disciplines that sustain both the business and the staff.

1. Absorb: The "Root Cause" Discipline

Listening to a customer is the start; understanding why the system failed them is the practice.

• The Practice: Use the "Five Whys" to look past the surface. For example, if a customer is frustrated because an order was delayed, don't stop at "human error."

  • Why was it delayed? The warehouse didn't get the shipping authorization.

  • Why? The system flagged a missing tax ID.

  • Why? The sales rep didn't know it was required for this region.

  • Why? The software doesn't ask for it during initial entry.

  • Why? We designed the software to be "fast" for sales, but inadvertently created a bottleneck for the customer.

• The Goal: To absorb the reality of the system, not just the symptom. This prevents "quick fixes" that actually create more work for your staff later.

2. Legitimize: The Capacity-Based Promise

Alignment fails when we make promises to customers that our current staffing levels cannot realistically keep.

• The Practice: The "Commitment Check." Before setting a new service standard (like a 24-hour turnaround), ask the team: "What has to be deprioritized to make this happen?"

• The Goal: To legitimize the constraints of your staff. If you don't have the resources for a four-hour turnaround, don't promise it. Alignment means matching the External Promise to the Internal Capability. A slower, honest promise builds more trust than a fast, broken one.

3. Integrate: The "Friction-Free" Policy Audit

Integration is about ensuring your internal rules don't create unnecessary "busy work" for staff or hurdles for customers.

• The Practice: The "Two-Way Value" Test. Review an internal policy and ask: "Does this serve the customer, or just our internal convenience? And does it sustain the staff, or just complicate their day?"

• The Goal: Delete policies that force staff to act as "gatekeepers" against the customer. By simplifying the rules, you reduce the cognitive load on your team and the frustration for your client.

4. Grow: Cross-Functional Empathy

In a lean organization, alignment depends on people understanding how their work affects the next person in line.

• The Practice: "Internal Shadowing." Have a member of the operations team sit with a customer-facing staff member for one hour a month to see the direct results of their work.

• The Goal: To grow an understanding of the "ripple effect." When staff see how a small error in the back office creates a massive headache for the front line, they naturally align their efforts to prevent it.

5. Nurture: The "Sustainably Better" Loop

We must commit to improvements long enough for them to stick, but we must also monitor the health of the team delivering them.

• The Practice: The 90-Day Health Check. Three months after implementing a change, ask two questions:

  1. Is the customer experience smoother?

  2. Is the team's workload manageable?

• The Goal: To nurture a culture where "success" is defined by a satisfied customer and a sustained team. If the customer is happy but the staff is quitting, the alignment is a temporary illusion.

The Resilient Path Forward

In times of uncertainty, your most valuable assets are your customers' trust and your employees' commitment. If you overpromise and underdeliver, you risk losing both.

True alignment is the art of creating a frictionless experience for the customer through a sustainable workflow for the staff. When those two are in sync, the organization becomes both the reliable business partner and the reliable employer.

ALIGN as A Customer EXPERIENCE STRATEGY

Peter Drucker, one of the most influential thinkers in modern management, made a simple and enduring point: organizations exist to serve their customers.

Internal alignment only matters if it improves the experience of the people they serve. That idea is easy to endorse and surprisingly easy to lose sight of in daily operations. Many organizations achieve strong internal alignment around efficiency, cost control, or process optimization, yet the customer experiences confusion, friction, or wasted time. Alignment that only works internally is incomplete. The real test of alignment is whether strategy, culture, and execution come together in ways that make it easier for customers to get what they need, do their work, and trust the organization they are dealing with.

Customer dissatisfaction may not be about the product or service itself, but about how misaligned systems show up in daily interactions. Automated phone trees that consume time before reaching a human. Scheduling systems that book appointments without syncing calendars. Sales or service handoffs where no one seems fully accountable. From the inside, each of these may make sense. From the outside, they feel disjointed, inefficient, and disrespectful of time.

Customers rarely articulate this as “misalignment.” They feel frustrated confused, delayed, discounted,  These various forms of friction lead the customer to quietly go elsewhere.

When misalignment affects your customers’ ability to do their work, the cost compounds quickly. You may not get a second chance to make it right.

Walk the Customer Journey Together

One of the most effective ways to address this is to walk your customer journey as a team.

Start internally. Identify where you believe the experience works well and where you already know friction exists. Pay particular attention to handoffs, policies, and moments where customers are asked to repeat information or wait unnecessarily.

Then engage customers directly. Not through a survey alone, but in conversation. Surveys have their place, but they often ask customers to do interpretive work for you. For many, that is just another irritation. A conversation, on the other hand, signals that their experience matters. Invite customers to lunch. Bring coffee to their workplace. Ask for 30 minutes of their time. Listen carefully.

Share what you believe is working and where you see opportunities to improve. Ask if they agree. More often than not, they will add insights you were not aware of or confirm issues you suspected but had not fully understood. Conversely, ask them first what works for them, or what doesn’t work for them. They will have opinions.

If they offer areas for improvement, do not defend or explain why things are the way they are. Thank them. Let them know how valuable their input is. Follow up with a note that acknowledges what you heard and what you plan to address.

Then, three months later, check back in. Ask how things feel now. And three months later, check in again. That continuity builds trust and signals commitment to them.

Using ALIGN Through the Customer Lens

The ALIGN framework offers a practical structure for doing this work with intention:

• Absorb what customers tell you. Listen without explanation or justification. Pay attention to patterns, not just isolated comments.

• Legitimize what you hear. When customer feedback mirrors what your team has already identified, name that alignment. Ask customers what matters most to their business and which improvements would make the biggest difference.

• Integrate those priorities into policies, processes, and practices. This may mean revising handoffs, simplifying steps, or clarifying ownership.

• Grow capability where needed. Ensure staff have the skills, tools, and training to deliver on changes. In some cases, customers may also need support or guidance as processes evolve.

• Nurture the work over time. Maintain a feedback loop with customers. Commit resources long enough for changes to take hold. Customers experience change fatigue too. Staying with improvements long enough to deliver results matters as much as making the change itself.

Alignment, Felt Externally

Alignment shows up in the customer’s experience of working with you. Customers experience alignment when it is easy to place an order, speak with the right person, resolve an issue, or suggest an improvement. Work flows smoothly, information is clear, and interactions respect the customer’s time and effort.

When alignment is strong, customers feel confident and supported. They experience consistency across touchpoints and trust that the organization will follow through. These experiences build credibility and reinforce long-term relationships.

Treating alignment as a customer experience strategy ensures that internal coordination translates into external trust, loyalty, and sustained results.

The Alignment snapshot

The ALIGN Framework

Part 6B of the ALIGN Series: The Alignment Snapshot, Final Post of the Series
Absorb | Legitimize | Integrate | Grow | Nurture

In this series of posts, I introduce each stage of the ALIGN Framework, a method designed to align leadership and engage staff, connecting strategy, culture and execution My premise is simple: when leadership is aligned, brilliant ideas take flight, and when staff is engaged early to shape the details, those ideas are far more likely to be adopted.

At this moment, many organizations are navigating competing demands, shifting expectations, and increasing complexity in their operating environment. Whether these conditions feel like opportunity, challenge, or both, an organization’s ability to respond effectively depends on how aligned it is.

Alignment is a set of observable conditions that allow an organization to move with coherence and purpose.

An aligned organization demonstrates the following:

• Leadership agrees on priorities and maintains a shared focus

• Staff understand the direction of the organization and have input into matters that affect their work

• Resources are allocated in ways that reflect stated priorities

• People have the capacity to deliver on expectations and are supported in building new capabilities as demands evolve

• Communication flows in both directions, with space for questions, concerns, and feedback

• Decision-making is clear and predictable

• The culture supports people in doing their best work

• There is a shared understanding of what success looks like and a commitment to that success.

When these conditions are present, effort translates into progress. Strategy flows into  execution. Culture supports the work at hand. People understand how their contributions connect to the organization’s goals.

The Work Wise Studio Alignment Snapshot is a short diagnostic designed to help you assess these conditions. It offers a practical way to take stock of where alignment is strong and where it may need attention.

If you are curious about your organization’s alignment, I invite you to complete the Alignment Snapshot. I will provide you with your results with tips on how to improve alignment. I also offer a complementary twenty-minute conversation to walk you through your results and answer your questions. Sometimes simply naming what is present, with an objective partner, creates clarity. We can explore additional supports and how they could strengthen focus, effectiveness, and results.

In the spirit of the Studio Practice, the Alignment snapshot helps you study what is working, surface what needs attention, and decide what to craft next.

ALIGN as a Möbius Strip: The Rhythm of Continuous Alignment

The ALIGN FRamework Part 6A of the ALIGN Series
Absorb | Legitimize | Integrate | Grow | Nurture

In this series of posts, I introduce each stage of the ALIGN Framework, a method designed to align leadership and engage staff. My premise is simple: when leadership is aligned, brilliant ideas take flight, and when staff is engaged early to shape the details, those ideas are far more likely to be adopted. Staff feel valued, heard, and involved. It is a win win for the organization.

This post in the ALIGN series reflects on the framework as a whole and the rhythm it is designed to support.

My premise is this: In most organizations, conditions, priorities, and people are constantly evolving. Alignment, therefore, is not a fixed state to achieve and preserve. It is an active practice that requires ongoing attention. The ALIGN framework was created for this reality. It helps organizations move through change with coherence and curiosity, keeping leaders and staff connected to what matters most as circumstances shift.

The Five Phases of ALIGN

Each phase of ALIGN carries a distinct focus and a guiding question. Together, they form a rhythm that moves from awareness to sustained effectiveness, building momentum as the organization learns, adapts and grows.

Absorb

Core Focus: Pay attention to what is really happening

Key Question: What is the experience of our stakeholders, including customers, staff, vendors, and shareholders, relative to a specific issue or current state?

Legitimize

Core Focus: Turn insight into shared understanding

Key Question: What matters most for us right now?

Integrate

Core Focus: Translate direction into action

Key Question: How do we turn our priorities into daily work?

Grow

Core Focus: Expand capacity and confidence

Key Question: What resources and capabilities do we need to meet the demands of our work?

Nurture

Core Focus: Sustain progress and attention

Key Question: How do we maintain focus long enough to achieve meaningful results?

These phases are not steps to complete and move past. They are patterns to return to. Each phase informs the next, and over time, the work naturally loops back to the beginning.

The Möbius Strip as a Symbol of Alignment

At first glance, ALIGN can appear to be a linear process with a clear start and finish. In practice, it behaves very differently. It functions more like a Möbius strip, continuous, fluid, and without a clear dividing line between beginning and end. The Möbius strip offers a way to see alignment as continuous rather than linear, where reflection and action constantly shape one another.

A Möbius strip is a simple loop with a twist. It has only one surface and one edge. When you trace your finger along it, you never cross a boundary. You simply return to where you started, seeing it from a new perspective.

That is what alignment feels like when it is working well. Awareness becomes direction. Direction becomes practice. Practice becomes learning. Learning brings you back to awareness, wiser and more attuned to what the organization needs next.

Inside Becomes Outside, Outside Becomes Inside

A Möbius strip blurs the boundary between inner and outer. What appears internal continuously becomes external, and what begins outside loops back in. The same dynamic is at work in organizations.

Signals from the marketplace, customer needs, expectations, frustrations, and responses inform what the organization must prioritize, design, and deliver. At the same time, what happens inside the organization, leadership values, trust, clarity of direction, and ways of working shapes how those products and services are conceived and carried out.

Culture, communication, and coherence inside the organization show up directly in the experience customers, clients, and partners have on the outside. In turn, how the marketplace responds feeds back into leadership priorities and organizational focus.

Alignment lives in this continuous exchange between the organization and the world it serves. It is an internal practice with external impact. When priorities, decisions, and ways of working are coherent inside the organization, that coherence shows up in how customers, clients, and partners experience it.

The Flow of Ongoing Work

ALIGN is not a project to complete. It is a practice to sustain. It replaces the idea of change as an event with a more grounded understanding that change is constant, and alignment is what allows organizations to move through it effectively.

Each turn through Absorb, Legitimize, Integrate, Grow, and Nurture represents a cycle of learning. With each pass, leaders and teams become more skilled at noticing what matters, making informed decisions, and adjusting with intention. Over time, ALIGN builds the organizational muscle required to pursue strategic goals without losing coherence or momentum.

The Discipline of Returning

The end of one cycle naturally becomes the beginning of the next. Leaders who consistently return to listening, reflection, and inquiry keep alignment alive. They create cultures where attention is sustained and adaptation feels normal rather than disruptive.

ALIGN supports a shared practice of noticing, deciding, learning, and adjusting together. This rhythm allows organizations to respond to change without losing their footing or their sense of purpose.

Closing Reflection

Alignment is a dynamic relationship between people, priorities, and purpose. Like a Möbius strip, it holds continuity and change in the same motion.

When alignment is treated as a shared leadership practice, adjustment becomes a matter of refinement rather than overhaul. Each cycle through ALIGN deepens understanding. Each return strengthens trust. Each conversation renews commitment to the work the organization exists to accomplish.

In practice: organizational reviews, reflection cycles, culture stewardship sessions, and leadership check-ins that keep attention focused and momentum grounded.

Nurture: Build the Habit of Ongoing Stewardship

Nurture: Part 5B of the ALIGN Series
Absorb | Legitimize | Integrate | Grow | Nurture

In this series of posts, I introduce each stage of the ALIGN Framework, a method designed to align leadership and engage staff. My premise is simple: when leadership is aligned, brilliant ideas take flight, and when staff is engaged early to shape the details, those ideas are far more likely to be adopted. Staff feel valued, heard, and involved. It is a win win for the organization.

In the Nurture phase of the ALIGN framework, the work is about sustaining momentum once priorities are in motion. Momentum is sustained when practices are embedded into daily operations and supported with consistent attention and resources over time.

Nurture focuses on leadership stewardship. It is where leaders stay present to the work, ensure resources remain aligned, review progress against expectations, and make deliberate adjustments as conditions change. Rather than assuming momentum will sustain itself, this phase recognizes that results are achieved when focus is maintained and accountability remains active.

In this stage, leaders are reinforcing what matters, checking whether efforts are producing the intended outcomes, and intervening early when progress begins to drift. Nurture is how organizations protect the investment they have already made and ensure that alignment continues to serve performance, effectiveness, and results.

Make Reflection Routine

After the launch of any initiative, schedule a regular cadence for check-ins that invite conversations. In addition to the typical statistics of time, budget and risks/mitigation,  ask open ended question to further understand how things are going.

·         What’s working as intended?

·         What surprised us?

·         What is going better than expected?

·         What feels harder than it should?

·         Does anything feel out of sync with our expectations?

·         Are we noticing any new opportunities?

 These conversations can begin with a project team and continue with staff  once an initiative transfers over to regular operations. They can also be conversations among the management team, and then taken to staff for further exploration

Ideally, the conversation flows in both directions, with leaders and staff sharing their experience and perceptions from their roles.

Group Problem Solving

Encourage staff to surface emerging issues, not just successes.

When leaders say they don’t want anyone to come to them unless they have a solution, they are increasing the risk that they will not hear about problems because people don’t have the information they need to solve the problem.

Some people are really good at spotting problems and need other people to identify the solutions. By discussing challenges, problems, obstacles (what ever word you want to use), it allows the team to utilize the collective team strengths.

Coaching Conversations

In the Nurture stage, it is important to stay connected to the development plans established during the Grow phase. Growth does not end once new skills are introduced; it requires continued attention and reinforcement. Whether someone is a leader, manager, or front-line staff member, people need ongoing support to build and sustain the capacity their role requires.

At its core, coaching is about learning from experience. It helps identify what is working and should be strengthened, and what is not working and should be adjusted. When pressure increases and demands pile up, the temptation is often to abandon developmental work in order to focus on immediate problems. While understandable, this short-term focus can prevent people from developing the skills and judgment that would reduce those recurring “fires” over time.

There will also be moments when people are putting in significant effort without seeing the progress they expected. In these situations, leadership plays a critical role. Acknowledging effort matters, but it is equally important to shift the conversation toward what has been learned through that effort. If progress remains limited and learning is not occurring, those conditions provide valuable information. They signal the need to revisit initial assumptions, reassess the approach, and consider what might need to change.

One-on-one coaching conversations are especially effective in supporting this kind of learning and performance improvement. They create space for reflection, honest feedback, and problem-solving in a way that is difficult to achieve in staff meetings or project team settings. Over time, these focused conversations help people build confidence, capability, and resilience, reinforcing the alignment the organization is working to sustain.

Celebrate Success

Momentum thrives when recognition is built into the feedback look . People need to see that their efforts matter.

Create visible ways to share stories of progress: short internal updates, dashboards that track meaningful indicators, or brief showcases where teams present what they’ve learned. When success is named and shared, it naturally reinforces alignment.

Sustain Focus on What Matters

Nurture is the ongoing work of staying with priorities as conditions evolve and ensuring that focus, resources, and accountability remain aligned with the outcomes the organization is trying to achieve.

Over time, pressures shift, new demands emerge, and assumptions made early in the work may no longer hold. Ongoing stewardship means leaders regularly stepping back to assess whether the work is still delivering the results it was designed to produce and whether adjustments are needed to keep it effective.

When this kind of review becomes routine, momentum grows and is sustained through leadership attention, clear accountability, and a willingness to make timely course corrections. In this way, Nurture ensures that progress continues  because it remains important.

Nurture in Practice

In practice: reflective team huddles, quarterly alignment reviews, recognition rituals, coaching check-ins, storytelling sessions, and leader reflection prompts that keep the purpose visible.