I recently had an experience where a project manager was basically demanding a yes/no answer in what felt to me like a power move. PM: Are we good to go live o

I recently had an experience where a project manager was basically demanding a yes/no answer in what felt to me like a power move. PM: Are we good to go live on Wednesday? (it's Monday) Me: Feature X isn't fully ready yet. Data science needs to address a bug that I found 2 weeks ago. If they fix the bug, I'll prepare a release for Wednesday. Alternatively, we can go live without feature X. PM: Feature X is required. Data science says they'll have the bug fix ready. So are we good to go live Wednesday? Me: If data science implements the bug fix, I'll release on Wednesday. (I don't trust data science to be ready, but I'm not going to say that) PM: Okay, so we're good to go live? <two or three more cycles> Context is very relevant. Yes/no questions often aren't yes/no. I didn't even include the full conversation where I tried to clarify what he means "go live" or whether the customer had signed off. In the end, customers hadn't signed off and he hadn't coordinated with other teams. The release has been put off for at least a month. I think this is somewhat different than a yes/no informational question. In this case, it wasn't even a yes/no question, it was a yes/yes question, he wanted me to take responsibility.