Experiment 01 / Published as a design exploration
Direct-answer-first guide structure
Does opening a technical guide with a three-sentence direct answer help readers decide faster whether to keep reading?
content structure / technical writing
0Experiment log
Open questions, recorded before the answers.
Each entry states what is being tested and why. Statuses describe where the work actually is — no conversion rates, traffic figures, or customer outcomes are claimed.
Experiment 02 / In synthesis
Comparison-table placement in technical content
Should a comparison table appear before the prose explanation of each option, or after it?
comparison / decision support
1Experiment 03 / Prototype reviewed
Tutorial code sample position
Do readers prefer a complete code sample up front with explanation after, or code introduced incrementally?
code samples / developer education
2Experiment 04 / Awaiting user testing
Decision-tree content format
Is an interactive decision tree more useful than a written decision procedure for choosing a web-data approach?
interactive tools / decision support
3Experiment 05 / In synthesis
Workflow-based versus feature-based navigation
Does organising the site around workflows rather than capabilities help readers find relevant material?
information architecture / navigation
4Experiment 06 / Planned
Source-traceability explanation patterns
Which explanation makes source traceability feel necessary rather than optional: a failure story, a diagram, or a worked example?
provenance / explanation design
5Experiment 07 / Prototype reviewed
RAG readiness self-assessment design
Can a short self-assessment produce a directional readiness judgement people actually trust?
rag / assessment design
6Experiment 08 / Awaiting user testing
Monitoring alert-priority visualization
Does a two-axis matrix communicate monitoring priority better than a scored list?
monitoring / visualization
7Experiment 09 / Published as a design exploration
Structured-data schema-builder interaction
Does letting readers edit a schema in the browser improve their understanding of extraction trade-offs?
structured data / interactive tools
8Experiment 10 / Published as a design exploration
Short-form definitions versus long-form explainers
Do glossary entries need a second paragraph of nuance, or does the one-line definition do the work?
glossary / content structure
9Experiment 11 / In synthesis
Implementation-intent query mapping
Which recurring questions about agent web access are best served by a guide, a tool, or a glossary entry?
content strategy / search intent
10Experiment 12 / Planned
Technical content update signals
What signal tells a reader that technical content is maintained, without inventing history?
trust / maintenance
11Entries document hypotheses and learning intentions, not verified commercial performance.