Which leadership role is taking ownership of generative AI at your org?

Leadership Innovation & Emerging Trends

CIO31%

CDO/CDAO (chief data/analytics officer)21%

CISO12%

CTO14%

CEO6%

Ownership is shared10%

Someone else3%

No one3%

203 PARTICIPANTS

2.3k views3 Comments

Sort by:

Senior Director, Information Technology of Service Deliverya year ago

Shared between our CISO, and CPO (Privacy), under the direction/guidance of the CIO.

Senior Data and Analytics Leader in Governmenta year ago

The leadership role responsible for Gen AI would ideally depend on factors such as the company size, industry, existing technology and data governance structures, and the specific use cases being explored. Effective collaboration and clear lines of accountability across different functions would be crucial for the successful and responsible adoption of Gen AI.

IT Manager in Construction2 years ago

The CAIO (Chief Artificial Intelligence Officer)

Content you might like

If you were designing an “AI leader” role at your organization, which of the following would be non-negotiable responsibilities? Select all that apply

Drive AI innovation 42%

Develop AI strategy 60%

Build AI team 36%

Establish use cases 26%

Track market trends 30%

New vendor discovery 21%

Design AI architecture 25%

Manage AI governance 30%

Improve AI delivery models 11%

Something else (share in comments!) 2%

View Results

How likely do you think it is that a four day work week will become the standard over the next 12 months?

Inevitable4%

Highly likely14%

Somewhat likely16%

Somewhat unlikely18%

Very unlikely41%

Impossible6%

View Results

How do you deal with a mismatch of risk appetites with the board? What are some ways to increase, or temper, the board’s risk appetite if necessary?

How do you think AI will disrupt business across industries? Add to my list: 1. Content creation 2. Photos and video production 3. Basic coding and debugging 4. Strategic analysis to be highly complimented

How does your organization balance using AI to make entry-level jobs more efficient with the need to maintain a robust talent pipeline? Are there specific roles you're purposely shielding from automation to retain pathways for employee development?