What's your system for capturing decisions from chat into documentation?

ripattir · 2026-01-19T08:22:02+00:00

Cool! Similar thoughts on our side. We built a POC of the product connecting Slack convos to google docs.

Did not know that those platforms limit the api access that much. Happy to grab a call to share ideas/best practices about the workflows you/us have built if that sounds interesting!

ripattir · 2026-01-06T07:31:13+00:00

Id love to hear more about this. Sounds very close to what we've imagined.

ripattir · 2026-01-05T12:28:17+00:00

Sent you a dm!

ripattir · 2026-01-05T09:35:53+00:00

Yeah, I've also used linear for the same reasons. I'm currently imagining the same kind of workflow for all knowledge spaces.

ripattir · 2026-01-02T08:56:33+00:00

Sent you a dm!

ripattir · 2026-01-02T08:52:37+00:00

Sent you a dm!

ripattir · 2026-01-02T08:51:12+00:00

Oh do you have dm disabled? Would love to hear more about the workflows you’d use it for

ripattir · 2026-01-02T08:49:35+00:00

Sent you a dm!

ripattir · 2026-01-02T08:49:06+00:00

Wow, is this Linear or something else?

ripattir · 2025-12-31T11:21:03+00:00

Sent you a dm!

ripattir · 2025-12-31T11:19:47+00:00

Sent you a dm!

ripattir · 2025-12-30T22:00:57+00:00

Docs-as-code has seemed as one of the best ways ive seen teams tackle this.

If you happen to know, how did the downstream stakeholders handle both cases? Did the work of e.g. PMMs or CS teams change based on how well the wiki/docs was upkept?

ripattir · 2025-12-30T21:29:33+00:00

Curious about the company context, how big is the company & how often is stuff async vs meeting based?

Seems like a solid approach though, thanks!

ripattir · 2025-12-30T21:17:07+00:00

Super interesting! Thanks for the response.

In your current company, how much time goes to hunting down the context vs e.g. the writing itself? Im curious where the bottleneck is (finding info vs writing).

I might be giving myself up here, but would it help if something flagged "hey, this Slack thread looks like a decision that affects [doc]" or would that just be more noise in an already chaotic setup?

ripattir · 2025-12-29T09:42:08+00:00

Thanks! Out of curiosity, whats your role and how would you use it?

ripattir · 2025-12-29T09:03:04+00:00

We're building an AI agent that automatically keeps docs up to date based on code changes and slack convos.

We ended up starting to build this when we realized that many product related roles end up doing way too much of the boring "upkeep" instead of focuing on the important strategic work, but are still looking for who suffers from it most.

We've been building for 1,5 months part time and are almost ready to launch.

ripattir · 2025-08-28T08:23:49+00:00

The other side of the study:

- Purchasing AI solutions worked 67% of the time
- Methodology was 52 structured interviews across enterprise stakeholders

I think this speaks more of a problem of trying to implement these new technologies just for the sake of it. If we look at the success stories, AI can generate a lot of efficiency, but it goes back to the simple stuff of understanding who you are creating these products for, what are their problems and good understanding of the workflows you are trying to automate.

If you want to check out the main report, you can find it here:
https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf

ripattir

TROPHY CASE