I recently interviewed a candidate who asked for a lot of ‘stuff’ during the interview process. She wanted compensation, perks, accommodations, and benefits that were way outside the norm. I’m assuming she was employing the adage we’ve all heard, that “it can’t hurt to ask.” Unfortunately, it can hurt to ask.
When forging new relationships, we watch (judge) people. We’re trying to figure out who they are and how they are. Are they the person they claimed to be during the interview process? Are they trustworthy? Did I make the right decision in bringing this person into my team, organization, and life?
Requests always make an impression. When we’re building new relationships, requests make an even bigger impression. Candidates who said the commute wouldn’t be an issue, but complain about it two weeks into the job, cause managers to doubt their hiring decision. Coworkers who consistently ask for extensions to deadlines, appear unreliable.
People watch us and silently judge, making assessments about our commitment, reliability and even character. Don’t make people question you. Make reasonable asks.
Five ways to make reasonable requests:
Vet your requests with people who know your company, manager, and/or industry, before making them. A reasonable request in one organization, might not be reasonable in another.
If something is important to you, ask for it during the interview process or at the onset of new projects and relationships. Don’t wait. Waiting to ask for things until after you’ve started a job can damage your relationships and reputation. Managers don’t like bait and switch, even when it’s unintended.
Once you’ve received an emphatic “no”, accept it. I worked with someone who asked for something during the interview process. I said “no” and explained why. He asked again after being hired. This annoyed me and made me feel like he didn’t listen.
If you think a change should be made in your organization, propose a solution. Offer to be the person who drives the process, if appropriate. Pursue the change over a period of months. Ask up to three times for changes to be made. If nothing changes over a period of months, ask the leader you’ve been working with if you should stop asking. The change may not be a priority, and over asking can make you look like a pest who doesn’t understand the organization’s priorities.
If you aren’t sure that what you’re asking for is reasonable, say so. Tell the person what you want and to please tell you if it isn’t a reasonable request.
Ask for feedback on your requests. If you’ve seen me speak, you know I’m a proponent of telling people, “If I do anything that damages our working relationship or makes you question me, I hope you’ll tell me. I promise I’ll take your feedback graciously and say, “thank you.”
Ask for what you want, within reason, be upfront when relationships begin, and build your relationships rather than break them.
Many people struggle to say no. As a result, when someone has a request that we can’t or don’t want to meet, we often say nothing. We simply don’t respond. Or we put the person off, telling them we’ll get back to them. Then people wonder. “Did they get my request? Should I send the request again? Will I look bad if I ask again? How many times should I ask before I just let the request go?”
Saying no is better than saying nothing. No gives people closure. Silence leaves people in limbo wondering what they should do next.
Saying no can be hard. We don’t want to disappoint or let people down. And yet, you can’t say yes to everything. You can say no and still sound like a responsive, easy-to-work-with, accommodating professional.
Here are ways to say no:
Thank the person for asking. “Thank you for asking me.”
Saying “thank you” acknowledges the other person and buys you time to think about their request.
Tell the person you need some time to think about their request. Ask, “Can I have a few days to think about it? I’ll get back to you by Friday.”
You don’t need to reply in the moment. I often regret things I agree to without thinking through the request thoroughly.
Consider what you really want and are willing to do. It’s much worse to over commit and under deliver than to simply say no or renegotiate requests.
Get back to the person in a timely way (when you said you would) and tell them what you’re willing to do.
How to Say No Option One: Simply say no.
Example: “I really appreciate you asking me to write the proposal for the __________ RFP. I’m not able to do that. Can I recommend someone else who has the expertise and time to do a great job?”
Don’t give a bunch of reasons for saying no. People aren’t interested in why we can or can’t do something; they just want to know if we will do it.
How to Say No Option Two: Agree and negotiate the time frame.
Example: “I’d be happy to do that. The first chance I’ll have to work on this is the last week of the month. Does that work for you?” If the answer is no, negotiate further. Ask, “What is the hard deadline? I can certainly do pieces by then, but not the whole thing. Given that I can’t meet your timeline, who else can work on this in tandem or instead of me?”
How to Say No Option Three: Say no to the request but say what you can do.
Example: “I can’t do _______. But I can do ________. How does that work?”
A review of how to say no:
Acknowledge the request by getting back to the requestor within 24 hours.
Give yourself time to think about and respond to requests.
Negotiate requests to your and the requestor’s satisfaction.
Agree on what you can and are willing to do.
Keep your commitments.
Saying no is hard. But it’s always better to say no than to ignore requests, or to say yes and do nothing.
If you work long enough, you will have a manager who doesn’t delegate well, doesn’t give feedback, and isn’t a great coach. Not everyone is a good manager.
You’re accountable for being successful, regardless of who you work for. Don’t wait for people to tell you what they need and expect, which often happens after breakdowns occur. Set clear expectations at the beginning of anything new and ask for feedback as you make progress. Take your career and success into your own hands. I call this reverse delegation.
Reverse delegation defined: Asking questions until you’re clear what a good job looks like and asking for work to be reviewed in stages, versus solely at the end of a project, ensuring you get all the information you need to be successful. Ultimately, taking your career success into your own hands, where it belongs.
The people you work for and with should tell you what they expect. They should give you feedback along the way. And many won’t. Your career is in your hands, and that’s a very good thing.
When you start a new job, project, or any responsibility, ask the person delegating the work some of these reverse delegation questions:
Reverse Delegation Question one: Why is this project a priority right now? How will it impact the organization?
Reverse Delegation Question two: What does a good job look like? What’s the criteria for success?
Reverse Delegation Question three: What kind of updates would you like? In what format, how frequently, and with what level of detail?
Reverse Delegation Question four: Who in the organization should I work with on this project?
Reverse Delegation Question five: What history, pitfalls, or landmines do I need to be aware of? Has anyone tried to do this before, and if yes, with what outcomes?
Reverse Delegation Question six: Who in the organization supports this project? Who doesn’t?
If you’ve been in your job for a long time or have been working on a project for a while, it’s not too late to ask these questions. Simply approach the person with whom you’re working and say, “I want to be sure I’m doing great work on _____________ project. Can I ask you a couple of questions about the desired end results and how we should be communicating, as I make progress?”
Lots of people aren’t the best delegators. They give us a project, ask if we have any questions, and provide a due date. Don’t fall into the trap of completing an entire project and then asking for feedback. Even if the person delegating the work doesn’t want to review work as it’s completed, ask for that feedback. Schedule weekly or monthly review meetings, present the work you’ve done, and ask for feedback. If you’re worried asking for iterative feedback will make you seem needy or like you don’t know what you’re doing, explain why you’re asking. Say something like, “I want to give you precisely what you’re asking for and don’t want to squander the organization’s resources.”
If you get to the end of a project or responsibility and what you deliver isn’t what the person delegating expected, you didn’t ask enough questions at the beginning and middle of the project, and didn’t get feedback along the way.
People will tell you everything you need to do a good job, if you ask. Take control of your career. Ask more. Assume less.
Breakdowns happen. There will be days people won’t give you what you need to complete projects. Things will break. And you will look bad. When breakdowns happen, I always ask myself, “What could I have done to prevent this situation?” or “What did I do to help create this situation?” I see myself as accountable for whatever breakdowns occur.
It may sound odd that I always look at myself when breakdowns occur, even when it’s someone else who didn’t do their job, but it’s just easier. I can’t control anyone else. But I can control me (admittedly, some days I do a better job at this than others). When I can identify something I could have done to make a situation go differently, I feel more in control – aka better.
It’s like getting off a highway versus sitting in bumper-to-bumper traffic. The alternate route may take longer, but at least I’m moving. I feel like I’m doing something and thus have more control. Taking responsibility for everything that happens to you is similar. When you’re accountable, you can do something to improve your situation. When someone else is accountable, you’re at the mercy of other people and have very little control.
There are, of course, exceptions to the practice that “we’re always accountable.” Terrible acts of violence, crime, and illness happen to people, about which they have no control. But in general, in our day-to-day lives, there is typically something we did to contribute to a bad situation or something we can do to improve it.
Here are five practices for improving difficult situations at work, even when you didn’t create the mess (alone).
1) Ask more questions. If you’re not clear about what someone is expecting from you, ask. You’re responsible for doing good work, regardless of the type of direction you receive.
2) Tell people what you think they’re expecting and how you’re planning to approach a project or task, to ensure everyone’s expectations are aligned. Clarifying expectations beats doing several weeks worth of work, only to discover what you created isn’t what someone else had it mind.
3) Ask for specific feedback as projects progress. Don’t wait until the end of a project to find out how you performed.
4) Say “thank you” for whatever feedback you receive versus defending yourself. The person providing feedback will be pleasantly surprised at your receptivity, and their frustration will dissipate more quickly. This could sound like, “That’s good feedback. I’m sorry that happened. Thank you for telling me.”
5) Admit when you make a mistake or when you wish you had done something differently. Don’t wait for someone to tell you. Saying, “I’m sorry. How can I make this right with you?” goes a long way.
I consistently ask the following questions:
“What could I have done differently?”
“What did I do to contribute to this situation?”
“What can I do now to make this situation better?”
“What can I do to prevent this from happening again?”
I encourage you to ask these questions, even when someone else drops the ball. You can’t control others, but you can control you. And your happiness and success is your responsibility.
Lots of organizations send out employee engagement surveys with the desire of improving employee engagement and retention; unfortunately, they often damage both in the process.
There are a few employee engagement survey pitfalls that luckily are easy to avoid.
Here are three practices to follow when sending out employee engagement surveys:
Shorter is better. I hate to say this, but no one wants to fill out an employee engagement survey. It’s time consuming, employees doubt the survey will yield results, and they worry that their feedback isn’t really confidential.
Make your employee engagement survey easy to fill out by making it short. And by short, I mean 25 questions or fewer. You’ll get a better response rate to a 25-question survey than a 65-question one.
Provide employees with survey results quickly. Most organizations ask for too much information. Leaders are overwhelmed by the volume of survey information, so they spend months and months reviewing it, while employees comment on yet another employee survey with no communication.
Send out a succinct communication sharing the top few learnings – the good and the not-so-good — within a few weeks of sending out the survey. You don’t need to take action at the same time. Simply keep employees in the loop by communicating a quick summary of what you learned. If you wait too long to share the feedback, it often never gets communicated. And the next time you send out a survey, employees will remember the absence of information and be hesitant to fill it out.
Within 90-days, tell employees what you will and won’t be changing, based on the survey feedback, and tell them why. Employees don’t need or expect all of their input to be utilized. Closing the loop with clear communication about what you are and aren’t changing, and why, is often sufficient.
The people you live and work with are hesitant to give you negative feedback. They’re afraid you’ll freak out, and they don’t want to deal your freak out. It’s easier to say nothing.
When I started teaching how to give and receive feedback, I provided elaborate explanations as to the predictable response to feedback and the rationale for that response. Now I’ve boiled the natural response to receiving feedback to three words: The Freak Out.
Every person you know – personally and professionally – wants to be liked and approved of. Even the people in your organization who you think are lazy, want you to think highly of them. And when anyone calls another person’s competence into question, that person is likely to freak out (become defensive).
It’s very difficult not to get at least a little bit defensive when receiving feedback. A defensive response often sounds something like, “Thanks for the telling me that. Can I tell you why I did it that way?” The problem with that slightly defensive response is that what the other person hears is, “You’re not listening. I’m wasting my time talking to you.” People want to feel heard. And when the feedback recipient becomes defensive, the person giving feedback doesn’t feel heard.
Don’t feel badly about becoming defensive when you receive negative feedback. Becoming defensive when receiving bad news just means you’re a living, breathing human being with feelings. But The Freak Out scares people. They don’t want to deal with your mild, moderate, or very defensive reactions.
Because people want to avoid The Freak Out, they keep negative feedback to themselves, or worse, tell someone else. If you want more truth, you need to make it clear there won’t be negative repercussions for speaking up.
Here are seven steps to get others comfortable giving you negative feedback:
1. Ask for feedback.
2. Be specific about the type of feedback you want.
3. Tell the person from whom you’re asking for feedback when and where they can observe you in action.
An ineffective way to ask for feedback: “I really want your feedback. Feel free to give it anytime.” This is too vague and doesn’t demonstrate seriousness on your part.
A more effective way to ask for feedback: “I really want your feedback on the pace of the new-hire-orientation program. Are you available to call into the first hour of orientation next Wednesday at 9:00 a.m. and tell me what you think of the pace and why?” This request tells the person specifically what you want and demonstrates you’re serious about wanting feedback.
4. When you receive feedback, say, “Thank you for telling me. I’m going to think about what you’ve said and may come back to you in a few days to talk more.”
5. Don’t respond to negative feedback immediately. End that part of the conversation instead of responding.
6. If you’d like more information or want to tell the person you disagree with what they said, wait until you’re calm to have that conversation. That can be minutes or a few days later.
7. You can express a counterpoint of view, just don’t do it immediately after receiving feedback. Anything you say in the moment will likely sound defensive.
No matter what a person’s role in your life – your boss, a peer, external customer, or even a friend or spouse – it takes courage to give you feedback. When a conversation requires courage, the speaker’s emotions are heightened. If the feedback recipient’s emotions rise in response to the feedback, conversations escalate. This is how arguments start. If you want to put the other person at ease and get more feedback in the future, do the opposite of what people are expecting. Rather than getting even the slightest bit defensive, do the opposite. Say, “Thank you for the feedback. I’m sorry you had that experience. I’m going to think about what you’ve said and may come back to you to talk more.” Then end that part of the conversation. You’re not being dismissive; you’re ensuring your emotions don’t take over. If you want to have a second conversation, have it within a week. Revisiting the conversation in a timely way shows you respect what the other person is saying and both of you will remember the topic at hand.
Ending a conversation, when all you want to do is react, is very difficult. Putting a conversation on hold will require a good deal of self-control, but the rewards are great. You will build trust, strengthen relationships, and get more information than you have in the past – information you need to manage your career, reputation, and business.
You’ve heard countless times that you never get a second chance to make a first impression. So when something not-so-positive happens – a customer is upset, you missed a deadline, or made an error – don’t let your boss find out about it from someone else. Manage your professional reputation and get there first to create the first impression of what happened.
Managers don’t like surprises. If your manager is going to get a call about something that isn’t positive, let them know before the call comes in. You will create your manager’s perception of the situation, and perceptions are hard to change. Don’t wait for the s*** to hit the fan. Get ahead of the problem by coming forward and giving your manager and other stakeholders a heads up.
It could sound something like this, “I just had a tough conversation with John in IT. You may get a call. Here’s what happened… I didn’t want you to be surprised.”
Or “I told Jessica at Intellitec we’re raising our prices this quarter. She wasn’t happy. You may get a call.”
Or let’s say you’re going to work on a strained relationship. Tell your manager before you take action. It could sound something like this, “I want to work on my relationship with Julie. Our relationship has been strained since we worked together on the software project last year. I’d like to approach her, tell her that I know our relationship is strained, and that I’d like a good working relationship with her. Then I’d like to ask if she’s willing to have lunch with me, talk about what’s happened, and see if we can start again in a more positive way. What do you think of me doing that? Would you approach the conversation differently? I don’t know how it’s going to go, so I wanted you to know what I’m planning to do, just in case it backfires and you get a call.”
Manage your professional reputation assertively by taking responsibility for mistakes, working on damaged relationships, and telling your manager before someone else does!
Most employees need only a handful of things to be satisfied and productive at work. The key is getting employees to tell you what those things are. And they might just tell you, if you ask.
Effective management involves asking questions during the interview process, after an employee starts, and again 90-days to six months into the job.
I recommend asking the seven questions below. I call the questions, Candor Questions.
Candor Question number one: “What brought you to our organization? Why did you accept this job? What are you hoping the job will provide?” Ask one of these three questions. Pick the one you like best.
Candor Question number two: “What would make you leave this job? What are your career deal breakers, things you just can’t tolerate at work?” Ask either of these questions.
Candor Question number three: “What type of work, skills, and/or areas of our organization do you want to learn more about?”
Candor Question number four: “Tell me about the best manager you ever had. What made them the best manager?” This will tell you what the employee needs from you as a manager and is a much better question than, “What do you need from me as your manager?” That is a hard question to answer. Telling you the best manager they ever had is easy.
Candor Question number five: “Tell me about the worst manager you ever had? What made them the worst manager?”
Candor Question number six: “What are your pet peeves at work? What will frustrate you?” Why find out the hard way what frustrates employees when it’s so easy to ask. This question demonstrates that you want your employees to be happy and that you will flex your own preferences, when possible, to meet employees’ needs.
Candor Question number seven: “How do you feel about being contacted via cell phone or texts outside of business hours? How do you feel about receiving emails during the evenings and weekends? What time is too early? What time is too late?” When boundaries like work hours are violated, it often erodes employees’ loyalty to managers and organizations, and it’s such an easy question to ask.
If you’ve participated in one of our management trainings or received a box of Candor Questions for Managers, you know I could go on. But these seven questions are a good start.
Regardless of age, work, and educational background, employees have a few things in common.
Employees want to:
• Work for someone who takes an interest in and knows them
• Feel valued and appreciated for their contributions
• Be part of and contribute to something greater than themselves
• Feel respected as a person. Managers respect their time, expertise, and needs
Taking the time to get to know employees throughout your working relationship accomplishes many employee needs.
If you have long-time employees, it’s never too late to ask these questions. Regardless of for how long employees have worked for you, they’ll appreciate you asking. Don’t worry that employees will raise an eyebrow and wonder why you’re asking now. They’ll just be happy you’re asking. You can simply say, “I realized that I’ve never overtly asked these questions. I just assume I know. But I don’t want to do that. During our next one-on-one meeting I’d like to ask you these questions and you can ask me anything you’d like.”
If you have a manager who is unlikely to ask these questions, provide the information. Don’t wait to be asked. You’re 100% accountable for your career. Tell your manager, “There are a few things about me I want to share with you. I think this information will help ensure I do great work for the organization for a long time.”
Managers, the better your relationship with your employees and the more you know about what your employees need from you, the organization, and the job, the easier employees are to engage, retain, and manage. Stop guessing and start asking.
When I interviewed for my last job, before starting Candid Culture 19 years ago, the CEO put a mug in front of me with the company’s values on it and asked if I could live by those values at work. He was smart. Hiring someone with the skills to do a job is one thing. Hiring someone who fits into the organizational culture, is another.
Determining if a prospective employee will fit your organizational culture is much harder than determining if someone has the skills to do a job. Often when an employee leaves a job, only to take the same role at another company, they left for fit. They just didn’t feel comfortable. They weren’t a good fit with the organizational culture.
You’ve probably heard discussions about employees who deliver results at the expense of relationships. Or about employees who fellow employees really like, but they just can’t do the job.
Leaders of organizations need to decide what’s important: What people do? How they do it? Or both. I’m going to assert that both the work employees deliver and how they deliver that work is equally important. I think you should hire and fire for fit.
Work hard to hire people who will fit into your organizational culture. Get rid of people who don’t fit. The impact on your organization’s reputation and on internal and external relationships depends on hiring people who behave consistently with your brand and how you want your organization’s culture to feel.
At Candid Culture, we teach people to have open, candid, trusting relationships at work. Thus, we must hire people who are open to feedback and communicate honestly, and we tell people who don’t model those behaviors to find a better fit
Here are a few ways to ensure you hire people who are a good organizational culture fit:
Share your current or desired culture with job candidates early, often, and clearly.
Work to assess how candidates fit the culture. Use practical interviews, job shadowing, and reference checks to assess organizational culture fit.
Talk about the culture when onboarding employees.
Make behaving according to the culture part of your performance appraisal process.
Reward behavior that matches the culture.
Have consequences for not acting according to the culture. A negative feedback conversation is a consequence.
Ensure your leaders and managers live the culture. Eliminate leaders and managers who aren’t a good culture fit. This takes courage.
When people leave an organization, they don’t often take copies of reports they produced or work they created. And if they do, they rarely look at that work. What they do take, remember for years to come, and find meaning in, are the relationships they built at work. Relationships are dependent on organizational culture.
Determine the organizational culture you want. Talk about it regularly. Require people to act according to the culture. Reward the ones who do. Get rid of the ones who don’t. Make working in your organization feel as you want it to feel.
People leave feedback training armed with new skills and unfortunately sometimes use those skills as a weapon. It goes something like this, “I need to have a candid conversation with you.” And then the person proceeds to dump, dump, dump. This couldn’t be more wrong, wrong, wrong.
When you give someone negative feedback you are essentially telling the person they did something wrong. And who likes to be wrong? The ego gets bruised, and people often start to question themselves. This normal reaction doesn’t mean you shouldn’t give feedback, you just need to do it judiciously.
Ask yourself these four questions when deciding whether or not to give someone feedback:
Do I have the relationship to provide feedback? Does the recipient trust me and my motives?
Do I have permission to give feedback? If the recipient doesn’t work for you, you need permission to give feedback.
Is this something the person can do something about? If it’s not a change the recipient can make, keep your thoughts to yourself.
Is the feedback helpful? Ultimately the purpose of all feedback is to be helpful.
Let’s say you’re on the receiving end of too much feedback. What should you do? It’s ok to say “no thank you” to feedback. Here’s what you could say:
“Thank you for taking the time to bring this to my attention. I really appreciate it. You’ve given me a lot of feedback today. I’d like something to focus on that I can impact right now. What’s the most important thing I should do?” You’ve validated the other person and demonstrated openness and interest. You’ve also set some boundaries and expectations of what you will and won’t do.
“Thank you for taking the time to share your requests about… We won’t be making any changes to that and here’s why.” It’s ok not to act on all feedback, simply tell people why you won’t.
“I appreciate your concern. I’m not looking for feedback on that right now.” Can you say that to someone? Yes. Should you? Sometimes. To your boss – no. To someone who offers unsolicited advice that’s outside of their lane, yes. They’ll get the message.
People can only act on and digest small amounts of feedback at a time. Be judicious and assess your motives. The purpose of feedback is to be helpful, when the feedback is requested, and when you have the relationship to give it.
If you receive too much feedback or unsolicited feedback, it’s ok to decline. You’re not the 7-11, aka you’re not always open.
It could sound something like this, “I just had a tough conversation with John in IT. You may get a call. Here’s what happened… I didn’t want you to be surprised.”
she’s willing to have lunch with me, talk about what’s happened, and see if we can start again in a more positive way. What do you think of me doing that? Would you approach the conversation differently? I don’t know how it’s going to go, so I wanted you to know what I’m planning to do, just in case it backfires and you get a call.”
