Alex Kowalkoski

leadership · March 9, 2026

Navigating Conflict: A Leader's Handbook for Small Business Dynamics

By , keynote speaker

Related keynote: The Cost of Being Invisible · Book Alex for your event

On this page
  1. The hard truth: Conflict is draining your margin, momentum, and mindshare
  2. Measure the cost of conflict before you try to fix it
  3. The ALEX Playbook: Practical conflict resolution for small businesses
  4. A — Assess the signal and type the conflict
  5. L — Listen privately, then jointly (fast)
  6. E — Engineer clarity: roles, decisions, and “done”
  7. X — Execute and inspect
  8. Tools and scripts you can use today
  9. Real-world examples from scaling small teams
  10. Prevent conflict by design: Build the system first
  11. Remote and hybrid nuance
  12. When to coach, when to restructure, when to part ways
  13. Metrics that prove your conflict system is working
  14. The cost of disruption, paid forward
  15. Final word and next step

The hard truth: Conflict is draining your margin, momentum, and mindshare

If you’re a small business owner, you’re not losing sleep over your P&L—you're losing it over two adults who won’t talk to each other, a passive-aggressive Slack thread, the client account that’s at risk because sales and delivery are finger-pointing, and the top performer who’s suddenly “checking out.” I’ve been there. I’ve built and scaled multiple companies, and the consistent brake on growth wasn’t a lack of ideas or pipeline—it was unresolved conflict stealing time, trust, and traction.

Here’s the no-nonsense reality: conflict is not a “people problem.” It’s a leadership and systems problem. And it’s solvable with clear frameworks, fast intervention, and cultural guardrails. This is the playbook I use with teams when the cost of disruption starts to show up on the balance sheet.

Measure the cost of conflict before you try to fix it

What gets measured gets taken seriously. In small teams, every conflict is amplified because roles overlap and every handoff touches revenue. Quantify it.

  • People-hours lost: number of people involved x hours spent venting, revisiting decisions, reworking deliverables
  • Delay cost: impact on delivery dates, churn risk, discounting to appease unhappy clients
  • Leadership drag: hours you and your managers spend refereeing instead of selling, building, or shipping

Example: Two team leads are at odds. Four 1-hour “alignment” meetings in a week with six people each. That’s 24 hours. At a loaded cost of $60/hour, that’s $1,440. Add a 1-week delivery delay that forces a 10% discount on a $30,000 project—$3,000 gone. You just burned $4,440 to avoid a hard 45-minute conversation.

When you put a number on it, the path is obvious: act fast, act clearly.

The ALEX Playbook: Practical conflict resolution for small businesses

I use a four-step framework to move teams from friction to flow. It’s direct, pragmatic, and designed for busy founders and operators.

A — Assess the signal and type the conflict

Not all conflict is the same. Type it before you treat it.

  • Task conflict: disagreement about what work to do
  • Process conflict: how the work gets done and by whom
  • Role conflict: unclear decision rights or overlapping responsibilities
  • Values/confidence conflict: perceived disrespect, safety, or trust issues
  • Capacity conflict: workload vs. resources—often mislabeled as “attitude”

Once you type it, you can pick the right tool: SOP update, RASCI clarifications, decision framework, coaching, or in rare cases, exit.

Red flags you should never ignore:

  • Slack sarcasm and “us vs. them” language between teams
  • Two leaders avoiding each other and triangulating through you
  • Rework and late handoffs becoming “normal”
  • High performers going quiet in meetings

L — Listen privately, then jointly (fast)

Use the 24-hour rule: as soon as you spot a pattern, meet 1:1 with each person within 24 hours. Your script is simple:

  • Situation-Behavior-Impact (SBI): “In Tuesday’s handoff, when you bypassed QA and sent files direct to the client, it created rework and undermined the process.”
  • Ask: “Help me understand your intent and constraints.”
  • Boundaries: “This behavior can’t continue. We need a joint plan today.”

Then, bring them together within 48 hours. No public call-outs. No “HR theater.” Keep it short and structured.

