Provide technical documentation

Define 'technical documentation' for a network-support team in a way that cleanly separates it from 'training materials' and 'inline code comments.' Use the Audience-Task-Context framework in your definition and give three specific examples of artifacts that belong in docs vs training vs comments for a Cisco router replacement project our team will do next month.

Map 'providing technical documentation' for network support onto a 1–5 mastery spectrum. For each level give 3 observable behaviors, one measurable artifact example, and one quick test a team lead could run in 10 minutes to detect that level on our Confluence repo.

Explain, from first principles, why a Minimal, Reproducible Example (MRE) makes troubleshooting docs more effective for network support. Tie the explanation to cognitive load theory or similar psychological mechanisms and give one short experimental test I could run in our team to validate the claim (50–90 words).

Describe an anti-pattern for a network-support specialist who believes they 'write good docs' but actually cause costly outages. Use the SBI adapted for docs (Situation-Behavior-Impact) to structure one extended example about VLAN change procedures and list five tangible tells that reveal this anti-pattern on our Confluence page.

Roleplay an urgent on-call exchange: I'm the on-shift network-support specialist handling a partial outage after a config push. You play the senior engineer (difficult, pragmatic). I will paste my proposed runbook steps. Using the Minimal, Reproducible Example (MRE) idea and the Single Source of Truth principle, push back where my steps are risky, ask for missing pre-checks, and demand a specific rollback command if needed — don't be polite: call out anything that would make you refuse to run it.

Walk me through an autopsy of a real-feeling project where lack of maintainable docs caused a weeks-long network rollout failure. Use SBI adapted for docs to map the timeline, identify the earliest traceable sign, and point to the single doc change that would have prevented escalation. Be specific: name the artifact (e.g., 'edge-firewall cutover checklist'), the missing line, and the immediate consequences.

I maintain network docs for a mid-size enterprise on-prem stack. Roleplay three short memos (startup, global enterprise, remote-async team) explaining how I'd change the 'router failover troubleshooting' doc. Use Audience-Task-Context and SBI adapted for docs explicitly; for each memo list exactly which sections you'd add/remove and why (focus on SLAs, tooling, and expected reader interruption levels).

I just wrote this Slack reply to a junior tech, defending a terse runbook: "It's in the repo. Read the README and the script comments. If it breaks, revert." Rewrite that message to demonstrate strong Audience-Task-Context framing and use the SBI adapted for docs to make the expectations and next steps explicit. Keep it a Slack message (50–80 words).

At my company US ops writes runbooks as stepwise CLI commands; our Tokyo NOC prefers annotated screenshots and flows. How can we reconcile these styles so Japanese shift engineers and US field techs both succeed? Use Audience-Task-Context and Single Source of Truth / Source Control for Docs to propose an explicit doc structure and a concrete workflow for edits across cultures (70–90 words).

Look at the 2018 major outage where a misapplied config rollback caused regional network split (summarized: engineer followed an outdated, fragmented doc and performed an unsafe revert). Argue specifically how applying Single Source of Truth / Source Control for Docs plus an SBI-style troubleshooting template would likely have prevented that rollback. Be concrete about what lines in the doc would change and what the emergency workflow would have been (80–110 words).

Last Thursday I handed on-call notes to a junior tech who then escalated a routine switch reboot as a 'network outage' to the manager. Using the Audience-Task-Context framework and SBI adapted for docs, coach me on how my written handoff should have shaped their response — show the exact phrases I should have written and a 2-sentence postmortem I could send the manager.

I document routine router configs. Show me examples (junior, senior, manager) of an 'interface config' doc for a VLAN trunk using Audience-Task-Context and an MRE. Highlight the differences in scope, assumptions, and maintenance notes.

Simulate a 6-turn disagreement between a network engineer who insists docs must prioritize 'complete runbook steps' and a docs advocate who insists on 'audience-focused MREs and living docs' (use Audience-Task-Context and Single Source of Truth). Make each side realistic, name the one tacit sign they'd notice in each other's work, and end with your adjudication and one action item I should push for.

I'm a network support specialist deciding whether to expand our troubleshooting docs from a single-page runbook to an exhaustive 40-page playbook. Use the Audience-Task-Context framework explicitly. Give me a conversation: argue for 'keep it minimal' and then for 'make it exhaustive' as opposing team leads (3-4 points each with trade-offs tied to on-call time, onboarding speed, and drift). Then tell me which side I'd likely need given a team of six, 60% junior hires, 20% on-call load, and three concurrent vendor platforms.

Argue that 'audience-focused, example-rich docs' are overrated for network support specialists who mainly need quick checklists. Then immediately rebut your own argument and land on a pragmatic middle path: what specific hybrid doc format and maintenance rule should our team adopt? Keep it actionable (70–100 words).

Design a 30-minute workshop to teach 'writing troubleshooting docs' to our network support team. Use Audience-Task-Context and SBI adapted for docs; include a 10-minute hands-on exercise (with deliverable) and one discussion question that forces the team to choose between completeness and brevity.

Give me 5 specific post-meeting questions I can ask myself after any troubleshooting or handoff meeting to judge how well I applied Audience-Task-Context, SBI adapted for docs, and Single Source of Truth principles.