Why Text Workbench Is the First Step in the Writing Flow

1. Hypothesis

The hypothesis was that having a central, unopinionated starting point for text manipulation reduces the cognitive load of switching between formatting tools. If writers can dump text into a plain-text environment first, they are more likely to use subsequent refinement tools deliberately.

2. What I built

Text Workbench — a simple, local-first editor that strips rich-text formatting and provides real-time character and word counts. I positioned it as the entry point for writing workflows, rather than another standalone utility.

3. Example Input/Output & UI Decisions

Input: A messy Google Doc draft filled with bolding, inconsistent font sizes, and hidden HTML spans.

The UI Decision: Instead of adding rich-text features, I deliberately restricted the Workbench to plain text only. The core action is a single "Clear Formatting" paste, followed by a raw read-out of text metrics.

Output: Clean, raw text ready to be fed into the Readability Checker or Tone Switcher.

4. What I observed

No session or interaction tracking was in place when this note was written. The following are design assumptions and inferences, not measured outcomes:

• Assumption: The primary use pattern is paste, strip, copy — the tool is used as a staging area, not a primary editor. This is what the interface was designed for, but it has not been confirmed by usage data.
• Observation: No requests for bolding or list formatting appeared in the feedback received. The plain-text constraint was not actively pushed back against.
• Interpretation: The tool appears to serve its intended role as a formatting reset before moving text to other tools. The interpretation is based on absence of contrary feedback, not direct measurement.

GA4 tracking of tool interactions is now in place from 2026-05-27. How visitors actually use Text Workbench will be visible after a measurement period.

5. What changed

No handoff buttons were added — Text Workbench remains a standalone formatting tool. The documented workflow for passing text between tools is in the Edit a Draft workflow.

6. Status

kept

FAQ

Does Text Workbench send pasted text to a server?

No. All formatting cleanup and text metrics run locally in your browser. Nothing you paste is ever sent to a server.

Does it work with text pasted from Google Docs?

Yes. The primary use case is stripping the hidden HTML spans, inconsistent font sizes, and bolding that appear when pasting from Google Docs or other rich-text editors.

How is Text Workbench different from the Readability Checker?

Text Workbench normalizes formatting and gives raw character and word counts — it does not score the text. The Readability Checker measures sentence density and Flesch ease. The two tools work in sequence: clean the formatting first, then check the clarity.