# Whybook: keeping human analysts in charge in the AI era

**URL:** <https://discourse.jupyter.org/t/whybook-keeping-human-analysts-in-charge-in-the-ai-era/38930>\
**Category:** Show and Tell\
**Created:** [October 11, 2026, 10:13am UTC](https://discourse.jupyter.org/t/whybook-keeping-human-analysts-in-charge-in-the-ai-era/38930 "2026-10-11T10:13:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![krassowski](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/krassowski/32/1685_2.png) [@krassowski](https://discourse.jupyter.org/u/krassowski)\
**Post date:** [October 11, 2026, 10:13am UTC](https://discourse.jupyter.org/t/whybook-keeping-human-analysts-in-charge-in-the-ai-era/38930/1 "2026-10-11T10:13:13Z")

</div>

Hey, I am exploring this idea for closing the [understanding gap](https://whybook.dev/#why) for analyses and research given how more and more work gets delegated to AI: [https://whybook.dev/](https://whybook.dev/) - and building on Jupyter strengths.

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/jupyter/original/3X/4/f/4fe1767a705cb20f628b9d00e3e5ff267d7f6b03.png)

The theses are:

- people needs to be the ones asking questions for analysis to be meaningful and insightful for them
- we need to make analysis that does not depend on chat box as primary interface fun in order to encourage analytical journey that results in insight retained by humans and better mental model
- we need to make use of all the visual representation richness that Jupyter UI can offer to close the understanding gap
- both human and AI generated notebooks can easily hide important decisions; we should surface them without overwhelming users; code is secondary to the decisions that it makes
- we should explore where Jupyter fits in if the world continues to move towards handing off more analytical jobs to AI (and avoiding a possible outcome of humans losing control, by steering the analysis towards keeping humans in charge)

The [website](https://whybook.dev/) has the full writeup, please give it a look. It is open source ([GitHub - openteams-ai/whybook: A question-driven view of Jupyter notebooks, as a JupyterLab extension · GitHub](https://github.com/openteams-ai/whybook)) and long-term I would like to upstream quite a few pieces. For now, this also a testing ground for various APIs to make improvements upstream for building blocks in Jupyter.

I would be keen to explore further and see if we can get someone to build it with us but for now it is evenings/weekends-only project. Please share any feedback to let me know if this is worth pursuing further, and drop a message if you are interested in contributing (which could be testing, rolling out for a trial to users, or giving structured feedback).