Article
Conflict in MSMEs usually appears as personality tension, but the root cause is often unclear work design. Who promised the delivery date? Who approved the discount? Who confirmed stock? Who owns customer communication? Who follows up payment? When these answers are not explicit, every missed handoff becomes a blame conversation.
The Week 9 macro backdrop makes this practical. Uneven demand and rising input costs increase stress inside the business. Sales wants to close quickly. Finance wants advance and margin control. Operations wants realistic timelines. Purchase wants supplier clarity. HR or admin wants people stability. None of these functions is wrong. The problem is that the business has not defined how trade-offs are decided.
Conflict resolution should begin before conflict starts. Define decision rights. Sales can commit only within approved price and delivery rules. Purchase can order only within budget or with approval. Operations can reject unrealistic timelines with documented reasons. Finance can block credit extension when overdue thresholds are crossed. Team leads can escalate exceptions, but they must bring facts, not accusations.
Use a three-step method for disputes. First, separate facts from interpretation: what was promised, when, by whom, with what document or message? Second, identify business impact: delay, margin loss, customer risk, safety risk, cash impact or morale impact. Third, decide the next action: who will call the customer, who will revise the schedule, who will approve cost, who will update the SOP, and by when.
The owner should avoid becoming the judge for every disagreement. Instead, become the designer of escalation rules. Low-impact issues should be solved by team leads within 24 hours. Customer-impacting issues should be escalated the same day with a proposed solution. Financial or legal risks should go to the owner or designated senior person immediately. Repeat conflict should trigger process correction, not repeated scolding.
Documentation matters, but it should be light. A one-page conflict log can record date, issue, teams involved, root cause, decision, owner and prevention step. Over time, patterns become visible: unclear quotations, late stock updates, weak onboarding, missing approvals, poor handovers, incentive design or one manager's communication style. The log is not for punishment. It is for reducing repeat friction.
The CHRO action this week: publish a conflict-resolution rule for team leads. No public blame. Bring facts. State business impact. Propose one next action. Escalate within defined timelines. Close the loop in writing. A growing MSME cannot eliminate conflict, but it can stop conflict from silently reducing speed, quality and trust.