I agree with Jordan.  There are definitely instances where to prevent ambiguity or uncertainty phrasing the request as a question will do more harm than good...that said its also critical to keep the request respectful for obvious reasons.

MET

-----Original Message-----
From: ironlady@stagen.simplelists.com [mailto:ironlady@stagen.simplelists.com] On Behalf Of Massey, Jordan (OUC)
Sent: Wednesday, June 21, 2017 5:55 PM
To: ironlady@stagen.simplelists.com
Subject: RE: Committed Action

I don't necessarily agree.  I think it depends on the situation and if it is truly a request or is really a requirement.

If it is really a requirement, but presented as a question, you may end up seeming to be manipulative, because there is really only one satisfactory answer and any other answer will not be accepted.  At the end of the day - in order to show that committed action concepts are really ok to employ, there has to be a differentiator between a request and a requirement.  If the line is cloudy, your audience will assume questions are really demands and the answer always has to be yes.

My opinion is that requirements/demands should be stated as such.  (EX: Please complete this project by 5pm tomorrow.)

Jordan Massey, CPA, CIA  |  Director  |  Internal Audit  |  ORIX USA Corporation  |  1717 Main Street, Suite 900  |  Dallas, TX 75201  |  t  |  469-385-1378     c  |  214-205-1926     e  |  jordan.massey@orix.com  |  www.orix.com  |  www.orixfoundation.org

-----Original Message-----
From: ironlady@stagen.simplelists.com [mailto:ironlady@stagen.simplelists.com] On Behalf Of Marie Reynolds
Sent: Wednesday, June 21, 2017 9:11 AM
To: ironlady@stagen.simplelists.com
Subject: Re: Committed Action

Ryan- thanks for the post.  My experiences:

Questions stated respectfully and clearly are almost always well received.

Statements are received as authoritative "calls to action" (even though this  may not be intended) and are not well received most of the time.

-Marie

Sent from my iPhone

> On Jun 21, 2017, at 7:56 AM, Farha, Ryan <Ryan.Farha@orix.com> wrote:
>
> I've been trying to use Committed Action as much as possible since learning in the HPP.
>
> Before HPP, I had a problem with being direct - my concern was rubbing people the wrong way, or coming off as rude, abrasive, etc. The Committed Action practice has helped me grow out of that concern.  In fact, when I started using it someone told me she appreciates the clarity in assignments so she knows what is urgent and what isn't.  It's a useful tool to prioritize for the recipient.
>
> One other practice point I tried to figure out early on was whether to frame requests as a question (perhaps with someone senior to you) or a statement.
>
> For example, "Jack, can you please . . . ?" versus "Jack, please . . ."
>
> I mostly frame requests as a questions to show respect to the recipient. I'd be curious to know whether any of you disagree with this approach, and think maybe framing as a statement is better with direct reports or in other situations.
>
> Ryan Farha
> Managing Director, Legal
> (214) 237-2242
> ryan.farha@orix.com<mailto:ryan.farha@orix.com>