Michael works in product in the banking and finance industry. His days are mostly meetings with different teams, but he is careful not to describe the meeting itself as the whole job.
“The real work usually starts after the meeting, not during it,” he says.
That may sound counterintuitive in an industry where so much time is spent aligning stakeholders, reviewing options, and discussing risks in real time. But for Michael, the meeting is often where information first becomes visible. It is where questions are raised, assumptions are challenged, and competing paths are put on the table. The decision itself usually needs more space.
A lot of his work is about sitting with complexity without forcing a conclusion too early.
“I’m often thinking about whether I need to decide now—or if it’s better to wait until I’ve thought it through properly,” he says.
That instinct matters in banking and finance. Decisions are rarely made in isolation, and they often carry constraints that are not obvious from the outside. A product choice might involve technical feasibility, customer experience, risk, compliance, operations, timing, and long-term maintainability. In that environment, moving quickly is useful only if the reasoning is sound.
Michael learned that early. When he first started working in more complex environments, he tried to make decisions in the room. Over time, he realized that was not always the right approach.
“Complex decisions need distance,” he says.
Before using Plaud, Michael often left meetings with a lot in his head. He would remember the main discussion and the broad options, but it was harder to walk back through the reasoning cleanly afterward. What risks were raised? Which assumption changed the direction of the conversation? Why did one path seem better than another? Which part of the decision was evidence, and which part was instinct?
“Before Plaud, I’d leave meetings with a lot in my head, but no clean way to walk back through my own reasoning,” he says.
That distinction is important. Michael was not looking for a tool to capture every meeting or create a record of everything said. In fact, because he works in a regulated environment, he is clear that any tool has to respect real limits.
“Of course,” he says, when asked whether he had any hesitation before using Plaud. “I can’t record most internal conversations, so any tool has to work within those limits.”
That constraint shaped how he uses it. For Michael, Plaud is not a blanket recording tool. It is something he uses very intentionally, often outside the office or after the fact, when he has room to think. The value is not in indiscriminately capturing everything. It is in giving him a structure for reflection when a conversation is over but the decision is not.
“Usually when a discussion is done, but the decision isn’t,” he says. “That’s the moment it’s most useful.”
In those moments, Michael uses Plaud to reconstruct his own thinking. He goes back through the options, the risks that came up, and the reasons one path may make more sense than another.
Sometimes that means recording his own reflections after a meeting. Sometimes it means flagging the pieces that need more attention so he can return to them later with a clearer head.
“I like that I can flag what matters, then come back to it later when I’m in the right headspace to think,” he says.
The phrase “right headspace” comes up naturally in his story. A meeting can be useful, but it is not always the best place to finish the thinking. There may be too many voices, too many moving pieces, or too much pressure to respond immediately. For Michael, having a way to return to the reasoning later helps him separate the urgency of the conversation from the quality of the decision.
He describes the effect plainly: “It helps me slow my thinking down and make it defensible, not just intuitive.”
That word—defensible—says a lot about his work. In some professions, a good decision only needs to feel right to the person making it. In Michael’s environment, that is not enough. A decision needs to be explainable. It needs a trail. If someone asks why a certain direction was chosen, he needs to be able to walk back through the reasoning without relying only on memory.
“It gives me a clear trail of how I got to a decision,” he says. “That really matters in my environment.”
This is where Plaud fits into Michael’s workflow. It does not replace his judgment. It does not make decisions for him. It gives him a way to preserve and revisit the thinking around a decision, especially when the first conversation is only the beginning of the process.
There was one situation where that mattered. Michael describes it without over-dramatizing it: a decision could not be made in the room. There were too many factors involved, and choosing too quickly would have meant skipping over parts of the reasoning that needed more attention. Being able to step back and work through the decision properly made the difference.
“There was a situation where the decision couldn’t be made in the room,” he says. “Being able to step back and work through it properly made the difference.”
That example captures the real value of Plaud for him. The benefit was not speed for its own sake. It was the ability to create enough distance from the meeting to think clearly, while still keeping track of the logic that came out of it. In a fast-moving workday, that kind of distance is easy to lose.
Michael also talks about the emotional side of this, though not in a dramatic way. Plaud makes the process feel steadier. It reduces the pressure to rush himself into a conclusion while a conversation is still unfolding.
“It feels steady,” he says. “Like I’m not rushing myself into conclusions.”
That steadiness has practical consequences. He describes fewer rushed decisions and fewer moments where he has to revisit why something was decided. In complex work, those two things are connected. If the reasoning is unclear at the time, it often creates more work later: more clarification, more backtracking, more time spent trying to reconstruct the original logic.
With Plaud, Michael is more comfortable letting conversations flow because he knows the thinking can continue afterward.
“I’m more comfortable letting conversations flow, knowing the thinking happens later,” he says.
That is not the same as postponing responsibility. It is a more disciplined way of handling decisions that deserve more than an immediate reaction. For Michael, the ability to revisit and pressure-test his own thinking is part of doing the work properly.
“If Plaud disappeared tomorrow, I’d miss having a way to slow down and pressure-test my own thinking,” he says.
What stands out in Michael’s story is how restrained his use case is. He is not trying to automate judgment away. He is not asking AI to give him an answer to copy. In fact, his view of technology is almost the opposite.
“AI is most useful when it gives you space to think, not answers to copy,” he says.
That line gets close to the center of his relationship with Plaud. The product is useful because it protects the conditions that good judgment needs: time, structure, context, and the ability to revisit the logic behind a decision. It helps him stay with the complexity instead of flattening it too quickly.
At the end of the interview, Michael put it simply.
“It doesn’t replace judgment,” he says. “It protects the time and structure judgment needs.”
For a product manager in banking and finance, that is the point. The work is not just making decisions. It is making decisions carefully enough that he can stand behind them later.
Be Present — Because Every Conversation Matters.
