When you reinforce your expertise, it gives clients the confidence they need to support you and your recommendations and provides evidence they can use to sell you to their co-workers, managers, and team mates.Īnd just wait. It tells the client I’ve done this before. Instead, I describe what I do as my experience. It’s not “…I’m looking forward to designing your new site and jump-starting lead generation!” I see some do that, and it must work, but… ick. I don’t do the smarmy thing where I describe what I want to do for them. Where we build custom tailored applications on top of the Microsoft stack. I’m a Design Lead with the Houston Studio I help clients configure and optimize their Microsoft365 platforms, so employees can work better and be more productive. I’m a Workplace Experience Architect with Avanade. Where I work with agile teams to make sure the engineering team has the designs they need, when they need them.
I’m a User Experience Lead in Avanade’s Digital Studio My introduction went something like this: I surmise the Engineering Director worries about how UX will affect velocity. Describe how your expertise addresses that worry.Īn example: We’re selling UX pods to an agile project. Address this worry in the second part of your introduction. What issue about the thing they want to talk about worries them the most. What the client worries aboutĪfter you answer the first question with a title they understand and expect, them know you’re the person they should be speaking to.Īs you prepare for your meeting, ask yourself: What is the client worried about? Not what do they want to talk about. Tailoring your title to what the client expects, so you can answer that question with a yes. When it’s your turn to introduce yourself, your client asks themselves if you’re the person they need to speak to. The client doesn’t care about your aspirations.) (If you’re a product designer, and the client barely knows what UX is, I promise you, it’ll go better if you just say you’re a UX designer. But how I describe myself from one meeting to the other is based on who the client expects or wants to meet. I’ve been a usability analyst, user researcher, accessibility lead, team lead, project manager, business analyst, and digital strategist, and I’ve delivered and can deliver all of those roles. Never lieĭon’t make up a title that wouldn’t fit. The most important constraint: never lie. Is there another designer involved? Then I’m a UX Lead or UX Architect.ĭo they see UX as too low-level and want to speak with someone more strategic, then I might be a Workplace Experience Lead. So, when I meet new clients, I use a title they both understand and expect.ĭo they think of UX as mostly visual design? Then I’m a UX Designer. Very few clients understand-at first glance-an “experience director”. Experience means I do experience design… at Avanade. Director means I’m senior and lead teams… at Avanade. Your title most likely doens’t reflect who the client wants to speak to. Someone created your title to identify you inside your company, not to identify you to clients. Right away, your introduction should let the client know you are who they want to speak to. Who does the client want or expect to meet? To craft a good intro, take a couple minutes before the call and answer two questions: It’s about who the client needs you to be. Your introduction isn’t about who you are. The introduction offers one of your first opportunities to forge a connection and tell your story. When you introduce yourself in terms of what you do for your organization, you start the conversation off communicating badly. I’m not communicating in a human-centered, client-centered way. I am an Experience Director with Avanade’s Digital Innovation Studio. And when the time comes, you rattle off your name, organization and what you own or lead or drive for your organization.
If you’re like most people, you spend the beginning of a call waiting for your turn to introduce yourself.
0 kommentar(er)
