Fifteen people. Fifteen minutes. Roughly ninety seconds of information.
The format's failure is structural, not cultural. You're asked what you did yesterday at the exact moment you're least able to answer before coffee, from memory, in front of an audience. So everyone reports the ticket they had open, because that's the retrievable answer. The actual texture of the day, the part where you'd learn something about how the sprint is really going, is gone.
The thing that's worked better for us: declaring intent in the morning instead of reporting history. "Here's what I'm picking up today" takes ten seconds, is answerable without memory, and produces something you can compare against reality at 6pm. Plan versus done, written down, no meeting.
Where it falls apart is that plan-versus-done is only useful if nobody's judged on the gap, the moment it becomes a scorecard, everyone starts declaring safe plans.
Congrats. Looks very interesting. 😊 What's on your roadmap?
@roopreddy Thanks! Our roadmap includes integrations with Linear, GitHub, Azure DevOps, and Trello, along with more personalized productivity insights. We’re also improving the activity timeline, task matching, and drafted updates based on feedback from this launch. As one of Meridian’s makers, the standard we’re building toward is a private, transparent work journal that stays useful to developers without becoming a monitoring tool. Which part would be most valuable to you?
@roopreddy We’re looking for B2B SMB companies where we can implement Meridian and make a measurable difference for engineering teams. If that matches your company, I’d be glad to discuss a pilot.
Can non-devs use this product? I would love to!
@himani_sah1 Yes, it’s for anyone who works on a computer! We’ve tested Meridian with non-developers, and it works very well for them too.
@himani_sah1 @adityaharish2002 how does this work for non-devs? for example, if my workflow is a combination of email, zoom calls, slack, claude/chatgpt, manus -- does it just take screen shots periodically and from their deduce what tasks i have worked on or is there something else?
@himani_sah1 @adityaharish2002 @rafaella_fontes_be Meridian captures on-device activity from tools like email, Slack, Zoom, and Claude or ChatGPT, then uses that context to identify and summarize the work you’ve done. It doesn’t simply take periodic screenshots.
This is really cool. How does it map the work with existing tickets.. lets say in Jira?
@chilarai Meridian analyzes your on-device activity, then matches that context against open Jira tickets. It suggests the most relevant ticket and drafts an update for you to review and approve before posting.
@adamroot Yes, Meridian can generate a weekly bullet-point summary of completed work, so you don’t have to spend an hour compiling it manually.
@adamroot Yes, Meridian can serve as an automatic second brain for work. It continuously captures on-device activity, organizes it into a timeline, and preserves the context Claude would otherwise miss, including investigations, decisions, unexpected fixes, and unplanned work. Unlike Obsidian, it does not require you to manually write and organize every note.
It does not currently pull context from Granola transcripts.
Are you going bottoms up with this, or planning to sell into larger organizations with large performance review cycles?
@tori_seidenstein We’re starting bottoms-up with individual developers and small engineering teams, then expanding into larger organizations as we learn what they need. Performance review cycles are a strong use case, but we want Meridian to remain developer-first rather than become a top-down monitoring tool.
Is it voice-led right?
@busmark_w_nika Not currently. We don’t record voice. We may explore that for meetings in the future, but for now, Meridian gets enough context from on-device activity.