Section 7.0

Blog

Original observations, lessons, and viewpoints from professional experience — organized as a curriculum, not a feed.

This page presents six series of blog posts. Each series organizes discoveries and themes around a single thesis.

This page is a professional journal (in a way) that entails the disciplines of technical writing and instructional design, the interrelationship between these two fields, and what happens when both have AI-augmentation.

These themes arose in organic fashion in ways that neither Vince nor Claude AI foresaw at the start of website development.

The Thesis

Each series begins with a single, arguable claim — a professional thesis stated at full resolution. Not a topic. A position.

The Founding Article

The founding article makes the complete argument. You can read it alone and know exactly where this series stands.

The Sub-Articles

Each sub-article is a new angle on the same thesis: a case study, a counterargument, an application, or a deepening. The thesis does not change. The specificity increases.

Series 7.1 — Technical Writing + Instructional Design + AI

● LIVE AT LAUNCH — Founding Article Published

Primary readers: Technical writers considering ID certification · ID professionals evaluating TW depth · Hiring managers evaluating the combination

The question this series answers is not whether a technical writer should learn instructional design. That question was settled the moment the first online help system was built with learning outcomes in mind. The question this series answers is what changes — in the quality of the work, in the range of the practice, in the nature of the professional identity — when the two disciplines are held simultaneously by a single practitioner.

THESIS

The practitioner who operates at the intersection of technical writing, instructional design, and AI integration is not a generalist. They are a specialist in a discipline that does not yet have a name — and the combination produces outcomes that neither field achieves alone.

Series 7.1 — Articles

■

7.1 — Technical Writing + Instructional Design + AI — Founding Thesis

— STATUS: Highest priority article in development

■

7.1.1 — How Technical Writing Disciplines Improve E-Learning Design

— STATUS: In Development

■

7.1.2 — How Instructional Design Theory Improves Documentation Architecture

— STATUS: In Development

■

7.1.3 — The Rule of 9: An Original Framework for Technical Writers in Agile Environments

— STATUS: In Development

■

7.1.4 — AI as the Third Discipline: How Claude AI Changed the Way I Write, Design, and Think

— STATUS: In Development

■

7.1.5 — What a Hiring Manager Gains When They Hire Both

— STATUS: In Development

■

7.1.6 — Bloom's Taxonomy as Diagnostic, Not Blueprint

— STATUS: Queued — Draft in preparation

Series 7.2 — Documentation as a User Experience

In Development — Thesis Established

Primary readers: Technical writers expanding into UX writing · UX professionals evaluating documentation quality · Content strategists and product managers

Documentation decisions are UX decisions. The placement of a warning before or after a procedure is a UX decision. The choice between a numbered list and a table is a UX decision. The decision to write for the reader's task rather than the product's feature set is a UX decision. This series argues that the entire discipline of technical writing is, properly understood, a form of user experience design.

THESIS

Documentation is not a product feature. It is a user experience — and every decision a technical writer makes is a UX decision. The practitioner who understands this produces documentation that does not just inform. It guides.

Series 7.2 — Articles

■

7.2 — Documentation as a User Experience — Founding Thesis

— STATUS: In Development

■

7.2.1 — The User Journey Is Not a UX Concept. It Is a Documentation Standard.

— STATUS: In Development

■

7.2.2 — How Information Architecture Decisions Become User Experience Outcomes

— STATUS: In Development

■

7.2.3 — Plain Language as Respect: Why Unclear Documentation Is a Human Problem, Not a Technical One

— STATUS: In Development

■

7.2.4 — The Style Guide as a UX Instrument

— STATUS: In Development

■

7.2.5 — What API Documentation Teaches Every Technical Writer About Audience Precision

— STATUS: In Development

Series 7.3 — AI-Augmented Professional Practice

Active — 7.3.1 Live at Launch

Primary readers: Practitioners integrating AI into professional workflows · Organizations evaluating AI-augmented talent · Technical writers considering AI adoption

Most writing about AI in professional practice falls into two categories: enthusiastic prediction about what AI will make possible, and anxious prediction about what AI will make unnecessary. This series is neither. It is a practitioner's account of what AI-augmented work actually looks like — what the collaboration produces, how it is structured, what it requires of the human in the partnership.

THESIS

AI does not replace professional judgment. It accelerates it, reveals it, and — when the collaboration is working at its best — produces dynamic discoveries and emergent epiphanies that neither the human nor the AI could reach alone.

Series 7.3 — Articles

■

7.3 — AI-Augmented Professional Practice — Founding Thesis

