top of page

By:

Quad Najmi and PTI

17 June 2026 at 5:11:32 pm

Uddhav faces another rebellion; decision today

Six Lok Sabha MPs trying to move away; picture may be clear at today’s Parliamentary party meeting in New Delhi AI generated image Mumbai: A cloak-and-dagger crisis engulfing the Uddhav Thackeray-led Shiv Sena has landed at the door of the Lok Sabha Speaker, with the party urging him to guard against any unlawful defection and issuing a whip directing its MPs to attend a meeting in Delhi on Thursday. Amid the escalating crisis, a group of rebel Shiv Sena (UBT) leaders is learnt to have met...

Uddhav faces another rebellion; decision today

Six Lok Sabha MPs trying to move away; picture may be clear at today’s Parliamentary party meeting in New Delhi AI generated image Mumbai: A cloak-and-dagger crisis engulfing the Uddhav Thackeray-led Shiv Sena has landed at the door of the Lok Sabha Speaker, with the party urging him to guard against any unlawful defection and issuing a whip directing its MPs to attend a meeting in Delhi on Thursday. Amid the escalating crisis, a group of rebel Shiv Sena (UBT) leaders is learnt to have met Speaker Om Birla informally on Wednesday, claiming the support of six of the party's nine MPs in the Lower House, sources said. Thursday's high-stakes meeting in Delhi will legally and physically define whether Uddhav Thackeray retains his parliamentary strength or faces another devastating party division, the third since Raj Thackeray split Shiv Sena in 2006. Sources in Sena (UBT) said the rival camp still doesn't have the support of six MPs. They claim two of the six rebels have reportedly changed their mind. In a swift counter-offensive to contain the damage, the party high command issued a mandatory three-line whip, summoning an emergency parliamentary party meeting in New Delhi on Thursday to force a physical showdown where the MPs will have to mark their presence physically. The developments triggered a day of high political drama in the national capital, marked by a furious, expletive-laden press conference by Raut, a reported counter-meeting by the rebel faction with Lok Sabha Speaker Birla, and sharp condemnation from the Congress. The internal fracture was visible at Sanjay Raut's press briefing, where only three other Lok Sabha MPs, Arvind Sawant, Anil Desai, and Rajabhau Waje, stood by him. The remaining six lawmakers were conspicuously absent; their exact whereabouts are unknown. The Sena (UBT) has nine MPs in the Lok Sabha, and at least two‑thirds of them would be required to form a separate group. Apart from Desai, Waje and Sawant, the other six MPs are Sanjay Patil, Sanjay Deshmukh, Omprakash Raje Nimbalkar, Bhausaheb Wakchaure, Nagesh Patil-Ashtikar and Sanjay Jadhav Not Reachable The six MPs stopped responding or became unavailable since Wednesday forenoon, after which the party stopped contacting them. They said when the party contacted Mumbai North East MP, Sanjay Dina Patil, he told party leaders that he was not with the rebel group. The party had asked them to submit a letter to the Lok Sabha Speaker, which he has not submitted so far. Later in the day, sources claimed that the group of six rebel lawmakers had privately met the Lok Sabha Speaker to claim a two-thirds majority in the Lower House, the precise threshold required to escape disqualification under the anti-defection law. Simultaneously, Deputy Chief Minister Eknath Shinde, who split the undivided Shiv Sena in 2022, was reportedly camping in Delhi to oversee the operational layout of the defection of MPs. He returned to his home town Thane in Wednesday night. He is reportedly studying all the legal aspects before taking a final call before the party’s foundation day on Friday. Speaker’s Role Following reports of the rebels' move, a loyalist delegation consisting of Raut, Sawant, and Desai rushed to meet Speaker Birla to file a formal representation urging him to reject any unlawful group alignment. Desai argued that the legal provisions are strictly on the side of the original organisational structure. "Under the law, a splinter group cannot simply merge with another party on its own, even if they have two-thirds support. Only the original administrative party holds that right," Desai told reporters, adding that the Speaker assured them he would thoroughly examine every legal aspect before rendering a decision. The widening panic inside the party also triggered a public, familial disconnect involving missing Hingoli MP Nagesh Patil-Ashtikar. While the MP remained unreachable, his son, Krushna Patil Ashtikar, the MVA's official candidate for Thursday's Maharashtra Legislative Council elections, released a video statement strongly defending Uddhav Thackeray. "I am a Shiv Sainik of Uddhav Thackeray. There is no room for doubt when it comes to me," the younger Ashtikar stated.

