How our MSFT-X team learned to read between the lines
One habit has stayed with me through every role change since my days in the Admin team as an Architect: arriving before 8 a.m. That quiet time allows me, even now in the Services team, to review the emails and requests coming in each day. I'm not simply reading what customers want. I'm looking for the reason behind the request, the challenge they're trying to solve, and the need they may not have articulated yet.
The drill and the hole in the wall
There's an analogy I keep coming back to. When you go to a hardware store to buy a drill, you don't actually want the drill. You want the hole in the wall so you can hang your frames. It's the same with our customers. It's not the deck they want; it's what they want to achieve with it. Maybe they want to recognise their team members and make people feel special. Maybe they want to impress their bosses. When we understand that, we can help them achieve it in the best way possible, so that when they buy something from us, they buy a better version of themselves to present.
In our team, a small group of us is intentionally looking for these opportunities: myself, Marlene, Anji, Meban, Mahesh, Synshar and Pynshkem. We have a huddle at 9:30. We screenshot the emails that feel important and bring them to the discussion. We look at which team and department the customer belongs to. If they deal with an external audience, maybe video or interactive slides are the right way to get the message across. If something worked with a similar team, we try it again; if it didn't, we try something else. Then we either execute it ourselves or bring in the POC.
Three ways we think about value
Better execution: doing what the customer asked, and doing it to the best. That's expected, so we don't count it as new value.
Better solution: the customer asks for one thing, but we think another approach would work better. One customer usually announced their yearly awards through emails. We turned it into a video with the nominees and winners, where colleagues could react and comment. They liked it.
New opportunity: seeing a need the customer didn't mention. One customer asked for a flyer but was clearly struggling with the content, so we offered content support too. They didn't go ahead, but we tried.
This framework has helped us stop focusing on the requested deliverable and start focusing on the desired outcome. We choose the method based on what the customer is trying to achieve, not a favourite tool
What it has meant for us
The biggest change hasn't been the opportunities we've found. It's the way we think.
We've started looking beyond requests to identify needs, uncovering opportunities that might have otherwise gone unnoticed. Customers are now coming to us for services they hadn't previously considered.
What was once owned by a single person is now owned by the team. Opportunity spotting has become part of our daily conversations, and people call out potential ideas as soon as they see them.
It's not always easy
Some customers tell us who the audience is and what the occasion is, which makes it easy. Others just ask us to polish a slide, so we have to open the deck and work out the message ourselves. Our customers are all in the US, so if we try an experiment, we usually only hear back at the end of our day, and if they don't like it, we start again the next day.
But experiments are rarely wasted. One customer first said no to a video, and later came back asking for exactly that.
The best opportunities are hidden in the gap between what the customer asks for and what they're trying to achieve. Our job is to bridge it.
What I've learned
New customer value isn't only about AI or new tools. It's about people understanding needs.
Pick the tool after you understand the outcome, whether that's PowerPoint, video, Viva Engage or Copilot.
Even an experiment that's turned down shows customers what you can do.
Blog Categories
Recent Posts
Tags

Only for Those Determined to Do More!