Joint conversation structure (30–45 minutes):

  1. State the business goal at risk (client, deadline, margin)
  2. Each person shares their view using SBI—no interruptions
  3. Identify conflict type(s)
  4. Commit to a shared outcome and concrete next steps
  5. Document agreements in writing before leaving the room

E — Engineer clarity: roles, decisions, and “done”

Most conflicts thrive in ambiguity. Kill ambiguity with precision.

Use the 6Q Alignment Checklist:

  • Why: What outcome are we optimizing for? (revenue, speed, quality)
  • Who: Who owns the decision? Who’s consulted? Who’s informed? (RACI)
  • What: What does “done” look like? Include acceptance criteria.
  • When: Deadlines and SLAs between roles (e.g., design to dev: 24 hours for review)
  • Where: Source of truth for assets, decisions, and updates
  • How: The tool/process used (ticketing, SOP links, change control)

Write it down. Share it in the project’s source of truth (not buried in chat). Confirm with both parties: “Is this workable? Anything missing?” Secure explicit yeses.

X — Execute and inspect

Agreements without inspection are wishes. Put it on your calendar to follow up in 7 days and 30 days.

  • 7-day check-in: “Are we meeting SLAs? Any friction points?” Adjust micro-processes.
  • 30-day review: “What’s improved? What still drags?” Decide if coaching, training, or role changes are needed.

If the same behavior resurfaces after clear agreements and support, you’re in values/behavior territory. Move to a formal performance plan or part ways. Respectfully. Quickly.

Tools and scripts you can use today

Here are assets I install in small teams to reduce conflict noise by 50% or more in 90 days.

  1. Ways We Work (one-page cultural guardrails)
  • We disagree in private, decide in the room, and commit in public.
  • We use SBI to give feedback within 24 hours.
  • We never triangulate—if you have a concern with someone, talk to them first, then your manager.
  1. Decision rights framework (RAPID/DACI hybrid)
  • One owner decides (D)
  • Drivers propose
  • Approvers sign off (limited, time-boxed)
  • Consulted are heard, not vetoed
  • Informed get the outcome
  1. SLAs between teams
  • Sales to Delivery: 48 hours for Statement of Work review
  • Design to Dev: 24 hours for asset QA
  • Support to Product: Bug triage within 2 business days
  1. Meeting scripts
  • 1:1 opener: “What’s working? What’s stuck? What do you need from me?”
  • Tension triage: “Name the impact. Type the conflict. Solve the smallest thing that moves us forward.”
  1. Retrospective format (monthly, 60 minutes)
  • Start: One win per person
  • Stop: One behavior/process we kill this month
  • Continue: What’s working we double down on
  • Decide: Top 2 process improvements, owners, due dates
  1. Performance plan trigger criteria
  • Repeated boundary violations after written agreements
  • Erosion of team trust measured by feedback/NPS
  • Missed commitments without transparency or recovery plans

Real-world examples from scaling small teams

Example 1: Sales vs. Delivery standoff

  • Context: 22-person software shop. Sales promised features that delivery couldn’t hit. Slack battles, clients sensed it.
  • Action: We mapped a simple SLA, installed a Deal Review gate with one Approver, and created a “Red Flag” tag for risky promises.
  • Result: Discounts dropped 70% in a quarter, cycle time improved 14%, and two “problem people” became top collaborators once the system carried the weight.

Example 2: Senior operator undermining a new manager

  • Context: E-commerce brand with 35 employees. A veteran ops lead rolled eyes in meetings and “quietly corrected” the new manager.
  • Action: 1:1 SBI conversation, then a joint alignment. Clarified decision rights (manager owns staffing and prioritization). Set a 30-day behavior plan: no cross-assignments without manager approval, weekly syncs with clear agendas.
  • Result: Hand-offs stabilized, error rate dropped 22%, and the veteran became a peer mentor—or would have been exited if behavior hadn’t changed. The plan made the stakes clear.

Prevent conflict by design: Build the system first

