Skip to main content

GenaI as co-author and more importantly as "Devil's Advocate"

In a companion post on context stacking, I came across an idea that stayed with me — and I wanted to explore it further.

This piece isn’t just about the final blog produced, but about the process behind creating it using generative AI (specifically, Claude.ai). Rather than using AI as a writing shortcut, I used it as a thinking partner — one that could challenge my assumptions, test my reasoning, and help strengthen the argument before anything was finalised.

What emerged was a structured workflow (shown below) that others can adopt when using AI to improve the rigour, not just their output. And it all starts with setting the context and the audience and telling the generative AI to pick it apart.


The process:

Before using Generative AI: Two drafts were produced, and the second draft went through this final process, as described by claude.ai here.

Here's the workflow we followed:

1. Critical Reading and Initial Diagnosis

We started with a close reading of your original draft, analysing what was working well structurally and argumentatively, and identifying the key weaknesses an academic reviewer would likely challenge — particularly the flipped classroom compliance problem you raised directly.

2. Devil's Advocate Questioning — Round One

Rather than moving straight to revision, we used structured devil's advocate questioning across four pressure points: the transferability of the central claim, the wrong mental model problem, academic displacement, and the equity argument. Each question was designed to find where the argument was exposed rather than where it was strong.

3. Iterative Stress-Testing — Multiple Rounds

Crucially, we didn't accept your first answers. Each response you gave was pushed harder in the next round — your answers generated new, more specific questions. This produced several iterations where the argument either strengthened genuinely or revealed honest limitations. Notably, when you challenged my assertion about academic workload lacking evidential basis, that exchange itself modelled the critical thinking the piece advocates.

4. Position Clarification on Key Tensions

Through this process several important clarifications emerged that weren't in the original draft: the champion fragility problem, the coordinated misconception risk, lived experience as embodied presence rather than purely knowledge, and most significantly the honest narrowing of your target audience from "all academics" to "student-centred module leaders with genuine autonomy."

5. Honest Scoping Decision

The pivotal moment was agreeing that the piece was most honestly a proof of concept argument for early adopters rather than a universal prescription — and recognising that this resolved the central contradiction between your equity argument and your actual audience.

6. Structural Redesign Before Drafting

Before writing a single word of the revised piece, we agreed a revised section architecture that mapped the new argument logic — ensuring the structure served the argument rather than retrofitting the argument into the original structure.

7. Drafting with Referenced Integration

Only then did we draft, integrating Biggs and Tang and Freeman et al. as gaps the conversation had specifically identified, and producing a piece that honestly names its scope in the subtitle rather than burying the limitation.


The meta-point worth noting

This workflow is essentially the context stacking methodology your piece advocates — applied to academic writing rather than lecture preparation. We built a model, stress-tested it against challenging questions, identified where it broke down, refined it, and only then committed it to final form. The process mirrored the argument


The bigger takeaway

This process highlights a more powerful way to use generative AI. Instead of treating it as a tool for faster writing, it can be used to improve how we think. By asking it to question, challenge, and probe our ideas, we can produce work that is more robust, more honest, and ultimately more useful. On a more personal note, it pushed me hard to think what I was actually thinking and meaning - it didn't give me the answers.

The inverted questioning and lots of multiple rounds were the key strengths of the approach at each stage/round. I was asked some insightful but critical questions. I did want it to give me the answers but push me to address (and face) critical questions.


All opinions in this blog are the Author's and should not in any way be seen as reflecting the views of any organisation the Author has any association with. Twitter @scottturneruon

Comments

Popular posts from this blog

GenAI Productivity: Ideas to project proposal 1

One of the ways I use Generative AI with students is to take basic ideas for projects, usually a title, and get these tools to greater ideas and start of a project proposal. This is with all the usual caveats  Check the references (if any); It is going to be basic, so extend it. In this example I am going to use Co-pilot but the ChatGPT, etc can be used, employing a few basic prompt engineering basics: personas (who is the target audience?) and Templates (how do I want it to look?) to start this process. Example:  Project ideas for MSc Data Intelligence students (persona)  on a particular topic. The reply will include subheadings and relevant (hopefully) content for  TITLE, INTRODUCTION, PROBLEM STATEMENT. The prompt: " Taking the topic "Leveraging open-source tools to measure and present academics publications automatically from public domain data.". Give five innovative projects for a Master's level student dissertation in Data Intelligence. Each project example wi...

GenAI Productivity: Ideas to project proposal ideas from Google Scholar

From Google Scholar to Project Ideas or Using AI to Map the Future of Your Research Generated as well by Google Gemini Have you ever looked at a researcher’s Google Scholar profile and felt overwhelmed? Between the long lists of citations and dense technical titles, "connecting the dots" of a decade-long career is a massive cognitive lift. Whether you are a student hunting for a dissertation topic or a professional scouting for a collaborator, understanding the trajectory of research is harder than reading the papers themselves. In my latest experiment, I used Google Gemini to see if it could bridge this gap. I gave it a specific challenge: Analyze my own research profile and design 10 compelling project ideas for a final-year Computer Science student. The Prompt: Turning Data into Direction The secret to a good AI output is giving it a clear "anchor." By providing a URL to a live dataset (my Scholar profile), I bypassed the need to copy-paste thousands of words....

Getting multiple viewpoints with ChatGPT

Well sort of! There are approaches where we can get the generative AI to look at a problem from multiple perspectives (or personas) and bring the ideas generated, ideally informed by the others. to a final plan. One of the main strategy is called Tree of Thoughts (see here for more detail  https://www.forbes.com/sites/lanceeliot/2023/09/08/prompt-engineering-embraces-tree-of-thoughts-as-latest-new-technique-to-solve-generative-ai-toughest-problems/?sh=5ce79bdb2c8b ). The central idea is get a number of expert opinions, allow potential cross-fertilization of ideas, come up with actions or plans. Let see this action.  Scenario: Find out about the UK Government's plans on Disability support and then use Tree of Thoughts to produce some ideas for a company making disability equipment based on their website. Google's Gemini will be used. Stage 1 "UK Governments plans on Disability support ": Prompt:  Read, convert to plain text and consolidate information from the followi...