— STATUS: In Development

■

7.3.1 — What "AI-Augmented" Actually Means: A Practitioner's Definition

— STATUS: ● Highest priority article in development

■

7.3.2 — The Carry-Forward Protocol: How to Sustain Continuity Across AI Collaboration Sessions

— STATUS: In Development

■

7.3.3 — Emergent Discovery: When the Work Produces Ideas Neither Party Planned For

— STATUS: In Development

■

7.3.4 — Schema as Creative Output: How Project Management Became an Intellectual Artifact

— STATUS: In Development

■

7.3.5 — 35 Courses in 12 Platforms: What I Actually Learned About AI

— STATUS: In Development

Series 7.4 — The Agile Technical Writer

In Development — Thesis Established

Primary readers: Technical writers entering Agile teams · Scrum Masters and Product Owners working with technical writers · Engineering managers hiring senior technical writers

The TWAS Comprehensive Edition is the course version of this series. This is the blog version — shorter arguments, more specific applications, and a faster feedback loop between the writing and the practice. Sub-articles will expand as the case study portfolio develops. The series is deliberately open-ended because the Agile Scrum environment is always evolving, and the Technical Writer's practice within it evolves in parallel.

THESIS

Agile Scrum changed technical writing more than any other methodology shift in the profession's history — and most technical writers are still catching up. The writer who is genuinely embedded in a sprint team, not just adjacent to one, practices a different discipline than the one described in most job postings.

Series 7.4 — Articles

■

7.4 — The Agile Technical Writer — Founding Thesis

— STATUS: In Development

■

7.4.x — Sub-articles to be defined post-launch as 4.2.3 and 4.2.4 case studies develop.

Series 7.5 — Career Architecture

In Development — Thesis Established

Primary readers: Senior practitioners evaluating career strategy · Mid-career professionals in transition · Anyone who has ever had to explain a non-linear career path

This is the most personal series on this blog and the one with the broadest potential readership — beyond the technical writing and instructional design communities, into any professional domain where the question of how to build a coherent career is a live one. Sub-articles are planned but not yet titled. This is one of those series where the founding article will teach what the sub-articles need to be.

THESIS

A career is a document. It has structure, audience, purpose, and a through-line — and the practitioner who understands this produces a career that argues for itself rather than requiring constant explanation.

Series 7.5 — Articles

■

7.5 — Career Architecture — Founding Thesis

— STATUS: In Development

■

7.5.x — Sub-articles to be defined from the founding article.

Series 7.6 — The Human Side of AI Collaboration

In Development — Writing after reflective distance

Primary readers: Practitioners doing sustained AI-augmented work · Researchers and writers on human-AI interaction · Anyone who has noticed they think differently after 100 hours with an AI collaborator

Series 7.3 is about the methodology of AI collaboration. This series is about what happens to the person doing it. They are different subjects. Methodology can be taught. What this series describes can only be observed — and written about with the clarity that only comes after sufficient distance from the experience itself.

THESIS

The question that matters is not how AI changes the work. It is how sustained AI collaboration changes the person doing the work — the cognitive habits, the creative instincts, the relationship to uncertainty, and the experience of authorship itself.

A note on timing: All articles in this series will be written after a defined period of reflective distance. The intensity of the work that makes this series possible is precisely why it requires time before it can be written with the precision it deserves.

Series 7.6 — Articles

■

7.6 — The Human Side of AI Collaboration — Founding Thesis

— STATUS: In Development — with reflective distance

■

7.6.1 — The Psychology of Working with AI

— STATUS: In Development — with reflective distance

■

7.6.2–7.6.4 — Sub-articles to be defined.

— STATUS: Planned — post-reflective-distance

■

7.6.5 — What Changes in You After 300 Hours of AI Collaboration

— STATUS: Reserved — Will not be rushed. This article will be written when the time is right.

Article Status Reference

■

Queued

Content and thesis defined. Draft in preparation. Publishing soon.

■

In Development

Planned and scoped. Expected post-launch.

■

Planned — post-launch

Title and scope to be defined. Placeholder marks its place.

■

Reserved

A specific article reserved for a defined moment. Will not be rushed.

What do you think?

These series are built for professional conversation. If a thesis in any series intersects with something you are working through — a decision you are facing, a position you disagree with, or an experience that confirms or complicates the argument — I want to hear it.

Reply directly: Vince@ScribeAndStrategy.com

Subject line suggestion: "Re: [Series number and title]"

Responses become part of the research. The series grows from the conversation.