Innovation 100: Question the Given

Inquiry

Question the Given

Teams slow down when they accept inherited assumptions as fixed truths. Processes, requirements, and workflows accumulate quietly over time, and people stop asking whether they still make sense. That’s when innovation stalls. Cross-functional partners absorb unnecessary friction, and customers feel delays driven by outdated thinking. “Question the Given” helps leaders and teams break that inertia. It encourages them to treat constraints as hypotheses, not rules etched in stone. When leaders create permission to challenge what’s assumed, they unlock faster problem-solving and cleaner execution.

Imperative Explained

Question the Given means refusing to let legacy thinking dictate today’s decisions. Leaders examine requirements, processes, and norms with a fresh lens. They separate what is truly essential from what simply “came with the job.”
When this practice takes root, teams stop waiting for permission. They redesign workflows, remove redundant steps, and surface opportunities that mature organizations often overlook. Innovation becomes a natural byproduct of curiosity and rigor—not a separate initiative.

Five Behaviors

  • Challenge inherited rules — Ask why they exist.

  • Probe constraints — Test whether they’re real or assumed.

  • Spot outdated logic — Identify what no longer fits.

  • Frame better questions — Focus on what’s possible.

  • Invite alternatives — Encourage multiple paths forward.

If You Don’t

The organization becomes rigid. Teams treat questionable constraints as immovable, slowing improvement. Rework grows, and customers experience stagnation masked as stability.

If You Do

Teams gain ownership and momentum. Accountability rises, deadlines become more reliable, and leaders spend less time chasing or correcting. Innovation strengthens because people stop deferring tough questions.

Mini-Case

A junior leader inherited a requirement that slowed every project. She questioned it, learned it was based on an outdated dependency, and removed it. The team’s cycle time shortened and accountability increased across the group.

Try It This Week

  1. Identify one assumed constraint.

  2. Ask why it exists.

  3. Test whether it’s still valid.

  4. Explore one alternative.

  5. Share what you learned.

Learn More

Explore Decision Making 100: Name the Tradeoffs for sharper framing, Learning 100: Follow Your Confusion to surface blind spots, and Strategy 200: Look to Subtract to remove outdated work.