Home / Courses / DB-FPX8730
Capella University — DBA FlexPath

DB-FPX8730: Managing Innovation, Design, and Creativity

A complete guide to Capella's DB-FPX8730, the FlexPath version of Managing Innovation, Design, and Creativity, covering how organizations build systematic, repeatable innovation capability rather than relying on occasional inspiration.

DoctoralFlexPathInnovation ManagementAPA 7th Edition

DB-FPX8730 treats innovation as a manageable organizational process, not a mysterious creative spark — covering the research on how organizations systematically generate, evaluate, and develop innovative ideas at scale.

Innovation as a systematic organizational process

DB-FPX8730 covers innovation process frameworks — from idea generation through evaluation and development — and organizational structures (dedicated innovation labs, ambidextrous structures balancing exploration and exploitation) that support systematic, repeatable innovation rather than relying on occasional individual inspiration.

Design thinking and fostering organizational creativity

The course covers design thinking methodology as a structured approach to innovation grounded in genuine user needs, and organizational factors (psychological safety, diverse teams, appropriate resource slack) that research links to higher creative output.

Key topics in DB-FPX8730

Working on your DB-FPX8730 competency assessments?

Our doctoral business experts build DB-FPX8730-level FlexPath assessments with genuine innovation management rigor.

Get Expert Help

Worked example: organizational ambidexterity in practice

  • Exploitation activities: Refining and efficiently scaling the company's existing, proven core product line
  • Exploration activities: A separate, protected innovation unit experimenting with genuinely new, uncertain product directions
  • Ambidexterity challenge: The same organization must excel at both simultaneously, even though they require different metrics, timelines, and tolerance for failure
  • Structural solution: Structurally separating exploration teams (protected from short-term efficiency pressure) while maintaining strategic integration with the core exploitation business
  • Lesson: Organizations that only exploit existing strengths eventually stagnate; organizations that only explore new directions often fail to build a sustainable core business

Get Help With DB-FPX8730

FlexPath innovation management competency assessments.

Place Your OrderView All Services

Related courses

Frequently asked questions

What is organizational ambidexterity, and why is it genuinely difficult for organizations to achieve?

Organizational ambidexterity refers to a company's ability to simultaneously excel at exploitation (efficiently refining and scaling existing, proven products and processes) and exploration (experimenting with genuinely new, uncertain innovations that may not pay off), and it's difficult to achieve because these two activities generally require different metrics, timelines, organizational cultures, and tolerance for failure — a culture optimized for efficient exploitation (rewarding predictability and short-term results) tends to actively suppress the kind of risk-taking and tolerance for failure that genuine exploration requires. DB-FPX8730 teaches that many organizations resolve this tension structurally, creating protected, separately-managed exploration units insulated from the short-term efficiency pressures of the core exploitation business, while maintaining enough strategic connection that successful explorations can eventually be integrated back into or scaled alongside the core business.

Why does design thinking emphasize starting with genuine user needs rather than starting with a proposed solution or technology?

Design thinking methodology begins with deep empathy and understanding of genuine user needs and pain points, only moving to solution generation and prototyping after that understanding is well established, specifically because starting with a proposed solution or an exciting new technology risks developing something that's technically impressive but doesn't actually solve a genuine problem people have. DB-FPX8730 teaches this user-need-first sequencing because a significant amount of innovation failure stems from organizations falling in love with a solution or technology before genuinely validating that it addresses a real, significant user need — design thinking's structured emphasis on empathy and problem definition before solution generation is specifically designed to reduce this common and costly innovation failure pattern.