NLG Talks

There are a handful of genuine practitioner insights - process-map before digitising, Microsoft Planner as a hidden M365 gem, audience-segmented communication - but they are buried under heavy repetition, filler affirmations, and standard lean platitudes. Insight per minute is low for a 29-minute runtime.

“If you have a waste in your process, you just have it as a digitized. Okay, you still have the waste but you bring it to the your digital uh, work process intelligence.”

“Microsoft Planner is one of the hidden tool within the Microsoft 365 that no one even know what it is today.”

The technology-definition reframe (frameworks and physical tools, not just digital) and the slight sharpening of the AI-replacement cliché show some independent thinking, but the bulk of the episode recycles well-known lean and change-management orthodoxy (Shingo model, Toyota, people-first) without adding a genuinely new angle.

“somebody who know how to integrate technology in the business model, okay. Will even replace the person who know AI.”

“when you define a technology it's any scientific knowledge that has been converted into a solution that help to increase the human capability.”

Hisham is a credible mid-senior practitioner with real oil-and-gas and SME consulting experience, and he draws on lived implementation stories rather than theory alone. However, he is a regional consultant rather than a verifiable C-suite operator who has scaled supply chains at a named enterprise, which caps the ceiling.

“I'm having more than 20 years uh, in setup and building manufacturing and supply chain systems across uh, several organizations.”

“this gap I have discovered with one of my customer. Everything he explained to me Microsoft Access is all what he needs.”

A few concrete anchors stand out - the NUMMI factory case, the Microsoft Access recommendation for a five-user client, and the CPOC/SIPOC mapping practice - but dollar figures, timelines, and attributed outcomes are absent. The Gartner '70% of projects fail' stat is invoked without date, report, or context.

“according to Gartner, the 70% of the project it's fail.”

“There is a, uh, real case called Numi New Me happened in the U.S. correct. Ford, when they are a uh, single motor. Sorry. They give one factory that is losing money to Toyota.”

The host softballs almost every question, routinely echoes the guest's answer back as his own observation, and never challenges a single claim. The session also reveals a basic preparation lapse - the host introduces himself as Jason but the guest calls him Justin throughout, suggesting minimal rapport-building and no real pushback dynamic.

“I have used Microsoft Planner. I feel that it's. It's a alternative slack.”

“Absolutely. So people uh. Is the framework I would say is the base for development.”