It's an average Monday, and there are four people sitting in a Microsoft Teams meeting.
A Product Manager.
An Executive.
A Consultant.
An Engineer.
Just like normal, the engineer starts providing updates.
The quiet part that is detrimental to the business is the part that goes unspoken.
The product manager, executive, and consultant all have different takeaways.
That's where most AI meeting tools fall short.
They generate one summary for everyone.
But one summary doesn't answer everyone's questions.
Here's the conversation.
Engineer #1:
Heads up, PR #482 went red again. Conflicts with main after Sam's rebase.
Engineer #2:
Yeah... I force-pushed...
If you're an engineer, that probably makes sense.
If you're everyone else...
...maybe not.
What a Product Manager needs to know
A Product Manager isn't trying to understand every technical detail.
They're asking:
- Is my timeline changing?
- What's the risk?
- What do I need to unblock?
hmm translates the conversation like this:
Summary
The engineering team is dealing with a conflict in their codebase due to overlapping changes in their database migration files, which could break the deployment process. They are considering different strategies to resolve the issue, but face a delay due to the absence of a necessary code reviewer. This could impact the timeline for the upcoming release.
Risk
Medium — The primary risk is a potential delay in the release due to unresolved code conflicts and the absence of an approver.
Recommended Action
Consider requesting a temporary codeowner override to avoid blocking the release.
The Product Manager doesn't need Git commands.
They need to know whether the release is at risk.
What an Executive needs to know
Executives aren't managing pull requests.
They're making business decisions.
Their questions are different.
- Is this going to delay the release?
- Does leadership need to intervene?
- Is there customer impact?
hmm translates the same conversation like this:
Summary
There is a conflict in the code due to simultaneous changes, which could delay the deployment of a critical feature. This issue needs to be resolved quickly to avoid missing the release deadline.
Risk
Medium — The primary risk is a delay in the deployment schedule, which could impact the release timeline.
Recommended Action
Leadership needs to approve a temporary codeowner override to expedite the review process and avoid delays.
The technical discussion hasn't changed.
The explanation has.
What a Consultant needs to know
Consultants live somewhere in the middle.
They need enough technical context to communicate with engineering...
...but also enough business context to keep clients informed.
hmm translates the conversation like this:
Summary
The engineering team is facing a merge conflict in a critical payments feature due to simultaneous updates, which could delay the deployment. This situation requires careful coordination and possibly an override of the code review process to meet the release deadline.
Risk
Medium — The primary risk is a delay in deployment if the conflicts are not resolved and approved in time.
Recommended Action
Monitor the situation closely and prepare to communicate any delays or timeline changes to the client.
Same meeting. Different understanding.
Notice something?
The conversation never changed.
Only the explanation did.
That's the difference between summarizing a meeting and helping someone understand it.
A Product Manager wants to know if the roadmap changes.
An Executive wants to know if the business is at risk.
A Consultant wants to know what to communicate to the client.
Giving all three people the same AI summary misses the point.
AI should adapt to the person reading it.
Technical conversations aren't one-size-fits-all.
The best explanation depends on who's asking the question.
That's why we built hmm.
Instead of creating another meeting summary, hmm translates technical conversations into role-specific explanations so every person leaves the meeting understanding what matters to them.
Coming soon
We're launching the hmm AI Teams Bot, bringing real-time technical translation directly into Microsoft Teams.
If you've ever thought:
"What does this mean? Why should I care?"
You're exactly who we're building it for.
Join the waitlist at tryhmm.com/waitlist.