Leadership Without Certainty | Manish Khadiya

In Leadership Without Certainty, Manish Khadiya and host Bob Hansen make the case that technology leadership is not about projecting perfect knowledge. It is about accepting responsibility, creating enough clarity for people to act and being willing to learn when an assumption proves wrong. The conversation stays grounded in practical situations that sharpened Khadiya’s approach to leading people and technology work at major organizations, including DIRECTV.

One early story centers on an ERP implementation at GE Plastics in Hong Kong. Khadiya was the technical lead and was learning the relevant module as the work moved forward. Shortly before go-live, the team discovered that a meaningful part of the process design was flawed because assumptions had been made without fully understanding the business requirements. The consequences could have extended to product shipments. The recovery required long hours, a quick pivot and collaboration with business partners who found workarounds while the technology issues were fixed. The value of the anecdote is not a heroic recovery narrative so much as its warning: diligence cannot be an IT-only exercise. Requirements have to be tested against how the business actually operates, and relationships with business partners become indispensable when a project goes off course.

Khadiya’s account of his first formal leadership role carries the same theme of revising an initially incomplete view of the job. Promoted to manage people who had just been his peers, he initially behaved as though the leader needed to be the person with the answers. A more experienced colleague challenged that instinct and pushed him to bring the team with him rather than dictate to it. Khadiya describes recognizing the mistake, having a candid conversation with the team and changing how he led. The lesson is deliberately unglamorous: a leader does not succeed separately from the team. Listening, admitting an error and making space for others’ expertise are operational leadership skills, not merely interpersonal niceties.

From there, the discussion broadens into advice for people building technology careers. Khadiya emphasizes understanding the business—particularly its financial logic—rather than treating technical execution as an end in itself. Leaders have to connect decisions to the outcomes the organization values. He favors consistent delivery and expectation management: promise responsibly, then deliver. When a delivery is at risk, the better course is to tell managers and stakeholders early. Early disclosure lets them become partners in a solution; concealment changes the relationship and magnifies the surprise.

Uncertainty, in this view, does not excuse indecision. Khadiya argues that leaders must offer direction even when the problem statement is incomplete. Past experience can help establish an initial course, but it should not harden into stubbornness. The useful posture is to make a reasoned move, learn and reverse or adapt if needed. That balance runs through his career advice as well. He advises listeners to prioritize opportunities for impact over titles and to build the resilience to recover from mistakes, because a career is a long-duration effort rather than a single verdict on any project. He also questions simplistic calls to follow one’s passion, suggesting instead that people identify what they do well, develop it and seek an eventual intersection with their interests.

The AI discussion brings this operating philosophy into the present. Khadiya presents AI strategy as unusually fluid, with tools and vendor positions changing rapidly. Rather than betting the organization on a single provider, he favors flexibility. At the same time, he treats security and protection of corporate data as non-negotiable. He describes DIRECTV as giving employees access to tools such as ChatGPT, Copilot and Claude so they can experiment and build familiarity, while also pursuing agentic applications. Examples discussed include virtual agents in call-center work and AI support across the software-development lifecycle, from requirements through code delivery and testing.

The conversation does not portray adoption as frictionless. Khadiya identifies governance as a continuing challenge, with policy-driven, manual controls that need to become more automated and scalable. He expects AI to automate some tasks and reshape work, but frames the near-term opportunity around moving people toward higher-value activity. The practical closing message is consistent with the rest of the episode: learn the technology, but do not confuse enthusiasm with strategy. Durable leadership still depends on accountability, collaboration, business judgment, resilience and a willingness to confront uncertainty without hiding from it.