Agile project management allows you to produce smaller deliverables more frequently and efficiently, making it an excellent choice for teams that work in product development, programming, business analysis, and other collaborative areas. But it's a fragile process that requires the right scope, goals, and management. In this course, we show you the tools and techniques you need to successfully manage a project through the agile life cycle. Learn how to use agile for the right projects and then walk through the four major phases in the cycle, from scoping the work and designing your sprint structure to collecting requirements, managing the project without interfering in the rapid build process, adapting to feedback, and closing the project. Topics include: What is agile project management? Selecting an agile project Scoping the project Designing your sprint structure Collecting requirements Running stand-up meetings Managing issues and risks Tracking lessons learned Responding to change requests Closing the project Spotting signs of trouble
You can’t always give your customers everything they want, and that is ok, trust me.
It would be impossible (and bad for business) to build every single feature your users or clients suggest, or to accept every imaginable form of payment, or to offer full refunds on anything and everything. You’re going to have to tell customers “no.” and clearly define what is acceptable and what is not.
On top of that, there are times when things go wrong. Servers go down. Errors occur. Features don’t go as planned. Your end users can’t do what they need to do, and you need to bear the bad news to the client.
But saying “no” to your customers can present a risk.
In any customer interaction, the words you use either build up your relationship with the customer or tear it down.
This is true whether you’re writing UI copy, sending a marketing email, responding to a support ticket, or even helping a customer in a store (for you omni-channel teams). And that’s exactly why it’s important for companies to get it right, consistently, across all channels and departments.
No small task!
So where do we begin?
Start with empathy
Our first instinct as professionals and ultimately human beings can be to defend our company and our policies—and to assume the user is at fault. But your users’ needs should be your top concern. Even when you aren’t able to give them what they want, you should understand and care about where they’re coming from.
When you understand how your user is feeling and why they’re feeling that way, your response will be much more genuine than if you think of them as just another problem. Coach your team on practicing empathy for your users so that your responses are consistently sincere. Some call it EI or Emotional Intelligence and it is something that takes practice to learn. The best way to learn EI is experience. You’ll learn how your clients operate and how they view the world; everyone is different.
Choose your words wisely
It may not surprise you to learn that “no” is a pretty loaded word. Andrew Newberg, M.D., and Mark Waldman have called it the most dangerous word in the world; just a brief flash of the word “no” on a screen can release stress-producing hormones in the body, impeding reasoning and communication.
It doesn’t take a neuroscientist to know that people don’t like being told “no,” but there’s also a case to be made for being honest and direct with your customers. It’s easy for customers to spot an indirect response that skirts around the issue to avoid blame. It’s also easy to spot overly cheerful language that can come across as cheesy and insincere in a negative situation.
- When possible, choose words with positive connotations (while still being sincere).
- Be careful that your response doesn’t place blame on the customer.
- Be brief but kind. Get to the point.
- If an apology is called for, then give it openly.
- If good alternatives are available, present them enthusiastically.
- Involve the client in your decision making process.
Here’s a nice example from the FAQ section of Dollar Shave Club’s site.
While the customer might be temporarily disappointed that they can’t mail a check, the copy does a nice job of making online payments seem like an even better alternative. (Bonus points for including a Contact Us button in case the user has further questions.)
Explain (and understand!) why “no” is the answer
The one thing worse than telling a customer “no” is telling them “no” without a reason. In fact, offering a reason can make people much more likely to respond positively.
In a 1978 experiment, researcher Ellen Langer found that when asked for a small favor (cutting in line at the copy machine), people were 50% more likely to comply if the request was followed by a reason.
Interestingly, people were equally likely to comply whether the reason offered additional, legitimate information (“because I’m in a rush”) or was just bogus (“because I need to make copies”).
Of course, I’m not encouraging you to go making up bogus reasons for your denial! It’s much better for your relationship with your customer if you explain the honest (but brief) reason why you can’t help them out. This not only offers them the peace of mind that there’s a reason why they can’t do what they want; in some cases, it gives them an idea of what to do instead.
Here’s an error message I found when I made a typo trying to sign into Slack.
What’s so great about it?
It not only tells me why I can’t sign in (Slack can’t find a team called “thedigitalpm”), it also offers a link to help me find my team and even gives me a reminder of a team I’ve already signed into.
Align your team’s voice and tone with a style guide
This document is the Content Strategist’s best friend. And the UI Copywriter’s. And the Customer Experience Manager’s. And… okay, everybody loves a good style guide. It’s your company’s playbook for addressing your audience in a helpful, positive, on-brand manner. It empowers your team members to write and speak to customers confidently, even in awkward situations.
If you don’t have a style guide yet, now’s the perfect time to create one. It doesn’t need to be fancy; it can be as simple as a list of words to use and not use. If you’re feeling nerdy, you can make your style guide more robust by adding in separate guidelines for different types of content and interactions, your company’s preferred grammar rules, brand assets, and so on. For inspiration, check out MailChimp’s style guide.
Once you have a style guide, make sure the different departments in your company know where to find it and how to use it. You might find it helpful to sync up with different team leaders and create separate sections for in-person, phone, chat, and written communications.
The power of “no”
Being able to decline customers with grace is a key to a lasting customer relationship. Whether it’s in an email, chat message, phone call, or in person, encourage your team to practice empathy for the customer, be honest, and maintain a positive approach. It’ll go a long way toward creating trust with your customers.
If you like this article feel free to check out some others on Digital Project Management.