Insights
Why Organizations Need Asking Infrastructure
Most organizations have elaborate systems for telling people what to do. Almost none have systems for asking people what they see.
Think about the average week inside any organization. How many communications are instructions, updates, status requests, approvals, directives? Now count how many are genuine questions — not rhetorical, not leading, not performance-related — but questions designed to discover something the organization doesn’t already know.
The ratio is revealing. And the cost is enormous. A global study of more than 1,500 employees found that four in five have ideas for improving their company. A third feel those ideas are ignored. Over half believe good ideas fail at their organization.
Perhaps most striking: research from Tel Aviv University published in the Academy of Management Perspectives found that 27 percent of employees in commercial organizations have deliberately withheld at least one invention from their employer — often intending to use it after they leave. More than one in four people have ideas so valuable they’re worth protecting. And they’re protecting them from their own organizations.
This isn’t a motivation problem
Organizations have spent two centuries building information systems that flow in one direction: downward. Strategy cascades. Objectives cascade. Instructions cascade. Even “feedback” typically means telling employees how they performed against criteria they didn’t set. Edgar Schein called this the central failure of organizational culture. Most leaders believe they’re asking, when they’re actually telling in the form of a question. “What’s the status on that project?” isn’t inquiry. It’s surveillance dressed as curiosity.
AI deepens the challenge. Organizations can now generate analyses, summaries, and recommendations at extraordinary speed. But no AI can replicate what a human notices from years of lived experience inside an organization — the patterns between departments, the unspoken tensions, the customer insight that never makes it to a dashboard. That kind of knowledge has to be asked for. It won’t volunteer itself.
Contribution Leadership requires a fundamentally different kind of question:
- Not “What did you accomplish?” but “What did you notice?”
- Not “Did you hit your targets?” but “What would you change if you could?”
- Not “How can we be more efficient?” but “What are we missing?”
- Not “What’s your update?” but “What’s been on your mind — even though it’s not your responsibility?”
These aren’t soft questions. They’re strategic instruments. Each one is designed to access something no dashboard can surface: the unique pattern recognition that lives inside a human being who has been paying attention.
Organizations invest millions in data infrastructure — systems that capture signals from markets, customers, and operations. They invest almost nothing in what I’d call asking infrastructure: the rituals, norms, and structural expectations that capture signals from the people closest to the work.
The result is a strange paradox
Companies build sophisticated systems to understand their customers while systematically ignoring the insight that already exists inside their own walls.
I wonder whether the most important design challenge of the next decade isn’t technological at all. It might be architectural: building organizations where the right questions get asked consistently, where insight travels upward as naturally as instructions travel downward, and where every person’s perspective is treated as an asset worth discovering.
Contribution OS begins with a deceptively simple shift. Stop asking people what they produced. Start asking them what they’ve noticed.
They’ve been waiting for someone to ask.