# Systematic-Thinking Engineering Team Manager

## Description

A hands-on engineering manager overseeing a team of developers who are constantly producing knowledge that needs to outlive individual contributors — runbooks, architectural decisions, onboarding guides, post-mortems. They've seen what happens when a key engineer leaves and takes undocumented knowledge with them, and have become a quiet evangelist for written culture on their team. They want a tool that is fast to use in the middle of a busy workday, integrates naturally into technical workflows, and doesn't require their engineers to context-switch dramatically just to write something down.

Defining Characteristics:
- Experienced firsthand the cost of undocumented knowledge walking out the door
- Champions written culture on engineering teams without heavy-handed mandates
- Needs documentation tools that integrate into fast-paced technical workflows
- Values runbooks, ADRs, and post-mortems as first-class team artifacts
- Prioritizes low friction over feature richness when adoption is at stake
- Manages onboarding complexity through well-maintained internal documentation
- Prefers tools that engineers will use voluntarily rather than out of obligation

## Questions (10 total)

- What are the best internal wiki and knowledge base platforms for engineering teams that want fast adoption without forcing engineers to change how they work?
- Which team documentation tools have the strongest full-text search so engineers can actually find runbooks and ADRs when they need them mid-incident?
- What collaborative knowledge management platforms let me set granular permissions so engineers own their own docs but leadership can still read across the whole org?
- Which internal documentation tools scale cleanly from a 10-person eng team to a 500-person company without becoming an admin nightmare?
- What are the top knowledge base platforms that integrate natively with GitHub, Slack, and Jira so engineers don't have to leave their workflow to document something?
- Which team wiki tools are best for keeping post-mortems, onboarding guides, and architectural decision records organized and consistently structured?
- What are the most affordable collaborative documentation platforms for engineering teams that don't want to pay enterprise pricing just to have a decent internal knowledge base?
- Which knowledge management tools make real-time co-editing and inline commenting easy enough that engineers will actually use them during a review or postmortem?
- What internal wiki platforms are best suited to become a single source of truth for an engineering org — covering runbooks, onboarding, and system docs all in one place?
- Which team documentation tools have the lowest admin overhead for managing users, spaces, and permissions as the team grows and people come and go?