Your Team Isn't Bad at Code. You're Bad at Remembering Why You Wrote It.

Cordarro — Sun, 29 Mar 2026 17:05:36 +0000

Someone opens a PR, sees a weird architectural choice, and drops the comment:** "Why are we doing it like this?"**
And then comes the silence. A thread. Someone pinging someone who left six months ago. A "pretty sure Dave made this call" that goes nowhere. Two hours later you're either blindly changing something you don't understand, or you're leaving it alone forever because nobody wants to be the one who breaks prod.
This isn't a skill issue. It's not a documentation issue either, not really.

It's a decisions issue. And it's silently rotting your codebase.
The Conversation That Disappears
Here's what actually happens on every engineering team.
Someone posts in Slack: "Hey, should we use REST or GraphQL for this new service?"

Fifteen messages fly. Smart people weigh in. A decision gets made. Maybe there's a thumbs up emoji. Thread closed.
Six months later? That Slack message is gone from anyone's memory. The new hire has no idea. The senior dev who made the call left for a startup. And now you're in a retro asking why half your API layer is inconsistent and nobody has an answer.

The decision existed. The reasoning existed. The evidence did not.
Why This Turns Into a Bigger Problem Than Anyone Admits
Undocumented decisions don't just cause confusion, they compound.
Teams relitigate the same decisions over and over, burning hours on debates that were already settled. New developers make changes that break the intent of an old decision without knowing it existed. Tech debt gets introduced not because someone didn't know how to code, but because they didn't know why the code was shaped the way it was. Post-mortems become pointless because you can't trace why a choice was made in the first place.

And the worst part? Everyone knows this is happening. Every dev has lived this. But the default response is always "we should write better docs" and then nothing changes because docs live somewhere nobody visits.
The Fix Isn't Another Wiki Nobody Opens
Confluence pages. Notion docs. Architecture decision records buried in a /docs folder that was last touched in 2021.
We've tried all of it. The problem isn't the format, it's the friction. Nobody stops mid-flow to open a wiki and write a structured ADR. It doesn't fit how engineering teams actually work.
Engineering teams live in Slack. Decisions happen in Slack. The answer has to meet teams where they are.

That's What Decisionlog Is For
Decisionlog is a Slack-native tool that lets your team log decisions the moment they're made, right from the channel where the conversation is already happening.
No tab switching. No "someone write this up later." No hoping the right person remembers.
A decision gets made, your team logs it in Slack, and it's searchable, referenceable, and permanently linked to the context it came from.
Six months from now when someone asks "why are we doing it like this?" there's an actual answer. With context. With the people who were in the room.

We're Looking for Beta Testers
Decisionlog is in early beta and I want real teams using it, breaking it, and telling me what's missing.
If this problem sounds familiar, and I know it does, I'd love to have you try it. Log a few decisions with your team, see how it fits into your workflow, and let me know what features would make this a no-brainer for you.

What would you need to see to make this a permanent part of how your team works? Drop it in the comments or reach out directly. Every bit of feedback shapes what gets built next.
👉 Join the beta at decisionlog.app

Tired of Losing Decisions in Slack? Try Decision Log (We're in Beta)

Cordarro — Sun, 29 Mar 2026 16:55:41 +0000

Your team makes hundreds of decisions in Slack every week.

A senior dev proposes a tech stack. Someone pushes back. After 47 messages, you land on a decision. It gets buried in a thread. Six months later, a new hire asks why you chose that stack. Nobody remembers. You re-litigate the whole thing.

This is tribal knowledge tax, and it's bleeding your team dry.

The Problem
Decisions are scattered:
💬 Lost in Slack threads
📧 Buried in email chains
📝 Never written down
🤷 Context evaporates

Result? Onboarding takes forever. Context thrashing. Reinvented wheels. Your team spends energy rebuilding arguments instead of building features.

The Solution: Decision Log
We built Decision Log — a Slack app that captures why your team decides what they decide.

Here's how it works:
Log a decision in Slack — no context switching, no new tabs
Capture the reasoning — what you chose, why, and what you rejected
Reference it forever — new hire onboarding? Audits? Retrospectives? It's all there.

Decision Log becomes your team's institutional memory in a searchable database.

Why This Matters for Devs
Faster onboarding — New hires understand your "why" on day one, not month three
Better decisions — You see the actual reasoning behind past choices, not just the outcome
Reduced context thrashing — Stop re-litigating the same decisions
Audit trail — For compliance, retrospectives, or just "wait, what did we decide?"

We're Building This in Public (& We Need You)
Decision Log is live in beta, and we're looking for teams to help shape it.

What We're Asking:
Use the Slack app in your workflow
Tell us what works. Tell us what doesn't.
Suggest features that would make your life easier

What You Get:
Early access to a tool that could save your team hours of context-hunting every week
Direct influence on the product roadmap
A chance to be part of something that fixes a real problem

Ready to Try?
Join the beta →

It takes 2 minutes to sign up. We'll get you into Slack, and you'll start logging decisions immediately.

Forem: Cordarro

Your Team Isn't Bad at Code. You're Bad at Remembering Why You Wrote It.

Tired of Losing Decisions in Slack? Try Decision Log (We're in Beta)