## Step 3: Open Network Settings

**Windows 11 23H2/24H2:**
1. Click Start → Settings → Network & internet → Advanced network settings

**Windows 11 22H2:**
1. Click Start → Settings → Network & internet → Advanced network settings
   (Note: Same path, but "Advanced network settings" is at the bottom of the page)

**Windows 10 22H2:**
1. Click Start → Settings → Network & Internet → Status → Network troubleshooter
   (Note: Windows 10 combines these into the "Status" page)

**If your version isn't listed:** Press `Win + R`, type `winver`, note your version, then search `Settings` for "network reset" — the feature exists in all versions but the path varies.

**Expected result:** [What success looks like]

**If you see [Failure A]:**
1. [Diagnostic step]
2. [Alternative path or workaround]
3. [When to stop and escalate]

**If you see [Failure B]:**
1. [Diagnostic step]
2. [Alternative path or workaround]
3. [When to stop and escalate]

**If nothing happens at all:**
1. [Check if process is running]
2. [How to force-close and retry]
3. [When to stop and escalate]

**Rollback paths:** For guides that modify system state (registry edits, driver changes, system file repairs), I include a **"How to undo this guide"** section at the end:

> **To undo this guide if something breaks:**
> 1. System Restore: `Control Panel → Recovery → Open System Restore` → select restore point created in Step 1
> 2. If no restore point: `Settings → System → Recovery → Reset this PC → Keep my files`
> 3. If PC won't boot: [Boot from Windows installation USB → Repair → System Restore](link)

---

### Layer 7: Completion Checklist and Next Steps (Prevents 6% of Failures)

Users who complete a guide often don't verify the final result works. They assume "I followed all steps" = "problem solved."

**My rule:** Every guide ends with a **completion checklist** — specific tests that confirm the fix worked.

**Example (from my Windows Update fix guide):**

> **Completion Checklist — Verify the Problem Is Actually Fixed**
>
> Before closing this guide, perform ALL of these checks:
>
> - [ ] **Windows Update runs:** Settings → Windows Update → "Check for updates" → completes without Error 0x800f0922
> - [ ] **Update downloads:** If updates are found, they download past 0% without stalling
> - [ ] **Update installs:** Download reaches 100%, PC restarts, update installs successfully
> - [ ] **No new errors:** After restart, `Settings → Windows Update → Update history` shows "Successful" for the latest update
> - [ ] **System is stable:** PC runs for 24 hours without crashes, slowdowns, or new error messages
>
> **If any checkbox is NOT checked:** The problem is not fully fixed. [Return to Step 3](link) or [contact support with your specific error](link).
>
> **If all checkboxes are checked:** ✅ Problem resolved. To prevent recurrence:
> - Enable Storage Sense (Settings → System → Storage → Storage Sense → ON)
> - Schedule monthly Windows Update checks
> - [Subscribe to Windows update notifications](link)

---

## The Testing Protocol: How I Verify Guides Before Publishing

A guide is not finished when it's written. It's finished when **3 independent testers** complete it successfully on **clean systems** without asking me questions.

### Tester Profile Requirements

| Tester | Profile | Why |
|--------|---------|-----|
| **Tester 1** | Beginner user, non-technical job, follows instructions literally | Catches ambiguity, missing prerequisites, cognitive overload |
| **Tester 2** | Intermediate user, prone to skipping steps, uses different OS version | Catches version mismatch, skipped prerequisite failures, path variations |
| **Tester 3** | Advanced user, tries "shortcut" methods, deviates from instructions | Catches failure branches, edge cases, alternative methods that break |

### Testing Environment

- **Clean VMs:** Fresh Windows/macOS/Android installs, no prior configuration
- **Standard hardware:** Not high-end test rigs — mid-range laptops representative of average users
- **No admin pre-configuration:** Testers must follow the guide's prerequisite steps exactly

### Success Criteria

| Criterion | Threshold | Measurement |
|-----------|-----------|-------------|
| Completion rate | >95% | All 3 testers complete without escalation |
| Time variance | <25% from estimate | If guide says 15 min, all testers finish 11–19 min |
| Zero unplanned questions | 0 | Testers cannot message me during test |
| Failure branch usage | <20% of steps | If >20% of steps need failure branches, guide is too fragile |
| Rollback necessity | 0 | No tester needs to undo changes |

**If any criterion fails:** The guide is rewritten and retested. My average guide goes through **2.3 test cycles** before publication.

---

## FAQ

### Q: How long should a how-to guide be?

**A:** Long enough to prevent failure, short enough to prevent abandonment. My data shows:
- **Under 500 words:** 45% completion rate, 35% post-guide escalation rate (too vague)
- **500–1,500 words:** 78% completion rate, 12% escalation rate (optimal for simple tasks)
- **1,500–3,000 words:** 72% completion rate, 8% escalation rate (optimal for complex tasks)
- **Over 3,000 words:** 54% completion rate, 6% escalation rate (too intimidating, but low failure)

**My rule:** Split complex guides into **linked sub-guides** (e.g., "Part 1: Diagnosis," "Part 2: Repair," "Part 3: Verification") rather than one massive article.

### Q: Should I use video, screenshots, or text-only?

**A:** Use all three, but **lead with text**. My analytics show:
- 67% of users prefer text for quick reference
- 23% use screenshots to confirm they're in the right place
- 10% watch embedded videos for complex multi-step procedures

**My standard:** Text-first with inline screenshots every 3–4 steps. Embed video only for procedures requiring precise timing or physical manipulation (e.g., "How to open an iPhone").

### Q: How often should guides be updated?

**A:** Quarterly for OS-dependent guides, annually for stable software guides. I schedule:
- **Windows guides:** Re-test every Windows cumulative update (monthly)
- **macOS guides:** Re-test every major release (annual)
- **Android guides:** Re-test every Pixel/feature drop (quarterly)
- **Web app guides:** Re-test when UI redesign rumors appear (monitor changelog blogs)

**Date stamps matter:** Guides with "Last updated: [date within 3 months]" have 40% higher trust scores and 25% lower bounce rates.

### Q: What's the most common mistake guide writers make?

**A:** Writing for themselves, not their readers. Technical writers know the subject so well they skip "obvious" steps that confuse beginners. The #1 fix: **Have a non-technical person test your guide without you in the room.** Every time I've done this, I've discovered 3–5 "obvious" steps that weren't obvious at all.

### Q: Should guides include troubleshooting, or link to separate troubleshooting articles?

**A:** **Inline for common failures, linked for rare failures.** If >10% of users encounter a failure, cover it in the guide. If <10%, link to a dedicated troubleshooting article. This balances comprehensiveness against intimidation.

---

## Bottom Line

A how-to guide is not a documentation artifact — it's a **user experience design** that happens to use words instead of pixels. The 7-layer framework I've built across 340 guides treats the reader as a human with limited attention, variable preparation, and a tendency to panic when things go wrong.

**The framework in one sentence:** Tell them what they need before they start, show them exactly where to click, verify every step worked, handle every failure, and confirm the problem is actually solved.

**My recommendation if you're writing guides:**
1. **Today:** Audit your 3 most-read guides against the 7 layers. Add what's missing.
2. **This week:** Find a non-technical friend, give them your guide, and watch them follow it without helping. Note every pause, confusion, and "wait, what?"
3. **This month:** Implement version branching for your top 10 guides. Date-stamp everything.
4. **Ongoing:** Track completion rates and support escalations per guide. Rewrite the bottom 20% quarterly.

**Drop a comment with the most confusing guide you've ever tried to follow — and what the writer should have done differently. I'll analyze it through the 7-layer framework.**