You can resolve conflicts one by one. Or you can install guardrails so most never ignite.

  • Role clarity with RASCI: Define who’s Responsible, Accountable, Supporting, Consulted, and Informed for your top 10 workflows.
  • Definitions of Done (DoD): For recurring deliverables, write acceptance criteria once and reuse them.
  • Decision logs: A single page capturing key choices, owners, and dates. Cuts “we already decided this” by 80%.
  • Escalation ladder: Team → Manager → Cross-functional lead → Founder. Each rung has a 24-hour SLA.
  • Feedback training: Teach SBI + curiosity questions. It’s a 90-minute workshop that pays back forever.
  • Digital hygiene: Source of truth beats scattered chat. Use your PM tool for scope and decisions; use Slack for updates.
  • Psychological safety: Safety isn’t coddling; it’s clarity. People speak up when it’s safe to be honest and unsafe to be vague.

Remote and hybrid nuance

Distance amplifies misunderstanding. Codify what in-office serendipity used to solve.

  • Default to written first: summarize decisions and action items in the channel of record.
  • Emojis and tone: be explicit—“strong opinion, light hold” or “draft, not a decree.”
  • Cameras on for conflict conversations; cameras off for focused work. Protect deep work windows.
  • Time zone fairness: rotate meeting times; publish notes and recordings.

When to coach, when to restructure, when to part ways

As a leader, your job is to differentiate between skill gaps, system gaps, and values gaps.

  • Coach if: The issue is skill-based (feedback, prioritization) and the person engages in good faith.
  • Restructure if: The conflict is role-based. Clearer decision rights or workload shifts will fix it.
  • Part ways if: Repeated boundary violations, refusal to commit to agreed behaviors, or values mismatch. Preserve the team’s trust bank. Move quickly, humanely, and legally.

If you’re hesitating because “we can’t afford to lose them,” run the COST check. If keeping them reduces speed, burns trust, and costs customers, you can’t afford to keep them.

Metrics that prove your conflict system is working

Track these monthly. If they trend in the right direction, the culture is getting healthier.

  • On-time delivery rate
  • Rework percentage
  • Team NPS or eNPS
  • Voluntary turnover of A-players
  • Escalations per month (expect a short-term rise as people learn to surface issues early, then a steady decline)
  • Average cycle time from idea to shipped

Tie them to business outcomes: churn reduction, higher close rates (prospects feel the confidence), and gross margin improvement.

The cost of disruption, paid forward

My philosophy is simple: disruption has a cost. You either pay it in confusion, churn, and chaos—or you invest it in clarity, speed, and trust. Small businesses don’t have a lot of slack in the system. That’s your advantage. You can change fast.

Here’s your 7-day challenge:

  • Day 1: Identify one live conflict. Type it (task, process, role, values, capacity).
  • Day 2–3: Run the 24-hour 1:1s and the 48-hour joint conversation. Use SBI.
  • Day 4: Install one guardrail (Ways We Work or a decision log).
  • Day 5: Clarify one SLA between two roles or teams.
  • Day 6: Document a Definition of Done for your most common deliverable.
  • Day 7: Schedule your 7-day follow-up. Measure rework and cycle time for that workflow.

Do this, and you’ll feel the pressure release, the team refocus, and the numbers move.

Final word and next step

Conflict isn’t a detour; it’s the work of leadership. Handle it with speed, structure, and respect, and you’ll unlock capacity you didn’t know you had. If you want help installing this system—training your managers on SBI, codifying decision rights, and building SLAs that stick—bring me in for a Conflict-to-Clarity workshop. Your team will get a shared language, your leaders will get a repeatable playbook, and you’ll get your time and margin back.

The takeaway: Treat conflict like a cost center you control. Measure it. Address it in 48 hours. Engineer clarity. Inspect the outcome. That’s how small businesses scale without tearing at the seams.

Bring this topic to your stageExplore the keynote: The Cost of Being Invisible →

Related articles

Ready to ignite your next event?

Alex books 3–6 months in advance. Response within 48 hours.

Request a Speaker Quote