When asking for something at work, many folks fall into the "yes or no" trap: they frame their request in a way that gets a binary "yes" or "no" answer. Sometimes, you'll get a "yes", but often, you'll get a "no." And when your request is denied, the conversation has effectively reached a dead end.

Instead, we recommend using the "What needs to be true?" framing to approach important conversations. Here's how it works: 

• Imagine your desired end state. Maybe it's working from home, moving to a new role, or taking on a project.
  ‍
• Now, think about why this end state is good for business. Write that down in simple, easy to understand language like this: "There seems to be a big need for this work to get done, but we don't have anyone who is explicitly responsible for it. I think having someone dedicated to this project would make sure it gets done well and on time." 
  ‍
• Then, use the "What needs to be true" statement. It might sound something like this: "Given my history working on projects like this, I'd love to be considered for this work. From your perspective, what needs to be true for me to take on this project?" 
  ‍
• Lastly, listen and make notes! The response you get from the "What needs to be true" question is essentailly a blueprint on how you can proactively manage any onbjections you might receive for your request. Once you have this response, take the time to check as many of those boxes as possible, and then re-visit the conversation with something like this: "Hey there. I appreciate you sharing your thoughts on that project and what you think it needs to be successful. I wanted to continue that conversation; I'm feeling confident that I'm the right person to take it on based on what you shared you were looking for." 

Once you've given it a try, let us know how it works for you in the comments below!