Re: Committed Action from Nicola Seth Braun (11 Jul 2017 16:23 UTC)
Re: Committed Action from Nicola Hobeiche, Nicola (11 Jul 2017 21:39 UTC)

Re: Committed Action from Nicola Hobeiche, Nicola 11 Jul 2017 21:39 UTC

Yes! Mostly. With one additional commitment of a commitment to commit when I am back from vacation. 😁

Nicola Hobeiche
Managing Director, Assistant General Counsel
ORIX USA Corp
214.237.2036

> On Jul 11, 2017, at 11:23 AM, Seth Braun <seth.braun@stagen.com> wrote:
>
> So,
>
> Did you come through on your commitment to commit?
>
> Seth
>
> Seth Braun | Executive Coach
> Seth.Braun@stagen.com |  303.443.6543
>
> Stagen | 3535 Travis  Street | Suite 100 | Dallas, TX 75204
> p: 214.744.9255 | f: 214.744.0094 | www.stagen.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.stagen.com_&d=DwIGaQ&c=l6wIEjFZ2r6NRbgTeJOW4HMPY8FVASe8l9IlzHzRYYs&r=K3J3Zev6irjtWJbrLyoKFobJx7xjDTOeqpy3VMTGlo4&m=FAsGPVQjGwoDv_TJfWpAvyJrDkKRbsbKSZ9p7i8WItM&s=7LwK8ArVhkPwAUs3LUiCutDiwhVGjbb4PN64-nDB1nA&e= >
>
>
>
>
>
>
> On 7/6/17, 10:56 PM, "ironlady@stagen.simplelists.com on behalf of
> Hobeiche, Nicola" <ironlady@stagen.simplelists.com on behalf of
> Nicola.Hobeiche@orix.com> wrote:
>
>> Ryan, Bob, Ron and I are working on a legal project that Rand is helping
>> us on. In our call today with Rand we ended with our to do list before
>> the next call and also our committed actions. Rand made a commitment to
>> get us some things by tonight - I have no doubt he will meet his
>> commitment to us. Ron, ryan, bob and I made a commitment to each other to
>> make a commitment, and having all gone through or being in the ILP, it's
>> been really great to be speaking the same language together and
>> appreciate what it means to take committed action and also follow through
>> on our promise to each other to take committed action.
>> It's happening people - it's applying all this skill and knowledge in our
>> ORIX world! We are making ripples each of us to get the class before us
>> and our class over the top and to the other side.
>> Ask me next week if we actually came through on our commitment to commit
>> 😉
>>
>> Nicola Hobeiche
>> Managing Director, Assistant General Counsel
>> ORIX USA Corp
>> 214.237.2036
>>
>>> On Jul 6, 2017, at 5:16 PM, Martin, David <DMartin@marinercapital.com>
>>> wrote:
>>>
>>> Piling on here, agree with below that phrasing as a question,
>>> especially if with a subordinate, can leave the request open ended
>>> unless the question is around whether a deadline is feasible or not.
>>>
>>> David Martin
>>> Managing Director
>>>
>>> Mariner Investment Group
>>> 1717 Main Street, Suite 900, Dallas, TX 75201
>>> Tel. (214) 237-2128
>>> Mobile (214) 649-6649
>>>
>>> Email dmartin@marinercapital.com
>>>
>>> Attorney Client Privileged and/or Confidential Information
>>>
>>>
>>> -----Original Message-----
>>> From: ironlady@stagen.simplelists.com
>>> [mailto:ironlady@stagen.simplelists.com] On Behalf Of Tharp, Mark
>>> Sent: Thursday, June 22, 2017 8:21 AM
>>> To: ironlady@stagen.simplelists.com
>>> Subject: RE: Committed Action
>>>
>>> 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>
>>>
>>> ________________________________
>>>
>>> This communication is for information purposes only and should not be
>>> regarded as an offer, solicitation or recommendation to sell or purchase
>>> any security or other financial product. The information and any
>>> opinions contained herein are as of the date of this message and the
>>> firm does not undertake any obligation to update them. Past performance
>>> is not indicative of future results, and no representation or warranty,
>>> express or implied, is made regarding future performance. All
>>> information contained in this communication is not warranted as to
>>> completeness or accuracy and is subject to change without notice. This
>>> email should be considered confidential and may not be reproduced in
>>> whole or in part, and may not be circulated or redelivered to any person
>>> without the prior written consent of the firm. If you are not the
>>> intended recipient of this message you must not disseminate, distribute,
>>> copy or take any action in reliance on this e-mail or any attachment.
>>> Please see the following
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marinercapital.co
>>> m_disclaimer_mariner.html&d=DwIFAw&c=l6wIEjFZ2r6NRbgTeJOW4HMPY8FVASe8l9Il
>>> zHzRYYs&r=K3J3Zev6irjtWJbrLyoKFobJx7xjDTOeqpy3VMTGlo4&m=OV8PYk-pYM-WKU1B7
>>> 4OOfWBrLKMdRDcYIcsPkAW7eXk&s=Q2Y5jYFAi9uT8hsPfGfeP-OFLDEwed_S1OihyV7yPJc&
>>> e=  for important disclosures that are incorporated by reference.
>