Member-only story
Capturing Knowledge with the Backstage Qeta Plugin
Why StackOverflow-style Q&A belongs in your developer portal, not Teams.
At OP Financial Group, we have thousands of engineers spread across dozens of teams. When someone solves a tricky problem with our Kubernetes setup or figures out why the CI pipeline behaves strangely on Wednesdays, they share the fix in Teams. The channel gets a few clapping emojis. Everyone moves on.
Three months later, a new developer joins and runs into the same problem. They spend two days debugging. Eventually they ask in Teams. Someone says, “Oh, we solved this before, just search the channel.” They search. Teams search is useless for anything older than two weeks. Nobody finds the thread. They ask again. Someone who half-remembers the solution throws out a vague answer.
If I had a euro for every time I heard or typed “just search the channel”, I would probably be driving a new car every month.
TL;DR: Qeta brings StackOverflow-style Q&A into Backstage. Questions get attached to catalog entities, answers stay findable forever, and AI can pre-answer routine questions. After six months, senior developers spend less time on repeat questions, new hires onboard faster, and Teams is quieter.