Designing for AI Without Chasing It

Over the last three weeks, we’ve tried to take the noise out of the AI conversation.

Week 1: AI isn’t a cure. It’s a diagnostic.

Week 2: AI breaks first where work is unclear.

Week 3: AI only creates leverage when the right conditions exist.


Now comes the real question:

How do you design for AI without turning your business into a lab?

Here’s a simpler way to think about it.


Stop thinking of AI as a tool. Think of it as a new hire.


When you hire a smart person, you don’t throw them into the business and hope they “figure it out”.


You give them:

  • a role

  • boundaries

  • access

  • supervision

  • rhythm


Most SMEs are doing the opposite with AI. They buy a tool, share logins, and feel surprised when:

  • responses sound polished but don’t match reality

  • customers get updates operations can’t fulfil

  • teams quietly bypass the system to protect themselves


That’s not AI failing. That’s poor onboarding. AI doesn’t need motivation. But it still needs a seat in your operating system.

The Mistake

The pattern we’re seeing is predictable. A leader introduces AI for relief. The team uses it for drafts and summaries. Then someone lets it touch real commitments … pricing, timelines, approvals. And stress follows. Not because teams fear AI. Because they fear being blamed for AI’s output.


When process clarity, input ownership, and decision rights are fuzzy, AI feels unsafe. So people hedge. Double-check. Keep the old system alive in parallel. So, the real question isn’t “How do we adopt AI?”


It’s: How do we create a structured place where AI can help without creating chaos?


The sequence

If you remember one line from this series, let it be this:

Capability → Automation → Intelligence.

Not as a lecture. As protection.

You don’t want AI to become a second operating system running on guesses.

Here’s what good sequencing looks like.


Step 1: Build one “AI lane”

Don’t launch AI everywhere. Pick one lane of work where:

  • the process is repeatable

  • errors are visible

  • ownership is clear

For example:

  • enquiry → quote → order confirmation

  • vendor purchase → invoice approval

  • support ticket → resolution

Choose one.

This isn’t about “starting small”. It’s about learning safely.

 

Step 2: Give AI a job description

A simple rule works:

AI can draft. Humans decide.

AI can:

  • draft replies

  • summarise calls

  • create first versions

AI should not:

  • commit delivery dates

  • approve payments

  • override pricing

The moment AI starts “deciding” in a system where decision rights are unclear, confusion follows. When boundaries are explicit, resistance drops. People feel protected.


Step 3: Define only the data that truly matters

Data discipline doesn’t mean cleaning everything. It means defining what must be correct for that one lane. If you’re using AI in order fulfilment, then ensure:

  • one customer master

  • one SKU naming rule

  • one pricing logic

  • one rule for promised dates

That’s it. You don’t need perfect data. You need owned critical data. Without it, AI becomes a confident guesser.


Step 4: Install a review rhythm

This is what separates experimentation from leverage. If you introduce AI and never review its use, two things happen:

  • small mistakes compound

  • trust erodes quietly

Instead, create a simple rhythm:

Once a week, review 5–10 AI-assisted cases.

Where did it help?

Where did it mislead?

What input was missing?

Adjust the process. When this rhythm exists, AI improves with the business instead of drifting away from it.


What to Fix

You don’t need a grand AI roadmap. Set one clear objective: Make one lane of your business legible.

Legible means:

  • the work has a defined shape

  • inputs have an owner

  • decisions have boundaries

  • reviews happen on time

Once work is legible, AI becomes useful naturally. Not because you chased it. Because it finally has something stable to sit on.


A Calm Close

Chasing AI creates short bursts of excitement and long-term fatigue. Designing for AI creates quiet confidence. The difference isn’t technology. It’s sequence. So instead of asking, “Which AI tool should we adopt next?” ask: Where in our business are we ready to multiply clarity? Because AI will multiply whatever you give it. Make sure it’s something worth multiplying.


(The writer is the CEO of PPS Consulting and quite passionate about helping SMEs make the right decisions and not costly ones. She can be reached at rashmi@ppsconsulting.biz)

 

Comments


bottom of page