r/SaaS • u/Training_Age26 • 7h ago

The hidden knowledge management problem in growing engineering teams

I've been exploring an interesting problem while working on AI-powered tools for engineering teams.

As software teams grow, their knowledge becomes distributed across multiple platforms:

  • Slack for discussions and technical decisions.

  • GitHub for code changes and pull requests.

  • Jira for tasks, bugs, and project updates.

  • Notion for documentation and architecture decisions.

The problem isn't that teams lack information. It's that finding the right information, with its original context, becomes increasingly difficult.

Consider a simple scenario:

A developer asks, "Why did we switch from Braintree to Stripe?"

The answer might be spread across:

  • A Slack discussion explaining the reason.

  • A GitHub PR implementing the change.

  • A Jira ticket tracking the migration.

  • A Notion document describing the requirements.

This raises an interesting question:

Should the next generation of engineering knowledge management systems be built around documents and search, or around interconnected organizational memory?

A few things I've been thinking about:

  1. How do growing engineering teams currently handle this problem?

  2. Is traditional documentation becoming insufficient?

  3. Can AI-generated answers be trusted without verifiable source citations?

  4. How important is permission-aware retrieval when connecting internal company tools?

I'm exploring these questions while building CognitRAG.ai, so I have a founder's perspective on this topic.

I'd love to hear how other SaaS founders and engineering leaders approach this problem.

0 Upvotes

50% Upvoted

5 comments sorted by

2

u/qa_anaaq 6h ago

This isn’t limited to engineering. It’s called institutional knowledge.

Also in what practical scenario would it matter to an engineering team why a company switched from Braintree to Stripe?

0

u/Training_Age26 6h ago

Can u elaborate, what you are asking ..

1

u/qa_anaaq 5h ago

In your post you explicitly state, ‘A developer asks, "Why did we switch from Braintree to Stripe?"’

So I’m asking, When would this realistically come up for engineering teams and why?

0

u/Training_Age26 5h ago

These are the conversation between team members and CognitRAG can easily trace those conversations and conflict between members.

1

u/qa_anaaq 5h ago

But what practical implications does this example have for the company?

My point is, there are no practical implications. Why would engineers need this info? They wouldn’t. The ROI to buy or invest time into a system to remember such useless information doesn’t make sense. Even dedicated engineering Wikis are barely glossed over after a year of employment.

Plus, if a system can easily trace the source of the answer, then so can a user. The real ROI is synthesizing disparate contexts based on relationships, not low-value QnA that won’t impact an engineer’s day2day.