# The team's output

> Leading a search engineering group while staying close enough to the system to tell a relevance question from an operations question.

## The problem

A search team fails in two opposite ways. The lead becomes the only person who can change relevance, or the lead steps so far back that nobody owns the answer the user gets.

## The approach

I came up as a Solr developer and a staff engineer, and I now lead engineers on a search and matching platform. The published book is the sequence I want a new manager to have: listen first, earn one visible win, then build a team that runs without the hero.

## Subjects

- [Engineering management](https://oppority.com/topics/engineering-management.md)
- [Enterprise search](https://oppority.com/topics/enterprise-search.md)
- [Apache Solr](https://oppority.com/topics/apache-solr.md)

## The conclusion

Your output becomes the output of the team. That is also how you keep a search platform honest: more than one person can explain why the top result is the top result.

## Notes

- [Your output is no longer your output](https://oppority.com/writing/first-90-days-new-engineering-manager.md)

## Books

- [Your First 90 Days as a New Engineering Manager](https://oppority.com/books/first-90-days-engineering-manager.md)