The two-pizza rule for internal tools
Internal tools that try to serve everyone serve no one well. The best ones are scoped to a small team and a specific job.
There's a temptation to build one internal platform to rule them all — every team, every workflow, one tool. It almost always becomes a bloated thing that fits no one's actual job. Internal tools work better small and focused.
Scope to the team and the task
A tool built for a specific team's specific job can fit that job exactly. A tool built for everyone has to compromise on all of them. Narrow scope is a feature: it means the tool can match how this team actually works instead of how a generic team theoretically might.
Compose, don't centralize
Several focused tools that each do one job well, connected by clean data flows, beat one monolith that does everything adequately. They're easier to build, change, and retire. When a team's needs shift, you adjust their tool — not a platform a dozen teams depend on.
An internal tool for everyone fits no one. Build small, build focused, and connect the pieces.