Project Scaffolding for Cognitive Compensation

Workbook-grounded and author-clarified; proposed reconstruction. Academic projects require initiation, sequencing, time estimation, task switching and recovery after interruption. These demands affect people managing busy lives and many concurrent projects and can create additional executive-function barriers for people with ADHD or other forms of neurodivergence, even when they understand the substantive work.

Proposed and author-clarified. Conventional project plans often record outcomes and deadlines without preserving the working state needed to resume after interruption. A returning person must reconstruct purpose, decisions, file locations, unresolved questions and the next action. When these invisible coordination demands are not externalised, re-entry becomes costly and a viable project may be delayed or abandoned.

Proposed and author-clarified. Build a personal external scaffold that preserves the project’s working state and converts future work into visible, discrete and resumable actions. Provide a clear point of entry, link notes to the actual project files, make dependencies and waiting states visible, and record a concrete next action before stopping. Adjust the scaffold when it creates friction. Treat it as practical support rather than diagnosis or treatment, and preserve the person’s authority over goals, pacing, prompts, sharing and disclosure.

• A visible project structure with small actions, dependencies, milestones and re-entry cues.
• Reduced friction in beginning, resuming and switching between tasks.
• A reviewable record of which supports help under which conditions.
• A person-controlled system that adapts without making medical claims or enabling performance surveillance.

The person defines goals, chooses supports, controls the scaffold and decides what is shared. Collaborators may supply project information, and accessibility professionals may advise when invited, but supervisors and project leads do not configure or monitor the personal system as a condition of participation. The system decomposes, reminds and visualises, but does not diagnose, monitor compliance or decide what the person should be able to do.

Reconstructed risks

• The pattern is misrepresented as treatment for ADHD or another condition.
• Automated reminders become coercive, infantilising or excessive.
• The scaffold over-fragments meaningful work and increases administrative load.
• Sensitive support information is exposed to supervisors, peers or unsuitable services.
• Failure to follow the generated plan is attributed to the person rather than to a poor scaffold or unrealistic workload.

• Minimum viable implementation: follow the documented four-stage procedure manually and retain a visible project structure with small actions, dependencies, milestones and re-entry cues, together with review decisions.
• Robust implementation: add structured templates, version history, provenance, access controls, exception handling and explicit quality gates suited to project scaffolding for cognitive compensation.
• Low-code implementation: connect approved services only where inputs and outputs remain inspectable, with a human approval gate before consequential use or publication.
• Local or privacy-preserving implementation: keep sensitive or unpublished artefacts in controlled storage and prefer local processing where policy, risk or participant expectations warrant it.
• Speculative implementation: explore additional automation only within constrained permissions, with logging, stop conditions, rollback and retained human authority.